This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.


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

Re: problem configuring cross


jab3@hotmail.com (John Breen) writes:

> Sorry, but I have no idea what you're referring to when you say "CYGNUS 
> LOCAL".  I don't recall anything about it in the FAQ (oddly enough I did 
> just see a message on the egcs list talking about "CYGNUS LOCAL" wrt 
> java, but I still didn't understand what it meant).

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

*However*, before everybody goes ftping from, say, ARM, bear in mind
that specialized releases may not work for any but the target for
which they were produced!  There are always all kinds of different
changes going on in our development trunk, but once we make the
release branch for a particular configuration, that's all we test and
fix.  So if the ARM release falls on its face for m68k, or its mips
configuration files are messed up, you're on your own.

							Stan Shebs
							Cygnus Solutions
							shebs@cygnus.com

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