meta-toolchain not always relocatable

meta-toolchain not always relocatable

[Marco Cavallini]

Hi,
I am facing to a very odd behaviour installing the resulting meta-toolchain.
I launch poky-glibc-i686-meta-toolchain-cortexa9hf-vfp-neon-toolchain-1.7.1.sh

If I install in the default directory or in /opt/poky/test it works as
expected, but if I install in /opt/poky/1.7.1-cortexa9hf there is a
problem. Using YP older that dizzy it worked with a charm.

$ ./poky-glibc-i686-meta-toolchain-cortexa9hf-vfp-neon-toolchain-1.7.1.sh
Enter target directory for SDK (default: /opt/poky/1.7.1):
/opt/poky/1.7.1-cortexa9hf
You are about to install the SDK to "/opt/poky/1.7.1-cortexa9hf". Proceed[Y/n]?
Extracting SDK...done
Setting it up...done
SDK has been successfully set up and is ready to be used.

Now I can't use it calling the env setup as usual
$ . /opt/poky/1.7.1-cortexa9hf/environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi

the reason is that the resulting path is incorrect

$ env | grep PATH
PATH=/opt/poky/1.7.1-cortexa9hf-cortexa9hf/sysroots/i686-pokysdk-linux/usr/bin:/opt/poky/1.7.1-cortexa9hf-cortexa9hf/sysroots/i686-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi:.....

--
Marco

Re: meta-toolchain not always relocatable

[Paul Eggleton]

Hi Marco,

On Thursday 19 March 2015 17:46:44 Marco Cavallini wrote:
> I am facing to a very odd behaviour installing the resulting meta-toolchain.
> I launch
> poky-glibc-i686-meta-toolchain-cortexa9hf-vfp-neon-toolchain-1.7.1.sh
> 
> If I install in the default directory or in /opt/poky/test it works as
> expected, but if I install in /opt/poky/1.7.1-cortexa9hf there is a
> problem. Using YP older that dizzy it worked with a charm.
> 
> $ ./poky-glibc-i686-meta-toolchain-cortexa9hf-vfp-neon-toolchain-1.7.1.sh
> Enter target directory for SDK (default: /opt/poky/1.7.1):
> /opt/poky/1.7.1-cortexa9hf
> You are about to install the SDK to "/opt/poky/1.7.1-cortexa9hf".
> Proceed[Y/n]? Extracting SDK...done
> Setting it up...done
> SDK has been successfully set up and is ready to be used.
> 
> Now I can't use it calling the env setup as usual
> $ .
> /opt/poky/1.7.1-cortexa9hf/environment-setup-cortexa9hf-vfp-neon-poky-linux
> -gnueabi
> 
> the reason is that the resulting path is incorrect
> 
> $ env | grep PATH
> PATH=/opt/poky/1.7.1-cortexa9hf-cortexa9hf/sysroots/i686-pokysdk-linux/usr/b
> in:/opt/poky/1.7.1-cortexa9hf-cortexa9hf/sysroots/i686-pokysdk-linux/usr/bin
> /arm-poky-linux-gnueabi:.....

Yes, I discovered this a few months ago and it got fixed in master:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=7032

It looks like we still haven't backported the fix to 1.7 though. Anibal, could 
you please take care of that?

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: meta-toolchain not always relocatable

[akuster808]

On 03/19/2015 10:20 AM, Paul Eggleton wrote:
> Hi Marco,
>
> On Thursday 19 March 2015 17:46:44 Marco Cavallini wrote:
>> I am facing to a very odd behaviour installing the resulting meta-toolchain.
>> I launch
>> poky-glibc-i686-meta-toolchain-cortexa9hf-vfp-neon-toolchain-1.7.1.sh
>>
>> If I install in the default directory or in /opt/poky/test it works as
>> expected, but if I install in /opt/poky/1.7.1-cortexa9hf there is a
>> problem. Using YP older that dizzy it worked with a charm.
>>
>> $ ./poky-glibc-i686-meta-toolchain-cortexa9hf-vfp-neon-toolchain-1.7.1.sh
>> Enter target directory for SDK (default: /opt/poky/1.7.1):
>> /opt/poky/1.7.1-cortexa9hf
>> You are about to install the SDK to "/opt/poky/1.7.1-cortexa9hf".
>> Proceed[Y/n]? Extracting SDK...done
>> Setting it up...done
>> SDK has been successfully set up and is ready to be used.
>>
>> Now I can't use it calling the env setup as usual
>> $ .
>> /opt/poky/1.7.1-cortexa9hf/environment-setup-cortexa9hf-vfp-neon-poky-linux
>> -gnueabi
>>
>> the reason is that the resulting path is incorrect
>>
>> $ env | grep PATH
>> PATH=/opt/poky/1.7.1-cortexa9hf-cortexa9hf/sysroots/i686-pokysdk-linux/usr/b
>> in:/opt/poky/1.7.1-cortexa9hf-cortexa9hf/sysroots/i686-pokysdk-linux/usr/bin
>> /arm-poky-linux-gnueabi:.....
>
> Yes, I discovered this a few months ago and it got fixed in master:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7032
>
> It looks like we still haven't backported the fix to 1.7 though. Anibal, could
> you please take care of that?

I can if Anibal is working on other things. I have slowly back porting 
changes anyway for the next dizzy release.

- armin
>
> Thanks,
> Paul
>