This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: cd crosstool-ng ; make menuconfig

From: ANDY KENNEDY <ANDY dot KENNEDY at adtran dot com>
To: Anthony Foiani <anthony dot foiani at gmail dot com>
Cc: "Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>, "crossgcc at sourceware dot org" <crossgcc at sourceware dot org>
Date: Wed, 1 Jun 2011 18:28:17 +0000
Subject: RE: cd crosstool-ng ; make menuconfig
References: <F9C551623D2CBB4C9488801D14F864C60286DC@ex-mb1.corp.adtran.com> <201106010045.24919.yann.morin.1998@anciens.enib.fr> <F9C551623D2CBB4C9488801D14F864C6029731@ex-mb1.corp.adtran.com> <BANLkTimN8uJ_e1wASux+FGXJ-JmbqzwHaw@mail.gmail.com>

<snip> 
> This actually sounds close to your needs; you might consider this
> mode
> instead of trying to shoehorn ct-ng into each project. One of the
> few
> reasons for keeping different versions of ct-ng around would be to
> deal with older code bases, but even that seems like a stretch.

The ultimate goal is exactly that.  We will be keeping around the
exact release of ctng for just that purpose.  So, we'll end up with
a boatload of ctng releases in the dl dir of the build server.  I
know that we _should_ be able to reproduce any flavor of toolchain
we build with ctng with ctng (supposed to be two "with ctng"'s
there), but I want to be safe.

Andy

Follow-Ups:
- Re: cd crosstool-ng ; make menuconfig
  - From: Anthony Foiani

References:
- RE: cd crosstool-ng ; make menuconfig
  - From: ANDY KENNEDY
- Re: cd crosstool-ng ; make menuconfig
  - From: Anthony Foiani

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]