From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with buildroot and external toolchain
Date: Tue, 17 Jun 2008 21:04:46 +0200 [thread overview]
Message-ID: <87k5gng9wx.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190918260A@mi8nycmail19.Mi8.com> (hartleys@visionengravers.com's message of "Tue\, 17 Jun 2008 14\:57\:15 -0400")
>>>>> "hartleys" == hartleys <hartleys@visionengravers.com> writes:
Hi,
hartleys> But, like I said, the copy_toolchain_lib_root is locating
hartleys> the files but not actually copying them. If I manually copy
hartleys> the files to the root file system everything works fine.
Does <cross>-gcc -printf-file-name=<lib> give the right path? Have you
seen the new defaults I added to those settings lately? Those work for
me with a uclibc toolchain.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-06-17 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 17:41 [Buildroot] Problem with buildroot and external toolchain hartleys
2008-06-17 18:38 ` sjhill at realitydiluted.com
2008-06-17 18:57 ` hartleys
2008-06-17 19:04 ` Peter Korsgaard [this message]
2008-06-17 19:13 ` hartleys
2008-06-17 20:15 ` hartleys
2008-06-18 6:46 ` Peter Korsgaard
2008-06-18 18:28 ` hartleys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k5gng9wx.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox