Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot comments and questions
Date: Mon, 27 Apr 2009 09:47:34 +0200	[thread overview]
Message-ID: <87ljpmh71l.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <a4413b2d0904262349m133ac037t4c42095240c1256a@mail.gmail.com> (Hai Shalom's message of "Mon\, 27 Apr 2009 09\:49\:52 +0300")

>>>>> "Hai" == Hai Shalom <hai.shalom@gmail.com> writes:

Please keep communication on the buildroot list, thanks.

 Hai> The reason I am using uClibc 0.9.29 is because I have an NPTL
 Hai> patch over it, and it is used in the system for a long time. The
 Hai> official 29 and 30 versions do not include this patch, and
 Hai> trying to compile new linuxthreads for arm results in a missing
 Hai> header file in sysdeps (there are header files for all platforms
 Hai> except for arm). Therefore, I had to stick to my old version.

Ok. linuxthreads-old (the default) afaik works on ARM.

 Hai> Regarding the gcc patch, you are probably right. If I'll copy
 Hai> the mentioned patch file to the 4.2.4 subdirectory, does the
 Hai> Makefile automatically take all patch files in it?

Yes, all *.patch

 Hai> Regarding the find, I know I am using an older distribution, but
 Hai> in any case,?I recommend using the other alternative instead of
 Hai> -delete anyways to support all versions (it doesn't damage newer
 Hai> versions).

Agreed.

 Hai> I also tried to build with gcc 4.3.2, and halted on the same
 Hai> problem exactly in crtstuff.c.  I found a patch to workaround
 Hai> this, but then I get the emptry sections warnings from the
 Hai> linker.

Strange. gcc 4.3.x works fine here on ARM. Maybe your problems are
caused by your uclibc changes?

 Hai> I've attached this patch for your reference, although I
 Hai> don't think it is right.  ? I also attached my .config file for
 Hai> your reference and hopefully you'll find something I didn't
 Hai> configure right... Please note that I had to hack the .config to
 Hai> force using 2.6.18 headers (I don't think there is any relation
 Hai> to this because with the mentioned patch, the toolchain
 Hai> completed to build).  ? Thanks a lot, Hai.

Why would you want to use so old kernel headers? Didn't the make
headers_install target only get added to the kernel in 2.6.19?

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2009-04-27  7:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 14:36 [Buildroot] Buildroot comments and questions Hai Shalom
2009-04-26 20:10 ` Peter Korsgaard
     [not found]   ` <a4413b2d0904262349m133ac037t4c42095240c1256a@mail.gmail.com>
2009-04-27  7:47     ` Peter Korsgaard [this message]

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=87ljpmh71l.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