From: Microbit_Ubuntu <microbit@virginbroadband.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] ext x-tools (ct-ng-1.6.1) make error for LIB path with 2010.02
Date: Tue, 04 May 2010 08:06:48 +1000 [thread overview]
Message-ID: <1272924408.17672.12.camel@ubuntu> (raw)
Hi all,
I wonder if someone can enlighten me on this.
After setting up x-tools (ct-ng 1.6.1) and building BR2 2010.02,
1. links-2.2
The configure scripts seem to lose the LIB include for links package :
original error = "cannot find -lz"
After checking around, turns out that the path to staging/usr/lib is
simply not found. I worked around it by making links_LDFLAGS =
-L/path/to/buildroot/output/staging/usr/lib
2. ltrace-0.5
the OS path for sysdeps gets set to :
OS := linux-uclibcgnueabi
whereas internal toolchain 2010.02 produces at start of Makefile :
OS = linux-gnu
This results in an unknown path to /sysdeps/
Has anyone come across this behaviour before ?
I can workaround for now by manually changing Makefile and then resuming
build.
I can't find the common denominator - I think it has to do with CC being
set --sysroot=......
whereas the internal toolchain produces
--isysroot=...... ?????
Any input would be very welcome !!!
TIA
--
Best regards,
Kris
reply other threads:[~2010-05-03 22:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1272924408.17672.12.camel@ubuntu \
--to=microbit@virginbroadband.com.au \
--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