public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Scott Ballantyne <sdb@ssr.com>
To: gcc-help@gcc.gnu.org
Subject: Problem with includes during build
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <20000220182502.25676.qmail@ssr.com> (raw)
Message-ID: <20000401000000.f3HamVOM4sCA1651zSDUn9hEi3c-V7Gab2RRtTyUJFM@z> (raw)

I'm trying to build gcc 2.95.2 on sparc-unknown-openbsd2.6, which
ships with gcc 2.95.1.

It seems that there is a problem with fixincludes, which modifies
stdio.h to reference __gnuc_va_list and _BSD_DUMMY_VA_LIST, but does
not provide for a definition for either of these symbols. This causes
make bootstrap to fail during the tmplibgcc2.a portion of the build,
specifically when trying to generate the _eprintf.o file.

They are defined in _srcdir_/gcc/ginclude/stdarg.h, but this directory
is not included in the -I paths for xgcc.

I'm not sure if this is my error, or a problem in this distribution
which needs to be corrected, or what a good work around would be for
me at the present time, since I haven't followed the progress of the
fixinc work.

I'm wondering also, if fixinc is not doing more work than is optimal
for OpenBSD2.6...

Thanks in advance for your suggestions.

sdb

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-20 10:25 Scott Ballantyne [this message]
2000-04-01  0:00 ` Scott Ballantyne

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=20000220182502.25676.qmail@ssr.com \
    --to=sdb@ssr.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).