public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: holme@pos.megalink.net
To: gnu@gnu.org
Subject: GCC 2.95 and Solaris 2.7 (using GCC 2.72 built on solaris 2.5) problem
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200002182337.SAA13379@mescaline.gnu.org> (raw)
Message-ID: <20000401000000.MGiNEdQFBXuK80n4u8gQoLzN9wOzjOfNWIwdbmRvb6M@z> (raw)

GCC guru:

Last week I was having problems installing gcc2.95 on my solaris 2.7 release.
After many hours of effort, I found out that the gcc.2.7.2 include files built using
a previous relaease of Solaris (2.5) were the real problem. These include files did
not contain new information that had been added and the mixture invoked by the build
was incompatible.

So, I renamed the include directory and made an empty one for the gcc compiler's
override includes. Things were somewhat better - I got farther. Then I got the below
error - after some more brain-storming, I found out that I was compiling as 
ANSI_PROTOTYPES which should be fine and I was including varargs.h not stdargs.h.
However I am not baffled - I think I see `__builtin_va_alist' being defined, but
am not sure.

I have gone back and re-configured without the gcc include dir in place to no avail.
I have gone back to 2.7.2 and tried to recompile. The results are the same.

I have reviewed the install notes and errata - I see nothing alluding to my doing
anything wrong. I do NOT have a cc compiler, only the gcc.2.7.2 I made with solaris
2.5 on a classic (this is an ultra sparc - 64 bit machine).

So two questions:

  1) Was I right to rename (and make a new empty) gcc include directory before installing?
		(if so, consider adding to the release notes)

	/usr/local/lib/gcc-lib/sparc-sun-solaris2.5/2.7.2.2/include

  2) Why am I having a problem with varargs.h? - I would assume that a Solaris 2.7
     GCC 2.95 must have been built by someone by now.

Thanking you in advance for your help.

ray a holme (rah)



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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-18 15:37 holme [this message]
2000-02-18 16:37 ` Martin v. Loewis
2000-04-01  0:00   ` Martin v. Loewis
2000-04-01  0:00 ` holme

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=200002182337.SAA13379@mescaline.gnu.org \
    --to=holme@pos.megalink.net \
    --cc=gnu@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).