This is the mail archive of the crossgcc@sources.redhat.com 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] |
* William A. Gatliff <bgat@saturn.billgatliff.com> on Wed, Oct 17, 2001: > > Oooh, let's constrain ourselves to the 2.95.x series, ok? I'm still > reeling with the differences in 3.x... :^) As far as libgcc is conerned, I think the only major change is the ability to build a shared libgcc. > > I think I'm correct in saying that the "all-gcc" target stops before > building libiberty, but after building libgcc, no? > Yes, it's best to think of libgcc as being part of the C compiler proper, but like you stated earlier, it's possible to compile source files even without libgcc being available (usually system software does this). It's even possible to link applications w/out libgcc, as long as your code doesn't invoke any intrinsics (and that can be pretty difficult to arrange :). M. R.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |