| 1 |
drobbins@g.o wrote: |
| 2 |
|
| 3 |
> On Sat, Jan 27, 2001 at 06:07:37PM +0100, Achim Gottinger wrote: |
| 4 |
> |
| 5 |
> > Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the |
| 6 |
> > minimum required stuff, we can even place gcc and binutils in separate TARGET |
| 7 |
> > dependent packages, so it should be possible to make one cd that gives you |
| 8 |
> > the ability to build for all our intel targets. |
| 9 |
> |
| 10 |
> OK, so we have two install CD's: |
| 11 |
> |
| 12 |
> 1. the standard packages CD (for people who want a quick install) |
| 13 |
> |
| 14 |
> /images/sys.tbz2 |
| 15 |
> /packages/<all your .tbz2 packages here> |
| 16 |
> |
| 17 |
> 2. the autobuild CD (for people who want to build everything from scratch) |
| 18 |
> On this CD, the directory structure looks something like this: |
| 19 |
> |
| 20 |
> /portage |
| 21 |
> #profiles contains lists of packages to install for various types of |
| 22 |
> #systems, such as "desktop", "server", "router", etc. |
| 23 |
> /portage/profiles |
| 24 |
> /portage/distfiles |
| 25 |
> |
| 26 |
> # the i486, i586 and i686 build packages contain gcc and binutils |
| 27 |
> # compiled for their respective targets... question, is this necessary |
| 28 |
> # since you can access these sub-architectures with compile-time switches. |
| 29 |
> # this just changes the name of /usr/lib/gcc-lib/i686-pc-linux-gnu, or |
| 30 |
> # are there more extensive changes besides this? How about binutils? |
| 31 |
> # If there are no differences in generated code, we can have a single |
| 32 |
> # build.tbz2 instead of three. |
| 33 |
|
| 34 |
Hmm, maybe we can use i486 as build-host and make cross-compilers/binutils for all |
| 35 |
other targets. But I prefere |
| 36 |
a solution without crocc-compilers that works without tricks. |
| 37 |
|
| 38 |
> |
| 39 |
> /gentoo/i486/build.tbz2 |
| 40 |
> /gentoo/i586/build.tbz2 |
| 41 |
> /gentoo/i686/build.tbz2 |
| 42 |
> |
| 43 |
> > Well there is no base-system that needs to be rebuild. Instead the |
| 44 |
> > corresponding non statically linked packages get build and merged over or can |
| 45 |
> > be unmerged if not required after the build. |
| 46 |
> |
| 47 |
> Again, why are these static? I'm guessing so that you don't need to include |
| 48 |
> certain libraries? |
| 49 |
|
| 50 |
Because I want to use this set of packages for porting and for building gentoo on |
| 51 |
other linux-distros. And this is |
| 52 |
the simplest way |
| 53 |
|
| 54 |
> Wouldn't build.tbz2 be smaller with dynamic linking? |
| 55 |
|
| 56 |
Yes, but it is only temporary there and gets replaced with the shared version or can |
| 57 |
get unmerged. |
| 58 |
|
| 59 |
> |
| 60 |
> |
| 61 |
|
| 62 |
Bye Achim |
| 63 |
|
| 64 |
> |
| 65 |
> Best Regards, |
| 66 |
> |
| 67 |
> -- |
| 68 |
> Daniel Robbins <drobbins@g.o> |
| 69 |
> President/CEO http://www.gentoo.org |
| 70 |
> Gentoo Technologies, Inc. |
| 71 |
> |
| 72 |
> _______________________________________________ |
| 73 |
> gentoo-dev mailing list |
| 74 |
> gentoo-dev@g.o |
| 75 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |
Archives