public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Peter Barada <peter@baradas.org>
Cc: drow@mvista.com,  zack@codesourcery.com,  pinskia@physics.uc.edu,
	 wilson@tuliptree.org,  gcc@gcc.gnu.org
Subject: Re: cross-compilation documentation
Date: Mon, 23 Jun 2003 12:20:00 -0000	[thread overview]
Message-ID: <3EF67F7F.3070805@kegel.com> (raw)
In-Reply-To: <20030623025952.CE49398DFD@baradas.org>

Peter Barada wrote:
> glibc1: ${GLIBC_BUILDDIR1} glibc1-fix
> 	export PATH=${INSTALL_DIR}/bin:${HOST_INSTALL_DIR}/bin:$$PATH; \
> 	cd ${GLIBC_BUILDDIR1}; \
> 	CC=${TARGET}-gcc AR=${TARGET}-ar RANLIB=${TARGET}-ranlib \
> 	${GLIBC_SOURCE_PATH}/configure --host=${TARGET} \
> 	--prefix=/usr --without-cvs --disable-sanity-checks \
> 	--with-headers=${INSTALL_DIR}/${TARGET}/include ; \
> 	make cross-compiling=yes install_root=${INSTALL_DIR}/${TARGET} prefix="" install-headers
> 
> glibc1-fix:
> 	mkdir -p ${INSTALL_DIR}/${TARGET}/include/gnu ; \
> 	touch ${INSTALL_DIR}/${TARGET}/include/gnu/stubs.h ; \
> 	cp -f ${GLIBC_SOURCE_PATH}/include/features.h ${INSTALL_DIR}/include/features.h
> 
> 
> But this fragment *requires* a cross-compiler to build it.

Hmm.  That's odd.  I do almost the same thing, but I don't require a cross-compiler.
Maybe the step you're missing is the following kludge:
         make sysdeps/gnu/errlist.c
         mkdir -p stdio-common
         touch stdio-common/errlist-compat.c
That goes between the configure and the make of glibc, and keeps anything
real from being compiled by the install-headers.

> ... I'm hoping people see that there *is* a
> problem making blanket statements that "its perfectly normal to insist
> that the system headers be installed when building the bootstrap".

Indeed.

> I don't know what the solution is, but I trying to figure out the
> minimal set of changes necessary to make a(or most/if not
> all -linux toolchains).  That way hopefully with the next release of
> gcc/glibc I won't have to go through this mess all over again...

I think the powers that be are suggesting that the fix for gcc-3.5
might be to separate out the building of libgcc from the building of
gcc.  Hmm, and then separate out the building of anything in glibc
that requires libgcc into a separate target.  Then we could do
    make bootstrap gcc without libgcc
    make whatever parts of glibc that don't depend on libgcc
    make real gcc including libgcc
    make whatever parts of glibc that depend on libgcc
- Dan

-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

  reply	other threads:[~2003-06-23  4:08 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18  0:36 Dan Kegel
2003-06-18 14:58 ` Joel Sherrill
2003-06-22 17:10   ` Dan Kegel
2003-06-19  0:00 ` Jim Wilson
2003-06-22 17:12   ` Dan Kegel
2003-06-22 17:19     ` Andrew Pinski
2003-06-22 17:21       ` Dan Kegel
2003-06-22 17:35       ` Peter Barada
2003-06-22 17:50         ` Andrew Pinski
2003-06-22 17:56           ` Jan-Benedict Glaw
2003-06-22 18:07           ` Zack Weinberg
2003-06-22 20:15             ` Dan Kegel
2003-06-22 20:27               ` Zack Weinberg
2003-06-22 20:36                 ` Peter Barada
2003-06-22 21:10                   ` Daniel Jacobowitz
2003-06-23  3:06                     ` Dan Kegel
2003-06-23  4:08                       ` Jan-Benedict Glaw
2003-06-23  4:22                         ` Dan Kegel
2003-06-23  9:10                     ` Peter Barada
2003-06-23 12:20                       ` Dan Kegel
2003-06-23 12:15                         ` Peter Barada
2003-06-23 12:20                           ` Dan Kegel [this message]
2003-06-23 14:14                             ` Peter Barada
2003-06-23 15:38                               ` Hans-Peter Nilsson
2003-06-23 16:04                                 ` Dan Kegel
2003-06-23 16:11                                   ` Hans-Peter Nilsson
2003-06-23 15:57                               ` Dan Kegel
2003-06-23 13:01                           ` Daniel Jacobowitz
2003-06-23 14:14                             ` Peter Barada
2003-06-23 14:50                               ` Daniel Jacobowitz
2003-06-23 14:10                       ` Daniel Jacobowitz
2003-06-22 18:41           ` Daniel Jacobowitz
2003-06-22 17:30     ` Jan-Benedict Glaw
  -- strict thread matches above, loose matches on Subject: below --
2004-05-29  6:25 Dan Kegel
2004-05-29  6:57 ` Zack Weinberg
2004-06-01 16:35   ` Dan Kegel
2004-06-01 17:38 ` Dave Korn
2004-06-01 17:45   ` Peter Barada
2003-06-22 17:43 Dara Hazeghi
2003-06-22 17:49 ` Jan-Benedict Glaw
2003-06-22 17:49 ` Andrew Pinski
2003-06-22 17:53   ` Jan-Benedict Glaw
2003-06-24  5:26     ` Jim Wilson
2003-06-22 19:36   ` Dara Hazeghi
2003-06-27 12:13     ` Gerald Pfeifer
2001-11-13 16:21 Cross-compilation documentation Joseph S. Myers

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=3EF67F7F.3070805@kegel.com \
    --to=dank@kegel.com \
    --cc=drow@mvista.com \
    --cc=gcc@gcc.gnu.org \
    --cc=peter@baradas.org \
    --cc=pinskia@physics.uc.edu \
    --cc=wilson@tuliptree.org \
    --cc=zack@codesourcery.com \
    /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).