[Buildroot] Problem trying to use an external tool chain

[Buildroot] Problem trying to use an external tool chain

[John O'Sullivan]

Hi,

I am trying to setup buildroot to use an external project from Xilinx

It has the followiing structure

aarch64-linux-gnu  bin  include  lib  lib64  libexec  share



>>> toolchain-external-custom  Installing to staging directory
/usr/bin/install -D -m 0755 /home/developer/BuildRoot/buildroot-2017.02.4/output/build/toolchain-external-custom/toolchain-wrapper /home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/bin/toolchain-wrapper
ln: failed to create symbolic link '/home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib': No such file or directory


Anyone have any idea on what its failing on, what lis it trying to link

'/home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib to

Is it something to do with the fact that it is 64 bit


Regards

John

I

________________________________

This email and any files transmitted with it are confidential and are intended for the sole use of the individual to whom they are addressed. Black Box Corporation reserves the right to scan all e-mail traffic for restricted content and to monitor all e-mail in general. If you are not the intended recipient or you have received this email in error, any use, dissemination or forwarding of this email is strictly prohibited. If you have received this email in error, please notify the sender by replying to this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170911/d6a34029/attachment.html>

[Buildroot] Problem trying to use an external tool chain

[Arnout Vandecappelle]

 Hi John,

On 11-09-17 19:08, John O'Sullivan wrote:
> Hi,
> 
> I am trying to setup buildroot to use an external project from Xilinx
> 
> It has the followiing structure
> 
> aarch64-linux-gnu? bin? include? lib? lib64? libexec? share
> 
> 
> 
>>>> toolchain-external-custom? Installing to staging directory
> /usr/bin/install -D -m 0755
> /home/developer/BuildRoot/buildroot-2017.02.4/output/build/toolchain-external-custom/toolchain-wrapper
> /home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/bin/toolchain-wrapper
> ln: failed to create symbolic link
> '/home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib':
> No such file or directory

 That directory should have been created as part of
SKELETON_INSTALL_STAGING_CMDS in the skeleton package.

 Is it possible that you changed the arch/toolchain configuration without 'make
clean'? Check /home/developer/BuildRoot/buildroot-2017.02.4/output/staging, it
should point to host/usr/aarch64-buildroot-linux-gnu/sysroot.


 Regards,
 Arnout

> 
> 
> Anyone have any idea on what its failing on, what lis it trying to link?
> 
> '/home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib
> to
> 
> Is it something to do with the fact that it is 64 bit
> 
> 
> Regards
> 
> John
> 
> I
> 
> 
> --------------------------------------------------------------------------------
> 
> This email and any files transmitted with it are confidential and are intended
> for the sole use of the individual to whom they are addressed. Black Box
> Corporation reserves the right to scan all e-mail traffic for restricted content
> and to monitor all e-mail in general. If you are not the intended recipient or
> you have received this email in error, any use, dissemination or forwarding of
> this email is strictly prohibited. If you have received this email in error,
> please notify the sender by replying to this email.
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] Problem trying to use an external tool chain

[John Stile]

For the settlement I will have to give rxy part of my ira, 401k, and
ameritrade (straight stock) accounts.

I am trying to figure out how to do it tax free, and how much that would
cost.


