From: Mark Constable <markc@renta.net>
To: buildroot@busybox.net
Subject: [Buildroot] No gcc 4.4.2
Date: Fri, 23 Oct 2009 19:57:16 +1000 [thread overview]
Message-ID: <4AE17DFC.5020605@renta.net> (raw)
FWIW I tried to ignorantly force the use of gcc 4.4.2 but it seems
there needs to be deeper changes than what I am capable of...
/bin/sh: line 0: cd: /home/sources/buildroot/output/target/usr/lib/gcc-lib/i686-linux-uclibc/4.4.2: No such file or directory
make: [/home/sources/buildroot/output/target/usr/bin/gcc] Error 1 (ignored)
(cd /home/sources/buildroot/output/target/usr/lib && /home/sources/buildroot/output/staging/usr/bin/i686-linux-uclibc-strip --remove-section=.comment --remove-section=.note libstdc++.so.*.*.* > /dev/null 2>&1)
(cd /home/sources/buildroot/output/target/lib && /home/sources/buildroot/output/staging/usr/bin/i686-linux-uclibc-strip --remove-section=.comment --remove-section=.note libgcc_s*.so.*.*.* > /dev/null 2>&1)
make: [/home/sources/buildroot/output/target/usr/bin/gcc] Error 1 (ignored)
#
rm -f /home/sources/buildroot/output/target/usr/lib/*.la*
#rm -rf /home/sources/buildroot/output/target/share/locale /home/sources/buildroot/output/target/usr/info \
# /home/sources/buildroot/output/target/usr/man /home/sources/buildroot/output/target/usr/share/doc
# Work around problem of missing syslimits.h
if [ ! -f /home/sources/buildroot/output/target/usr/lib/gcc-lib/i686-linux-uclibc/4.4.2/include/syslimits.h ]; then \
echo "warning: working around missing syslimits.h"; \
cp -f /home/sources/buildroot/output/staging/lib/gcc-lib/i686-linux-uclibc/4.4.2/include/syslimits.h \
/home/sources/buildroot/output/target/usr/lib/gcc-lib/i686-linux-uclibc/4.4.2/include/; \
fi
warning: working around missing syslimits.h
cp: cannot stat `/home/sources/buildroot/output/staging/lib/gcc-lib/i686-linux-uclibc/4.4.2/include/syslimits.h': No such file or directory
make: *** [/home/sources/buildroot/output/target/usr/bin/gcc] Error 1
--markc
reply other threads:[~2009-10-23 9:57 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=4AE17DFC.5020605@renta.net \
--to=markc@renta.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.