From: Andreas Schweitzer <andy@physast.uga.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] sys-build
Date: Sat Jan 27 13:00:02 2001 [thread overview]
Message-ID: <20010127150002.A45222@bender.physast.uga.edu> (raw)
In-Reply-To: <20010127113309.B16142@cvs.gentoo.org>; from drobbins@gentoo.org on Sat, Jan 27, 2001 at 11:33:09AM -0700
After understanding this now :-) I dare to answer on this one.
> > Hmm, maybe we can use i486 as build-host and make cross-compilers/binutils
> > for all other targets. But I prefere a solution without crocc-compilers that
> > works without tricks.
>
> When you say "all other targets", are you talking about
> i386,486,pentium,pentiumpro and K6? If so, a basic i486 build.tbz2 will work.
I think that should be correct.
> If the user sets the CHOST in /etc/make.conf to i686-pc-linux-gnu before
You mean in /etc/make.defaults ?
Plus setting CFLAGS.
Something for the not-next-release : Include the PGCC patches from
www.goof.com/pgcc ?
> building the system, then the system should compile an i686 gcc and i686
> binutils, correct? I don't think you'd need a cross-compiler, would you?
> We're not talking about different architectures here -- just different CPU
> variations.
One build.tbz2 for Intel should be enough.
Cheers
Andreas
--
Department of Physics & Astronomy and Center for Simulational Physics
University of Georgia Phone ++1 (706) 542 5043
Athens, GA 30602-2451 Fax ++1 (706) 542 2492
USA http://dilbert.physast.uga.edu/~andy/
next prev parent reply other threads:[~2001-01-27 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 8:58 [gentoo-dev] sys-build Achim Gottinger
2001-01-27 10:04 ` drobbins
2001-01-27 10:36 ` Achim Gottinger
2001-01-27 11:00 ` Andreas Schweitzer
2001-01-27 11:16 ` Achim Gottinger
2001-01-27 13:04 ` Andreas Schweitzer
2001-01-27 13:57 ` Achim Gottinger
2001-01-27 11:13 ` drobbins
2001-01-27 11:26 ` Achim Gottinger
2001-01-27 11:34 ` drobbins
2001-01-27 13:00 ` Andreas Schweitzer [this message]
2001-01-27 14:04 ` Achim Gottinger
2001-01-27 14:27 ` Achim Gottinger
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=20010127150002.A45222@bender.physast.uga.edu \
--to=andy@physast.uga.edu \
--cc=gentoo-dev@gentoo.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