This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


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

libgcc questions


The Mozilla project is looking at moving to using gcc 3.0 as their primary
compiler for downloadable Linux builds, but the requirement for libgcc is
one of the major obstacles that hasn't been dealt with yet.  After reading
the libgcc page, I wasn't clear as to what the best way of ensuring that the
user has a compatible version of the library installed.  It seemed like
distributing a copy of the shared library the binary is built with might be
an option, but if I read things correctly, you could get into trouble if
libc links against a different version of libgcc.  Although statically
linking the whole program is not viable due to the significant increase in
size of the binary, statically linking in just libc and libgcc might be a
possibility once Mozilla finishes relicensing - can gcc do that?

What's the best option?
Thanks,
Hampton



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