From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] 2009.05-rc1: fix dmraid build
Date: Thu, 07 May 2009 09:34:30 +0200 [thread overview]
Message-ID: <871vr1e589.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090506121110.46c105f8@bandomeer.europe.flane.local> (Olaf Rempel's message of "Wed\, 6 May 2009 12\:11\:10 +0200")
>>>>> "Olaf" == Olaf Rempel <razzor@kopf-tisch.de> writes:
Olaf> Hi,
Olaf> the dmraid build seems to be broken.
Olaf> On x86 it bails out with missing include files.
Olaf> I think it's some sort of $FOO_SUBDIR issue, but I couldn't find/fix it.
Olaf> After adding the "include" dir to CFLAGS it compiles, but fails during linking.
Olaf> Disabling parallel build (I'm using -j2) fixed that too.
Hmm, can you be a bit more specific? I see that the dmraid build
system is broken, as lib and tools race against each other with
parallel builds. I've fixed that in git - But other than that it
builds for me (x86-64 host, x86-core2 target).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-05-07 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 10:11 [Buildroot] 2009.05-rc1: fix dmraid build Olaf Rempel
2009-05-07 7:34 ` Peter Korsgaard [this message]
2009-05-07 9:57 ` Olaf Rempel
2009-05-07 10:15 ` Peter Korsgaard
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=871vr1e589.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