[gentoo-dev] sys-build

[gentoo-dev] sys-build

[Achim Gottinger]

Hi Guys,

Today I build a working sys-build package that includes all the packages
in sys-build, baselayout and portage.
This means we now have an environment to which we can chroot and build
everithing else within. (I tested all sys-packages with success, so the
rest should work too).
I used exactly the same dir-layout as in the corresponding sys-*
packages, so nothink statically linked remains
after the corresponding packages are merged over.
It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be,
maybe it can be reduced to around 100MB. :-/.
What can we do now?

1. This build sytsem can be placed on a bootable cd together with the
sources and the ebuild-tree. We can then
unpack the build.tbz2 instead of the sys.tbz2 to our target partition,
chroot there and build everything.

2. We can use this as a starting point for ports to other platforms. It
should be possible to build the sys-build stuff
if we have ports of spython and portage and gcc-2.95.2 on the
base-system.

3. There is no more need for the other sys-categories now so these
packages can be moved to the other categories now. So we are one step
closer to a minimum runtime system now.

Feedback please

Achim**

Re: [gentoo-dev] sys-build

[drobbins]

On Sat, Jan 27, 2001 at 04:29:53PM +0100, Achim Gottinger wrote:
> Hi Guys,
> 
> Today I build a working sys-build package that includes all the packages
> in sys-build, baselayout and portage.
> This means we now have an environment to which we can chroot and build
> everithing else within. (I tested all sys-packages with success, so the
> rest should work too).
> I used exactly the same dir-layout as in the corresponding sys-*
> packages, so nothink statically linked remains
> after the corresponding packages are merged over.
> It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be,
> maybe it can be reduced to around 100MB. :-/.
> What can we do now?
> 
> 1. This build sytsem can be placed on a bootable cd together with the
> sources and the ebuild-tree. We can then
> unpack the build.tbz2 instead of the sys.tbz2 to our target partition,
> chroot there and build everything.

OK, I'm very confused, so please explain how this works.  Also, what 
prevented us from just extracting sys.tbz2 and chrooting to /mnt/gentoo
and building everything?

When you say building everything, do you mean *re*building the base system
as well?  Does this system use a separate build partition and target 
partition, or just a single root partition mounted at /mnt/gentoo?

And I assume that sys-build has nothing extra.  For example, no star, no
iptables, etc?  OK, I'm looking at /usr/portage/sys-build as I should
have done in the first place.  Beautiful :)  But please explain how the
build process is supposed to work (maybe by typing in example command-line
build install).

> 2. We can use this as a starting point for ports to other platforms. It
> should be possible to build the sys-build stuff
> if we have ports of spython and portage and gcc-2.95.2 on the
> base-system.
> 
> 3. There is no more need for the other sys-categories now so these
> packages can be moved to the other categories now. So we are one step
> closer to a minimum runtime system now.
> 
> Feedback please

Is sys-build becoming our "official" install method?  Or will you continue
to make a sys.tbz2?  Or just a build.tbz2 and then all other packages will
be in their own individual package tarballs and we'll add the new system
profile (server,desktop,etc) capability to portage to help decide which 
.tbz2's to install.  This feature isn't ready for -rc4 but it can be for
-final.

Lots of questions this time,

Best Regards,


-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] sys-build

[Achim Gottinger]

drobbins@gentoo.org wrote:

> On Sat, Jan 27, 2001 at 04:29:53PM +0100, Achim Gottinger wrote:
> > Hi Guys,
> >
> > Today I build a working sys-build package that includes all the packages
> > in sys-build, baselayout and portage.
> > This means we now have an environment to which we can chroot and build
> > everithing else within. (I tested all sys-packages with success, so the
> > rest should work too).
> > I used exactly the same dir-layout as in the corresponding sys-*
> > packages, so nothink statically linked remains
> > after the corresponding packages are merged over.
> > It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be,
> > maybe it can be reduced to around 100MB. :-/.
> > What can we do now?
> >
> > 1. This build sytsem can be placed on a bootable cd together with the
> > sources and the ebuild-tree. We can then
> > unpack the build.tbz2 instead of the sys.tbz2 to our target partition,
> > chroot there and build everything.
>
> OK, I'm very confused, so please explain how this works.  Also, what
> prevented us from just extracting sys.tbz2 and chrooting to /mnt/gentoo
> and building everything?

Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the
minimum required stuff, we can even
place gcc and binutils in separate TARGET dependent packages, so it should be
possible to make one cd that
gives you the ability to build for all our intel targets.

