[yocto] nodejs npm qemux86_64

[Jean-Marie LEMETAYER]

Actually I just update my patchset to use ${nonarch_libdir} instead of ${libdir}.

This will be on the next patchset version.

For your information you can check the meta/conf/bitbake.conf file for others target filesystem paths.

Best regards,
Jean-Marie

On Nov 8, 2019, at 10:46 AM, Jean-Marie LEMETAYER jean-marie.lemetayer at savoirfairelinux.com wrote:
> Hi Jonas,
> 
> I am currently refactoring / updating the npm handling in Yocto:
> http://lists.openembedded.org/pipermail/openembedded-core/2019-October/288352.html
> http://lists.openembedded.org/pipermail/bitbake-devel/2019-October/020449.html
> 
> Your point is very interesting, I will take it into account for the next
> patchset version.
> 
> Best regards,
> Jean-Marie
> 
> On Nov 7, 2019, at 10:56 PM, Jonas Andersson jonaskgandersson at gmail.com wrote:
>> Hi,
>> 
>> I have installation problems for npm recipes.
>> Using Yocto thud and machine=qemux86_64(wrlinux-x), but as I can see it this
>> concerns all
>> use of npm.bbclass for 64-bits system.
>> 
>> The problem seems to be the use of ${libdir} in npm.bbclass, when 64 bit is used
>> this expands to lib64.
>> npm install --prefix ${D}${prefix} installs to /usr/lib/node_modules which is
>> not
>> in sync with the following mv ${D}${libdir}/node_modules ${D}${libdir}/node.
>> 
>> I made an quick fix by replacing ${libdir} by ${prefix}/lib/, but as I see it
>> nodejs packages never is installed to lib64 in any other system as I can find
>> information about.
>> 
>> So the question is if the use of ${libdir} is bad and the path should always be
>> to /lib/?
>> 
>> Best regards
>> Jonas