| AWARE [SYSTEMS] | Imaging expertise for the Delphi developer | |||||||
![]() |
TIFF and LibTiff Mailing List Archive | |||||||
LibTiff Mailing List
TIFF and LibTiff Mailing List Archive Contact
The TIFF Mailing List Homepage |
Thread1996.11.07 23:05 "Re: Unresolved __eprintf", by Adam P JenkinsJames Crawford Ralston writes: > Excerpts from dl.tiff: 7-Nov-96 Unresolved __eprintf Keith > Arbuckle@vx.com (1814*) > > > ... I tried to link in the [static] tiff library with ImageMagick which > > produced the error message "Unresolved: __eprintf". After using the > > "ld -y" command to determine where the unresolved was being used. I > > discovered it was being called from several places in the tiff library, > > with tif_read.c being one of those files. > > The __eprintf function comes from libgcc.a. If you let gcc call ld on > your behalf, it should do the right thing. > > I'm not sure how unresolved references to it popped up in your > libtiff.a, though; gcc should produce static libraries which have no > specific dependencies on gcc. Perhaps someone who is more intimately > familiar with Irix can comment. The assert macro, as defined in gcc's header files, uses __eprintf. gcc uses a different set of header files than the SGI native compiler. That's probably how __eprintf got into the object files. Adam |
|||||||