Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] SVN Rev 19269 won't build
Date: Mon, 30 Jul 2007 10:44:06 +0200	[thread overview]
Message-ID: <20070730084405.GB22956@aon.at> (raw)
In-Reply-To: <1D637BC976FEB2D52024B231@[192.168.83.121]>

On Fri, Jul 27, 2007 at 06:08:41PM +0200, Claas Hilbrecht wrote:
>--Am Freitag, 27. Juli 2007 16:08 +0200 Bernhard Fischer 
><rep.dot.nop@gmail.com> schrieb:
>
>> Alright. Last minute change after testing it.
>> r19278 Works For Me (tm)
>
>Somewhat better, but not quite right I assume. After entering the 
>menuconfig dialog and exit it without changing anything I just type make. 
>After I while I get these errors:
>
>mv tmp-specs specs
>echo | 
>/home/babel/buildroot/0.9.29/buildroot_org/buildroot/toolchain_build_i386/gcc-4.2.0-initial/./gcc/xgcc 
>-B/home/babel/buildroot/0.9.29/buildroot_org/buildroot/toolchain_build_i386/gcc-4.2.0-initial/./gcc/ 
>-B/home/babel/buildroot/0.9.29/buildroot_org/buildroot/build_i386/staging_dir/usr/i386-linux-uclibc/bin/ 
>-B/home/babel/buildroot/0.9.29/buildroot_org/buildroot/build_i386/staging_dir/usr/i386-linux-uclibc/lib/ 
>-isystem 
>/home/babel/buildroot/0.9.29/buildroot_org/buildroot/build_i386/staging_dir/usr/i386-linux-uclibc/include 
>-isystem 
>/home/babel/buildroot/0.9.29/buildroot_org/buildroot/build_i386/staging_dir/usr/i386-linux-uclibc/sys-include 
>-E -dM - | \
>          sed -n -e 's/^#define \([^_][a-zA-Z0-9_]*\).*/\1/p' \
>                 -e 's/^#define \(_[^_A-Z][a-zA-Z0-9_]*\).*/\1/p' | \
>          sort -u > tmp-macro_list
>/bin/sh 
>/home/babel/buildroot/0.9.29/buildroot_org/buildroot/toolchain_build_i386/gcc-4.2.0/gcc/../move-if-change 
>tmp-macro_list macro_list
>echo timestamp > s-macro_list
>The directory that should contain system headers does not exist:
> 
>/home/babel/buildroot/0.9.29/buildroot_org/buildroot/toolchain_build_i386/uClibc_dev//usr/include
>make[2]: *** [stmp-fixinc] Error 1
>make[2]: Leaving directory 
>`/home/babel/buildroot/0.9.29/buildroot_org/buildroot/toolchain_build_i386/gcc-4.2.0-initial/gcc'
>make[1]: *** [all-gcc] Error 2
>make[1]: Leaving directory 
>`/home/babel/buildroot/0.9.29/buildroot_org/buildroot/toolchain_build_i386/gcc-4.2.0-initial'
>make: *** 
>[/home/babel/buildroot/0.9.29/buildroot_org/buildroot/toolchain_build_i386/gcc-4.2.0-initial/.compiled] 
>Error 2
>
>I think if make menuconfig required some user changes I should at least get 
>a warning that I'm trying to shot myself.
>
>PS: Sorry to bother you with these error, but I tried to get a clean build 
>to setup another build system. Getting a svn rev working out of the box is 
>my first goal.

Well, this works for my config and did work before these PROJECT stuff
went in. Perhaps the author of that "PROJECT" thing (Ulf?) would know..
sorry

      reply	other threads:[~2007-07-30  8:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27  7:58 [Buildroot] SVN Rev 19269 won't build Claas Hilbrecht
2007-07-27 10:37 ` Bernhard Fischer
2007-07-27 10:53   ` Claas Hilbrecht
2007-07-27 12:30     ` Bernhard Fischer
2007-07-27 13:42       ` Claas Hilbrecht
2007-07-27 14:08         ` Bernhard Fischer
2007-07-27 16:08           ` Claas Hilbrecht
2007-07-30  8:44             ` Bernhard Fischer [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=20070730084405.GB22956@aon.at \
    --to=rep.dot.nop@gmail.com \
    --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