X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: LDD utility Date: 1 Dec 2005 12:45:45 GMT Lines: 34 Message-ID: <3v89jpF14m07nU2@news.dfncis.de> References: <200511302046 DOT jAUKkENl023371 AT envy DOT delorie DOT com> X-Trace: news.dfncis.de IEWWojVMk449TosERLhUEAAxX8ov1ysc+i8GIY4vBAh2HDc4A8grSgtweG X-Orig-Path: not-for-mail To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Radical NetSurfer wrote: > Linking in the standard libraries is automatic, and can sometimes > involve more than one libary... math, graphics, etc... No, it can't. Not in any recent version of DJGPP anyway. There's only *one* standard library in GCC. > ObjDump might be able to tell us what modules are expected, And what do you expect to learn from that? Please keep in mind that we're talking about *static* linking here, i.e. if you really want to know, you'll have to ask the linker to tell you about it, as it creates the binary. It does come with a manual, you know. Might as well be a little brave and read it. > but if I understand the process correctly, it does not actually > specify _from_ which library, by name, the linker needs to grab > the external references from.... No. But it has *you* specify all the libraries your program uses, manually, except for the two standard libraries (libc and libgcc). So if you don't know what you're doing, how do you expect anyone else, let alone a simple algorithm, figure it out? > It would make for a very interesting project, to create a utility, > even if human-assisted, that would take the C and C++ sources, > and actually list each individual external library reference, by > starting with the full name of the library, and whats needed from it. That's not interesting, that's utterly impossible. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.