>
>
> When you say building everything, do you mean *re*building the base system
> as well?  Does this system use a separate build partition and target
> partition, or just a single root partition mounted at /mnt/gentoo?

Well there is no base-system that needs to be rebuild. Instead the
corresponding non statically linked packages
get build and merged over or can be unmerged if not required after the build.

All is done on one partition, no fiddeling around with crosscompilers is
required.

>
>
> And I assume that sys-build has nothing extra.  For example, no star, no
> iptables, etc?  OK, I'm looking at /usr/portage/sys-build as I should
> have done in the first place.  Beautiful :)  But please explain how the
> build process is supposed to work (maybe by typing in example command-line
> build install).

Ok imagine you have a list of required packages that is sorted in order of
dependencies
and a filestructure on the cd that corresponds to that under /usr/portage

---------------------------------------
mkdir /mnt/gentoo/usr/portage
mount /dev/cdrom /mnt/gentoo/usr/portage
cp package-list /mnt/gentoo/root
vi /mnt/gentoo/etc/make.conf
chroot /mnt/gentoo
source /etc/profile
cd /usr/portage
for i in 'cat /root/package-list''
do
    ebuild $i merge
done
---------------------------------------


>
>
> > 2. We can use this as a starting point for ports to other platforms. It
> > should be possible to build the sys-build stuff
> > if we have ports of spython and portage and gcc-2.95.2 on the
> > base-system.
> >
> > 3. There is no more need for the other sys-categories now so these
> > packages can be moved to the other categories now. So we are one step
> > closer to a minimum runtime system now.
> >
> > Feedback please
>
> Is sys-build becoming our "official" install method?

Hmm, no but I think we can offer source-cd this as an alternative to the
package-cd.
We can put spython and the pkgmerge part of portage on our bootcd-img on the
package-cd and provide
several profile lists and later a package-management-gui.

> Or will you continue
> to make a sys.tbz2?  Or just a build.tbz2 and then all other packages will
> be in their own individual package tarballs and we'll add the new system
> profile (server,desktop,etc) capability to portage to help decide which
> .tbz2's to install.  This feature isn't ready for -rc4 but it can be for
> -final.

Maybe we make an rc5 for that.

>
>
> Lots of questions this time,

Hope all answerd.

Achim~~

>
>
> Best Regards,
>
> --
> Daniel Robbins                                  <drobbins@gentoo.org>
> President/CEO                                   http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] sys-build

[Andreas Schweitzer]

On Sat, Jan 27, 2001 at 06:07:37PM +0100, Achim Gottinger wrote:
> drobbins@gentoo.org wrote:
> 
> > On Sat, Jan 27, 2001 at 04:29:53PM +0100, Achim Gottinger wrote:
> > > Hi Guys,
> > >
> > > Today I build a working sys-build package that includes all the packages
> > > in sys-build, baselayout and portage.

Sounds very interesting.
Where can I find it to try it out ?

> > > This means we now have an environment to which we can chroot and build
> > > everithing else within. (I tested all sys-packages with success, so the
> > > rest should work too).
> > > I used exactly the same dir-layout as in the corresponding sys-*
> > > packages, so nothink statically linked remains
> > > after the corresponding packages are merged over.
> > > It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be,
> > > maybe it can be reduced to around 100MB. :-/.
> > > What can we do now?
> > >
> > > 1. This build sytsem can be placed on a bootable cd together with the
> > > sources and the ebuild-tree. We can then
> > > unpack the build.tbz2 instead of the sys.tbz2 to our target partition,
> > > chroot there and build everything.
> >
> > OK, I'm very confused, so please explain how this works.  Also, what

me too :-)

> > prevented us from just extracting sys.tbz2 and chrooting to /mnt/gentoo
> > and building everything?
> 
> Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the
> minimum required stuff, we can even
> place gcc and binutils in separate TARGET dependent packages, so it should be
> possible to make one cd that
> gives you the ability to build for all our intel targets.

But /mnt/gentoo will contain the compiler etc. ?
And it will be overwritten ?
Or at least some of the binaries in /mnt/gentoo ?

> > And I assume that sys-build has nothing extra.  For example, no star, no
> > iptables, etc?  OK, I'm looking at /usr/portage/sys-build as I should
> > have done in the first place.  Beautiful :)  But please explain how the
> > build process is supposed to work (maybe by typing in example command-line
> > build install).
> 
> Ok imagine you have a list of required packages that is sorted in order of
> dependencies
> and a filestructure on the cd that corresponds to that under /usr/portage
> 
> ---------------------------------------
> Mkdir /mnt/gentoo/usr/portage
> mount /dev/cdrom /mnt/gentoo/usr/portage
> cp package-list /mnt/gentoo/root
> vi /mnt/gentoo/etc/make.conf
> chroot /mnt/gentoo
> source /etc/profile
> cd /usr/portage
> for i in 'cat /root/package-list''
> do
>     ebuild $i merge
> done
> ---------------------------------------

