From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: buildroot@busybox.net
Subject: [Buildroot] Gcc broken on OS X
Date: Tue, 17 Jul 2007 11:33:26 +0300 [thread overview]
Message-ID: <469C7ED6.90402@cs.helsinki.fi> (raw)
Hi,
Some recent changes have also broken gcc build:
cp
/private/tmp/buildroot-devel/toolchain_build_i686/gcc-4.1.2/gcc/../fixincludes/README-fixinc
include/README
chmod a+r include/README
echo timestamp > stmp-int-hdrs
make[3]: *** No rule to make target `/usr/bin/i686-linux-uclibc-as',
needed by `stamp-as'. Stop.
make[2]: *** [all-gcc] Error 2
make[1]: *** [all] Error 2
make: ***
[/private/tmp/buildroot-devel/toolchain_build_i686/gcc-4.1.2-final/.compiled]
Error 2
Looks like an absolute path using $prefix has crept in from somewhere.
-- hl
reply other threads:[~2007-07-17 8:33 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=469C7ED6.90402@cs.helsinki.fi \
--to=holindho@cs.helsinki.fi \
--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