From: Alexandre Oliva <aoliva@redhat.com>
To: "S, Saravanan (Saravanan)" <ssaravanan@lucent.com>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Re: builtin_va_start error !
Date: Mon, 23 Jul 2001 22:10:00 -0000 [thread overview]
Message-ID: <orn15vndn3.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <B0BADCAFF5CDD211989700805F85E3F60253C88A@II0015EXCH001U>
On Jul 19, 2001, "S, Saravanan (Saravanan)" <ssaravanan@lucent.com> wrote:
> Hello,
> We get this error when using
> gcc 2.95.2 on an HP-UX system 10.20 :
> /bin/ld: Unsatisfied symbols: __builtin_va_start (code).
This is supposed to be a macro in GCC 2.95.2. Sometimes, when a
translation unit #includes both <stdarg.h> and <varargs.h>, this kind
of error shows up.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
prev parent reply other threads:[~2001-07-23 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 23:51 S, Saravanan (Saravanan)
2001-07-23 22:10 ` Alexandre Oliva [this message]
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=orn15vndn3.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ssaravanan@lucent.com \
/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).