A bit clearer. But again, this requires binaries in /mnt/gentoo
that you put there from unpacking build.tbz2 - right ?

And there are no sources in build.tbz2 ?
Those should also be on the CDROM ?
Alternatively, include wget and rsync, and the sources can
be grabbed from the net (if somebody wants to get them from there).

Still a newbie to gentoo - but it looks promising !

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/

Re: [gentoo-dev] sys-build

[drobbins]

On Sat, Jan 27, 2001 at 06:07:37PM +0100, Achim Gottinger wrote:

> Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the
> minimum required stuff, we can even place gcc and binutils in separate TARGET
> dependent packages, so it should be possible to make one cd that gives you
> the ability to build for all our intel targets.

OK, so we have two install CD's:

1. the standard packages CD (for people who want a quick install)

	/images/sys.tbz2
	/packages/<all your .tbz2 packages here>

2. the autobuild CD (for people who want to build everything from scratch)
	On this CD, the directory structure looks something like this:

	/portage
	#profiles contains lists of packages to install for various types of
	#systems, such as "desktop", "server", "router", etc.
	/portage/profiles
	/portage/distfiles
	
	# the i486, i586 and i686 build packages contain gcc and binutils
	# compiled for their respective targets... question, is this necessary
	# since you can access these sub-architectures with compile-time switches.
	# this just changes the name of /usr/lib/gcc-lib/i686-pc-linux-gnu, or
	# are there more extensive changes besides this?  How about binutils?
	# If there are no differences in generated code, we can have a single
	# build.tbz2 instead of three.

	/gentoo/i486/build.tbz2
	/gentoo/i586/build.tbz2
	/gentoo/i686/build.tbz2

> Well there is no base-system that needs to be rebuild. Instead the
> corresponding non statically linked packages get build and merged over or can
> be unmerged if not required after the build.

Again, why are these static?  I'm guessing so that you don't need to include
certain libraries?  Wouldn't build.tbz2 be smaller with dynamic linking?

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] sys-build

[Achim Gottinger]

Andreas Schweitzer wrote:

> On Sat, Jan 27, 2001 at 06:07:37PM +0100, Achim Gottinger wrote:
> > drobbins@gentoo.org wrote:
> >
> > > On Sat, Jan 27, 2001 at 04:29:53PM +0100, Achim Gottinger wrote:
> > > > Hi Guys,
> > > >
> > > > Today I build a working sys-build package that includes all the packages
> > > > in sys-build, baselayout and portage.
>
> Sounds very interesting.
> Where can I find it to try it out ?

Not yet uploaded.

>
>
> > > > This means we now have an environment to which we can chroot and build
> > > > everithing else within. (I tested all sys-packages with success, so the
> > > > rest should work too).
> > > > I used exactly the same dir-layout as in the corresponding sys-*
> > > > packages, so nothink statically linked remains
> > > > after the corresponding packages are merged over.
> > > > It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be,
> > > > maybe it can be reduced to around 100MB. :-/.
> > > > What can we do now?
> > > >
> > > > 1. This build sytsem can be placed on a bootable cd together with the
> > > > sources and the ebuild-tree. We can then
> > > > unpack the build.tbz2 instead of the sys.tbz2 to our target partition,
> > > > chroot there and build everything.
> > >
> > > OK, I'm very confused, so please explain how this works.  Also, what
>
> me too :-)
>
> > > prevented us from just extracting sys.tbz2 and chrooting to /mnt/gentoo
> > > and building everything?
> >
> > Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the
> > minimum required stuff, we can even
> > place gcc and binutils in separate TARGET dependent packages, so it should be
> > possible to make one cd that
> > gives you the ability to build for all our intel targets.
>
> But /mnt/gentoo will contain the compiler etc. ?

Yes you unpack build.tbz2 to /mnt/gentoo first.

> And it will be overwritten ?

Yes because build.tbz2 contains reduced to a minimum required and statically
linked versions of packages .
I used static linking because I want to be able to build the sys-build packages in
one step without manually
copying shared libraries from the system I build on.
This offers the possibility to build you packages on every linux-system with a
recent enogh kernel.
You just have to unpack build.tbz2 to a temp dir mount the source-cd or a
source-partition, chroot there
and build as described below.

