public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] sys-build
Date: Sat Jan 27 11:26:05 2001	[thread overview]
Message-ID: <3A730C03.4197A8D3@gottinger.de> (raw)
In-Reply-To: 20010127111228.A15830@cvs.gentoo.org

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




  reply	other threads:[~2001-01-27 18:25 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 [this message]
2001-01-27 11:34         ` drobbins
2001-01-27 13:00           ` Andreas Schweitzer
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=3A730C03.4197A8D3@gottinger.de \
    --to=320095285153-0001@t-online.de \
    --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