problem configuring cross

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

   Date: Wed, 21 Oct 1998 13:28:03 +0200
   From: Ola Liljedahl <olli@enea.se>

   Stan Shebs wrote:
   > 
   > Although Cygnus is heavily involved with egcs, we don't "own" it.
   > This means that our changes to egcs have to go through the same
   > approval process as everyone else does.  However, we also make many of
   > our own releases, such as cygwin32 betas, and specialized releases for
   > our semiconductor partners, such as ARM and Hitachi, that they
   > subsequently make available to the public.  Those releases usually
   > have bits in them that you won't find in egcs or in other FSF
   > releases, and those bits are usually (though not always) marked as
   > "CYGNUS LOCAL".

   You must have a great archiving system with all those different
   variants, versions and releases.

Just plain old CVS; but the repository is huge! - we've had versions
of GNU and other software in there since 1991.  Just for fun I counted
the number of release tags on the top-level configure script, since
it's been in all of our GNU releases since the beginning, and there
were about 700.  Yes campers, that means we average several releases
per *week*; Cygnus has a lot of clients getting versions of GNU
customized for their particular needs.

That's also why our maintainers are usually pretty fanatical about
patch quality and portability; if a new piece of code doesn't run
everywhere, it quickly causes a huge nightmare.

							Stan
________________________________________________
To get help for the crossgcc list, send mail to
crossgcc-request@cygnus.com with the text 'help'
(without the quotes) in the body of the message.