>
> Or at least some of the binaries in /mnt/gentoo ?
>
> > > And I assume that sys-build has nothing extra.  For example, no star, no
> > > iptables, etc?  OK, I'm looking at /usr/portage/sys-build as I should
> > > have done in the first place.  Beautiful :)  But please explain how the
> > > build process is supposed to work (maybe by typing in example command-line
> > > build install).
> >
> > Ok imagine you have a list of required packages that is sorted in order of
> > dependencies
> > and a filestructure on the cd that corresponds to that under /usr/portage
> >
> > ---------------------------------------
> > Mkdir /mnt/gentoo/usr/portage
> > mount /dev/cdrom /mnt/gentoo/usr/portage
> > cp package-list /mnt/gentoo/root
> > vi /mnt/gentoo/etc/make.conf
> > chroot /mnt/gentoo
> > source /etc/profile
> > cd /usr/portage
> > for i in 'cat /root/package-list''
> > do
> >     ebuild $i merge
> > done
> > ---------------------------------------
>
> A bit clearer. But again, this requires binaries in /mnt/gentoo
> that you put there from unpacking build.tbz2 - right ?

Yes

>
>
> And there are no sources in build.tbz2 ?

No

>
> Those should also be on the CDROM ?
> Alternatively, include wget and rsync, and the sources can
> be grabbed from the net (if somebody wants to get them from there).

wget is on the boot-cd image, rsync not yes. All the required binaries and all
kernel-network/nfs modules to
set-up a network enviroment are on the bootcd-image. So it should not be to
difficult to add that option too.

achim~

>
>
> Still a newbie to gentoo - but it looks promising !
>
> 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/
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] sys-build

[Achim Gottinger]

drobbins@gentoo.org wrote:

> On Sat, Jan 27, 2001 at 06:07:37PM +0100, Achim Gottinger wrote:
>
> > Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the
> > minimum required stuff, we can even place gcc and binutils in separate TARGET
> > dependent packages, so it should be possible to make one cd that gives you
> > the ability to build for all our intel targets.
>
> OK, so we have two install CD's:
>
> 1. the standard packages CD (for people who want a quick install)
>
>         /images/sys.tbz2
>         /packages/<all your .tbz2 packages here>
>
> 2. the autobuild CD (for people who want to build everything from scratch)
>         On this CD, the directory structure looks something like this:
>
>         /portage
>         #profiles contains lists of packages to install for various types of
>         #systems, such as "desktop", "server", "router", etc.
>         /portage/profiles
>         /portage/distfiles
>
>         # the i486, i586 and i686 build packages contain gcc and binutils
>         # compiled for their respective targets... question, is this necessary
>         # since you can access these sub-architectures with compile-time switches.
>         # this just changes the name of /usr/lib/gcc-lib/i686-pc-linux-gnu, or
>         # are there more extensive changes besides this?  How about binutils?
>         # If there are no differences in generated code, we can have a single
>         # build.tbz2 instead of three.

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.

>
>         /gentoo/i486/build.tbz2
>         /gentoo/i586/build.tbz2
>         /gentoo/i686/build.tbz2
>
> > Well there is no base-system that needs to be rebuild. Instead the
> > corresponding non statically linked packages get build and merged over or can
> > be unmerged if not required after the build.
>
> Again, why are these static?  I'm guessing so that you don't need to include
> certain libraries?

Because I want to use this set of packages for porting and for building gentoo on
other linux-distros. And this is
the simplest way

> Wouldn't build.tbz2 be smaller with dynamic linking?

Yes, but it is only temporary there and gets replaced with the shared version or can
get unmerged.

>
>

Bye Achim

>
> Best Regards,
>
> --
> Daniel Robbins                                  <drobbins@gentoo.org>
> President/CEO                                   http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] sys-build

[drobbins]

On Sat, Jan 27, 2001 at 06:57:23PM +0100, Achim Gottinger wrote:
> >
> >         # the i486, i586 and i686 build packages contain gcc and binutils
> >         # compiled for their respective targets... question, is this necessary
> >         # since you can access these sub-architectures with compile-time switches.
> >         # this just changes the name of /usr/lib/gcc-lib/i686-pc-linux-gnu, or
> >         # are there more extensive changes besides this?  How about binutils?
> >         # If there are no differences in generated code, we can have a single
> >         # build.tbz2 instead of three.

> 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.
If the user sets the CHOST in /etc/make.conf to i686-pc-linux-gnu before
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.

> > Again, why are these static?  I'm guessing so that you don't need to include
> > certain libraries?

