public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pgarrone@linuxmail.org
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/8180: --without-headers configure option not working
Date: Wed, 09 Oct 2002 17:16:00 -0000 [thread overview]
Message-ID: <20021010001404.2938.qmail@sources.redhat.com> (raw)
>Number: 8180
>Category: bootstrap
>Synopsis: --without-headers configure option not working
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Oct 09 17:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: pgarrone@linuxmail.org
>Release: gcc-3.2
>Organization:
>Environment:
building an sh4 xcompiler on a mandrake linux intel system
>Description:
The file gcc/configure does not set inhibit_libc if --without-headers is set, as this translates to --with-headers=no. So the bootstrap fails in compilation.
This is my own personal patch, which I urge you to study closely.
>How-To-Repeat:
host=i686-pc-linux-gnu
build=$host
target=sh-linux-gnu
../../gcc/configure \
--target=$target \
--prefix=$prefix \
--host=$host \
--build=$build \
-v \
--without-headers \
--enable-languages=c \
--with-cpu=sh4 \
--disable-threads
make all install
>Fix:
diff -r -C 5 gcc-3.2.orig/gcc/configure gcc-3.2/gcc/configure
*** gcc-3.2.orig/gcc/configure Sat Jun 29 10:20:11 2002
--- gcc-3.2/gcc/configure Thu Oct 10 09:08:54 2002
***************
*** 6787,6803 ****
# inhibit_libc
# If this is using newlib, then define inhibit_libc in LIBGCC2_CFLAGS.
# This prevents libgcc2 from containing any code which requires libc
# support.
! inhibit_libc=
! if test x$host != x$target && test x$with_headers = x; then
! inhibit_libc=-Dinhibit_libc
! else
! if test x$with_newlib = xyes; then
! inhibit_libc=-Dinhibit_libc
! fi
fi
# When building gcc with a cross-compiler, we need to adjust things so
# that the generator programs are still built with the native compiler.
--- 6787,6807 ----
# inhibit_libc
# If this is using newlib, then define inhibit_libc in LIBGCC2_CFLAGS.
# This prevents libgcc2 from containing any code which requires libc
# support.
!
! # If --without-headers was an option, then define inhibit_libc.
! # But if inhibit_libc is previously defined, leave it.
! if test x${inhibit_libc} = x
! then
! if ( ( test x$host != x$target && test x$with_headers = x) \
! || ( test x${with_headers} = xno ) \
! || ( test x$with_newlib = xyes ) \
! ); then
! inhibit_libc=-Dinhibit_libc
! fi
fi
# When building gcc with a cross-compiler, we need to adjust things so
# that the generator programs are still built with the native compiler.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-10-10 0:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 17:16 pgarrone [this message]
2003-05-14 9:36 Dara Hazeghi
2003-05-14 10:53 giovannibajo
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=20021010001404.2938.qmail@sources.redhat.com \
--to=pgarrone@linuxmail.org \
--cc=gcc-gnats@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).