public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: timlee@netcom.com.DELETE-THIS.BIT (Timothy J. Lee)
To: help-gcc@gnu.org
Subject: Re: NFS mounted gcc on multiple OS versions
Date: Tue, 30 Nov 1999 23:28:00 -0000	[thread overview]
Message-ID: <809qjd$agq$1@nntp6.atl.mindspring.net> (raw)
Message-ID: <19991130232800.NYesSi0Gv0NXqTbOOf2CAdzlnlp0L4KDII61b7QWyHQ@z> (raw)
In-Reply-To: <7vsmec$7jt$1@nnrp1.deja.com>

kevin_collins@my-deja.com writes:
|I have gcc installed under /usr/local on Solaris 2.5.1. and /usr/local
|is exported to several other machines running 2.5.1, 2.6 and 2.7 (tho
|not currently used). I am  in the process of upgrading our source
|management software from PVCS 5.3 to PVCS 6.5. PVCS 6.5 does not run on
|Solaris 2.5.1.
|
|I am getting a large amount of 'parse error' messages when I try
|building from a Solaris 2.7 system. I have determined that this problem
|is due to the fact that gcc creates "fixed" versions of system include
|files to resolve ANSI-C issues.
|
|I would like to be able to just create the "fixed" include files for 2.6
|and 2.7 and let gcc know about them, but I am not sure if it is possible
|for gcc to deal with these files for multiple versions of the OS.

Would copying all of the 2.5.1 (stock, not gcc-fixed) include files and
libraries into /usr/local/sparc-sun-solaris2.5.1/{include,lib} do what
you want? That would have the effect of getting gcc to always use the
include files and libraries for 2.5.1 -- effectively making gcc a cross
compiler when run on a 2.6 or 7 system (host 2.6 or 7, target 2.5.1).
Binaries made by that gcc should theoretically run on 2.5.1 or any
newer Solaris on the same type of processor.

Longer term, you may want to separate the shared executable / library
directories (while giving the newer OSes access to the older OSes'
directories so that they can execute them in binary compatibility mode).

--
------------------------------------------------------------------------
Timothy J. Lee                                                   timlee@
Unsolicited bulk or commercial email is not welcome.             netcom.com
No warranty of any kind is provided with this message.

  reply	other threads:[~1999-11-30 23:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-04 11:33 kevin_collins
1999-11-09 10:58 ` Timothy J. Lee [this message]
1999-11-30 23:28   ` Timothy J. Lee
1999-11-30 23:28 ` kevin_collins

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='809qjd$agq$1@nntp6.atl.mindspring.net' \
    --to=timlee@netcom.com.delete-this.bit \
    --cc=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).