> Because I want to use this set of packages for porting and for building
> gentoo on other linux-distros. And this is the simplest way

OK; I guess dynamic libraries could cause some problems on some other distros.
Though I haven't had problems chrooting to a location with shared libraries before,
even if I'm switching between two libc's.

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] sys-build

[Andreas Schweitzer]

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/

Re: [gentoo-dev] sys-build

[Andreas Schweitzer]

> > And it will be overwritten ?
> 
> Yes because build.tbz2 contains reduced to a minimum required and statically
> linked versions of packages .

OK - I got it ! :-)
Sounds right.

> > Alternatively, include wget and rsync, and the sources can
> > be grabbed from the net (if somebody wants to get them from there).
> 
> wget is on the boot-cd image, rsync not yes. All the required binaries and all
> kernel-network/nfs modules to
> set-up a network enviroment are on the bootcd-image. So it should not be to
> difficult to add that option too.

I'm just thinking of people like me, who don't have a CD burner, but
instead a fast internet connection. So I prefer to do network
installs. Then I only need to download something like
(generally speaking) boot floppies and some sort of images.
In this case I would think build.tbz2

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/

Re: [gentoo-dev] sys-build

[Achim Gottinger]

Andreas Schweitzer wrote:

> > > And it will be overwritten ?
> >
> > Yes because build.tbz2 contains reduced to a minimum required and statically
> > linked versions of packages .
>
> OK - I got it ! :-)
> Sounds right.
>
> > > Alternatively, include wget and rsync, and the sources can
> > > be grabbed from the net (if somebody wants to get them from there).
> >
> > wget is on the boot-cd image, rsync not yes. All the required binaries and all
> > kernel-network/nfs modules to
> > set-up a network enviroment are on the bootcd-image. So it should not be to
> > difficult to add that option too.
>
> I'm just thinking of people like me, who don't have a CD burner, but
> instead a fast internet connection. So I prefer to do network
> installs. Then I only need to download something like
> (generally speaking) boot floppies and some sort of images.
> In this case I would think build.tbz2
>

Hmm, for this case we need a soultion that mounts the cd-boot-image from another
partition or via nfs/dhcp instead of the cd because it requires around 16MB at the
moment.

achim~

>
> 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/
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] sys-build

[Achim Gottinger]

Andreas Schweitzer wrote:

> 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.

:-)))))))) Yes it is. I tested it.
I used
CHOST=i686-pc-linux-gnu
CFLAGS=-O2 -mpentiumpro -march=pentiumpro

I builded bison,flex and getext.
Then I was ready for binutils/gcc.

If I add bison,flex and gettext to sys-build we can imediately start building
binutils/gcc for the desired host.


>
>
> > 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 ?

I think it's better to wait for gcc-2.95.3. We used pgcc last year and had troubles
with a few packages.
But that time we compiled everything with -O6. :-)
If you want, make a modified package and post it here, we add it to the cvs-tree
and you can test how it works.

achim~

>
>
> > 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/
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev

Re: [gentoo-dev] sys-build

[Achim Gottinger]

drobbins@gentoo.org wrote:

> On Sat, Jan 27, 2001 at 06:57:23PM +0100, Achim Gottinger wrote:
> > >
> > >         # the i486, i586 and i686 build packages contain gcc and binutils
> > >         # compiled for their respective targets... question, is this necessary
> > >         # since you can access these sub-architectures with compile-time switches.
> > >         # this just changes the name of /usr/lib/gcc-lib/i686-pc-linux-gnu, or
> > >         # are there more extensive changes besides this?  How about binutils?
> > >         # If there are no differences in generated code, we can have a single
> > >         # build.tbz2 instead of three.
>
> > 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.
> If the user sets the CHOST in /etc/make.conf to i686-pc-linux-gnu before
> 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.
>
> > > Again, why are these static?  I'm guessing so that you don't need to include
> > > certain libraries?
>
> > Because I want to use this set of packages for porting and for building
> > gentoo on other linux-distros. And this is the simplest way
>
> OK; I guess dynamic libraries could cause some problems on some other distros.
> Though I haven't had problems chrooting to a location with shared libraries before,
> even if I'm switching between two libc's.

I checked dependencies of sys-build packages and detected that no other packages are
required to provide the shared libraries needed. The only packages that require other
libs are bash and spython but these are both statical linked in sys-apps/sys-devel so no
problem.

I will make the -static link flag optional controllable via USE sys-build-static

achim~

>
>
> --
> Daniel Robbins                                  <drobbins@gentoo.org>
> President/CEO                                   http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev