home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!munnari.oz.au!spool.mu.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!csn!qwerty-gw.fsl.noaa.gov!kestrel.fsl.noaa.gov!bear
- From: bear@kestrel.fsl.noaa.gov (Bear Giles)
- Subject: Re: Weird problem under Sun/C++
- Message-ID: <1992Dec30.235830.9504@fsl.noaa.gov>
- Sender: news@fsl.noaa.gov (USENET News System)
- Organization: Forecast Systems Labs, NOAA, Boulder, CO USA
- References: <1992Dec30.003304.4131@fsl.noaa.gov> <1992Dec30.182156.16470@fsl.noaa.gov>
- Date: Wed, 30 Dec 1992 23:58:30 GMT
- Lines: 23
-
- We finally found the problem.
-
- She was specifying the library with -lsage, thinking that the linker would
- use the copy of libsage.a in her current directory.
-
- Instead if was using an old copy in ~/lib which she had forgotten about.
- The procedure TupleFile::find() had recently changed (the fifth argument
- of the fourth argument (which was a pointer to a function) had just dropped
- a 'const' keyword).
-
- Therefore, her source and the _local_ library had matching member functions.
- Extracting the object file from the local library worked (although it caused
- 'multiply defined' error messages), but replacing the file in the local
- library didn't solve any problems.
-
- We only found the problem after replacing -lsage with libsage.a -- which
- suddenly worked! After switching back to -lsage and digging in the CC
- man page we found the linker flag which causes it to display the actual
- libraries used and discovered the old copy of the library.
-
-
- Bear Giles
- bear@fsl.noaa.gov
-