public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Soucek, L. (Libor)" <lsoucek@ford.com>
To: gcc-help@gcc.gnu.org
Subject: Missing std lib. references
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200002242206.RAA11627@mailfw5.ford.com> (raw)
Message-ID: <20000401000000.4D32IdJG02jwbvXUlifKS3pxkaNJyYAVxTD8Bzu3XR4@z> (raw)

Hi!
I've encounter problem with linking on HP. I believe it is standard
stuff and I also believe it is correctly defined in linker command
(extract below). Do you have some suggestion about solving this problem
(probably very easy to fix if one know how)? I've asked all my
colleagues but they've never had that problem.

System status:

> uname -a
> HP-UX sl0473 B.10.20 A 9000/785 2007433980 two-user license

Compiler:

> g++ -v
> Reading specs from /ford/ptrs14/unix/loc/gcc-2.95/HP-UX/lib/gcc-lib/hppa2.0-hp-hpux10.20/2.95.2/specs
> gcc version 2.95.2 19991024 (release)

Linking command was:

> ***** Final linking of PET *****
> .........................
> echo "/sl0270/u/petsoft/PET_PATCH"
> 
> /ptrs14/unix/loc/gcc-2.95/HP-UX/bin/g++ -o pet.GNU \
> comphierdlg.o infer.o petemo.o petfile.o petgpp.o petmodel.o \
> petoption_CB.o petoption_scrn.o petdump.o pethelp.o mssg.o petedit.o \
> petview.o petmain.o petmacro.o petundo.o version.o \ 
>         -lm \
> -L/usr/ccs/lib -ll -ly \ >-L/ptrs14/unix/loc/gcc-2.95/HP-UX/lib/gcc-lib/hppa2.0-hp-hpux10.20/2.95.2 -lgcc \
> -lstdc++ -lg2c \
> -L/usr/dt/lib -lXm \
> -L/usr/lib -lXt -lX11 -lXm \
> -L/usr/contrib/X11R6/lib -lXaw  -lXmu
>   
> /usr/ccs/bin/ld: Unsatisfied symbols:
>    __builtin_va_start (code)
>    treeWidgetClass (data)
>    XawTreeForceLayout (code)
> collect2: ld returned 1 exit status
> make: *** [pet] Error 1

             reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-24 14:06 Soucek, L. (Libor) [this message]
2000-04-01  0:00 ` Soucek, L. (Libor)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200002242206.RAA11627@mailfw5.ford.com \
    --to=lsoucek@ford.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).