Re: [foxboro] cc compiler library linking errors
- From: Darryl Bond <dbond@xxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Wed, 23 Jul 2003 14:42:56 +1000
Here is a section of a Makefile of mine that works for every Foxboro
program I have written
# LFLAGS to build on Foxboro box
LFLAGS= -L/usr/ccs/lib -L$(OPENWINHOME)/lib -L/usr/lib -lnsl \
-lX11 -lxhi -lfox -lfoxfdr -lfoxlc -lhi -lfoxapi -lposix4
-lhistory -lm
Regards
Darryl Bond
Jones, Charles R. (Chuck) wrote:
>Are there any C programmers still out there? I'm having trouble with the
>Fox libraries when I compile my program. I use the form:
>
>cc filename.c -o filename -lfox -lnsl -lsocket
>
>The program gathers bits of information from several blocks and prints the
>data out in a report. All I needed to do was to add one more line
>containing one more number to the report. The C code was embarrassingly
>simple and I'm certain that it is not the code, especially since the error
>messages tell me so:
>
>Undefined symbol first referenced in file
>timer_create /usr/lib/libfox.so
>sigwaitinfo /usr/lib/libfox.so
>timer_settime /usr/lib/libfox.so
>ld: fatal: Symbol referencing errors. No output written
>
>The file -- libfox.so -- is an ELF 32-bit MSB dynamic lib SPARC Version 1,
>etc -- according to the file command. So, I can't just scan through it for
>clues using the vi editor.
>
>Really, I've done this before. It's just that I can't recall doing it since
>the update to the operating system back in late 1999 (remember the Y2K
>hoax?). I'm open to suggestion from anyone familiar with this type of
>scenario. My current guess is that some of the subsequent library files
>have been moved from their former locations.
>
>Chuck Jones
>Refinery Automation Technologist
>Tate & Lyle North America -- Lafayette South Plant
>765.477.5324 - Office | 877.536.9219 - Pager
>
>
>
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
- References:
- [foxboro] cc compiler library linking errors
- From: Jones, Charles R. (Chuck)
Other related posts:
- » Re: [foxboro] cc compiler library linking errors
- » Re: [foxboro] cc compiler library linking errors
- » Re: [foxboro] cc compiler library linking errors
- [foxboro] cc compiler library linking errors
- From: Jones, Charles R. (Chuck)