public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* 'ld' advice for RH6.2 to RH7.2 migration
@ 2003-07-17  1:09 Hudson, Thomas
  0 siblings, 0 replies; only message in thread
From: Hudson, Thomas @ 2003-07-17  1:09 UTC (permalink / raw)
  To: binutils


Hi all, 
	We're currently having problems with the version ld shipped with RH6.2 (2.9.5). These range from segfaults to "memory exhausted" errors. Our builds are huge, with link times on the order of 20 minutes on a top-end desktop machine with 2 gigs of ram. We currently are in the process of migration to RH7.2, but factors beyond our control require that we build on 6.2 (glibc21) and deploy on 7.2 (glibc22) in compatibility mode.

We have tried using a later version of binutils (2.13.2), and everything looked good until we noticed that many applications were suddenly unable to catch exceptions. It seems to happen mostly in apps that use dlopen. It is highly possible that these dlopen apps are composed of pieces built with the old linker and pieces built with the new. 

In investigating this, I have found that the RH7.2 version of 'ld' (2.11.90.8) has several supported emulations, most notably "elf_i386_glibc21". Any version of binutils I grab doesn't seem to have this emulation, though I have seen several patches floating around that seem related to this. I had hoped to build a newer version of binutils for 6.2 that could be deployed on 7.2 without problems, but it seems I need this emulation to get it to work correctly. 

Any ideas or suggestions?

Thanks,
Tomy

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-07-17  1:09 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-17  1:09 'ld' advice for RH6.2 to RH7.2 migration Hudson, Thomas

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).