public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: holme@pos.megalink.net
Cc: gnu@gnu.org, help-gcc@gnu.org
Subject: Re: GCC 2.95 and Solaris 2.7 (using GCC 2.72 built on solaris 2.5) problem
Date: Fri, 18 Feb 2000 16:37:00 -0000	[thread overview]
Message-ID: <200002190035.BAA31167@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <200002182337.SAA13379@mescaline.gnu.org>

>   1) Was I right to rename (and make a new empty) gcc include
>   directory before installing?

No. gcc produces those at installation time for a purpose, namely, to
fix known errors in the system header files. This means you cannot
lightly move a gcc installation from one operating system to another -
even if they are relatively similar, such as Solaris 2.5 and Solaris
7. In theory, re-running 'fixincludes' might help, but that is only an
option for experts.

>   2) Why am I having a problem with varargs.h?

I don't know. From your message it was not clear what *exactly* the
error message was you where getting, or what commands had been
producing it.

I recommend that you install a binary version of gcc 2.95.2 on your
system instead; follow the binaries link at the gcc.gnu.org.

Regards,
Martin

WARNING: multiple messages have this Message-ID
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: holme@pos.megalink.net
Cc: gnu@gnu.org, help-gcc@gnu.org
Subject: Re: 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: <200002190035.BAA31167@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <20000401000000.RbI1IaEP-yu1y-weDrTFx6UV7d7Yq0bW4dHI4Ez4ILU@z> (raw)
In-Reply-To: <200002182337.SAA13379@mescaline.gnu.org>

>   1) Was I right to rename (and make a new empty) gcc include
>   directory before installing?

No. gcc produces those at installation time for a purpose, namely, to
fix known errors in the system header files. This means you cannot
lightly move a gcc installation from one operating system to another -
even if they are relatively similar, such as Solaris 2.5 and Solaris
7. In theory, re-running 'fixincludes' might help, but that is only an
option for experts.

>   2) Why am I having a problem with varargs.h?

I don't know. From your message it was not clear what *exactly* the
error message was you where getting, or what commands had been
producing it.

I recommend that you install a binary version of gcc 2.95.2 on your
system instead; follow the binaries link at the gcc.gnu.org.

Regards,
Martin

  reply	other threads:[~2000-02-18 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-18 15:37 holme
2000-02-18 16:37 ` Martin v. Loewis [this message]
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=200002190035.BAA31167@loewis.home.cs.tu-berlin.de \
    --to=martin@loewis.home.cs.tu-berlin.de \
    --cc=gnu@gnu.org \
    --cc=help-gcc@gnu.org \
    --cc=holme@pos.megalink.net \
    /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).