On 09/11/2017 03:49 PM, Arnout Vandecappelle wrote:
>  Hi John,
>
> On 11-09-17 19:08, John O'Sullivan wrote:
>> Hi,
>>
>> I am trying to setup buildroot to use an external project from Xilinx
>>
>> It has the followiing structure
>>
>> aarch64-linux-gnu  bin  include  lib  lib64  libexec  share
>>
>>
>>
>>>>> toolchain-external-custom  Installing to staging directory
>> /usr/bin/install -D -m 0755
>> /home/developer/BuildRoot/buildroot-2017.02.4/output/build/toolchain-external-custom/toolchain-wrapper
>> /home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/bin/toolchain-wrapper
>> ln: failed to create symbolic link
>> '/home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib':
>> No such file or directory
>  That directory should have been created as part of
> SKELETON_INSTALL_STAGING_CMDS in the skeleton package.
>
>  Is it possible that you changed the arch/toolchain configuration without 'make
> clean'? Check /home/developer/BuildRoot/buildroot-2017.02.4/output/staging, it
> should point to host/usr/aarch64-buildroot-linux-gnu/sysroot.
>
>
>  Regards,
>  Arnout
>
>>
>> Anyone have any idea on what its failing on, what lis it trying to link 
>>
>> '/home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib
>> to
>>
>> Is it something to do with the fact that it is 64 bit
>>
>>
>> Regards
>>
>> John
>>
>> I
>>
>>
>> --------------------------------------------------------------------------------
>>
>> This email and any files transmitted with it are confidential and are intended
>> for the sole use of the individual to whom they are addressed. Black Box
>> Corporation reserves the right to scan all e-mail traffic for restricted content
>> and to monitor all e-mail in general. If you are not the intended recipient or
>> you have received this email in error, any use, dissemination or forwarding of
>> this email is strictly prohibited. If you have received this email in error,
>> please notify the sender by replying to this email.
>>
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>

[Buildroot] Problem trying to use an external tool chain

[John O'Sullivan]

Hi Arnout,

Yes that was the problem, thank you so much for your help

Kind regards
John

-----Original Message-----
From: Arnout Vandecappelle [mailto:arnout at mind.be]
Sent: 11 September 2017 23:50
To: John O'Sullivan; buildroot at busybox.net
Subject: Re: [Buildroot] Problem trying to use an external tool chain

 Hi John,

On 11-09-17 19:08, John O'Sullivan wrote:
> Hi,
>
> I am trying to setup buildroot to use an external project from Xilinx
>
> It has the followiing structure
>
> aarch64-linux-gnu  bin  include  lib  lib64  libexec  share
>
>
>
>>>> toolchain-external-custom  Installing to staging directory
> /usr/bin/install -D -m 0755
> /home/developer/BuildRoot/buildroot-2017.02.4/output/build/toolchain-e
> xternal-custom/toolchain-wrapper
> /home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/bin/tool
> chain-wrapper
> ln: failed to create symbolic link
> '/home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib':
> No such file or directory

 That directory should have been created as part of SKELETON_INSTALL_STAGING_CMDS in the skeleton package.

 Is it possible that you changed the arch/toolchain configuration without 'make clean'? Check /home/developer/BuildRoot/buildroot-2017.02.4/output/staging, it should point to host/usr/aarch64-buildroot-linux-gnu/sysroot.


 Regards,
 Arnout

>
>
> Anyone have any idea on what its failing on, what lis it trying to
> link
>
> '/home/developer/BuildRoot/buildroot-2017.02.4/output/host/usr/aarch64
> -buildroot-linux-gnu/sysroot/usr/lib
> to
>
> Is it something to do with the fact that it is 64 bit
>
>
> Regards
>
> John
>
> I
>
>
> ----------------------------------------------------------------------
> ----------
>
> This email and any files transmitted with it are confidential and are
> intended for the sole use of the individual to whom they are
> addressed. Black Box Corporation reserves the right to scan all e-mail
> traffic for restricted content and to monitor all e-mail in general.
> If you are not the intended recipient or you have received this email
> in error, any use, dissemination or forwarding of this email is
> strictly prohibited. If you have received this email in error, please notify the sender by replying to this email.
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>

--
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

________________________________

This email and any files transmitted with it are confidential and are intended for the sole use of the individual to whom they are addressed. Black Box Corporation reserves the right to scan all e-mail traffic for restricted content and to monitor all e-mail in general. If you are not the intended recipient or you have received this email in error, any use, dissemination or forwarding of this email is strictly prohibited. If you have received this email in error, please notify the sender by replying to this email.