This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: linker options for hpux
- To: thomas dot porschberg at osp-dd dot de
- Subject: Re: linker options for hpux
- From: law at redhat dot com
- Date: Thu, 18 Oct 2001 03:48:38 -0600
- cc: gcc-help at gcc dot gnu dot org
- Reply-To: law at redhat dot com
In message <15303.15342.733678.486038@porschberg.osp-dd.de>you write:
> Which linker options should I give the HPUX linker to build the executable
> for gcc3.0.1?
>
> two examples:
> hp-sport(pberg):/proj/paloma/src/oci/ImportCustomerOrder> make
> gcc +eh -Wl,-L/home/oracle/lib -L/home/oracle/rdbms/lib -L/usr/loca
> l/lib
> -L/proj/standards/lib -L/proj/paloma/lib -o ImportCustomerOrder CustomerOr
> der_E
> xc.o CustomerOrder.o Configure.o ReadAuftragASC.o WriteResultASC.o OrtStras
> senPr
> fg.o MatchCodePrfg.o HandlingI.o Mainloop.o DBAction.o DBAction_Exc.o File_
> Exc.o
> Socket_Exc.o main.o -lpaloma_class_gnu -lccardgicc_class_gnu -loci_class_
> gnu
> -lclntsh -l:libcl.a -l:librt.sl -lpthread -l:libnss_dns.1 -l:libdld.sl -ls
> tdc++
>
> /usr/ccs/bin/ld: Unsatisfied symbols:
> __builtin_va_start (code)
> collect2: ld returned 1 exit status
This is actually an indication that GCC is picking up /usr/include/stdarg.h
or /usr/include/varargs.h instead of its own private copies.
Make sure nothing does -I/usr/include when compiling programs with GCC.
jeff