public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Patrick Begou <Patrick.Begou@univ-grenoble-alpes.fr>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: two gccs
Date: Sun, 17 Oct 2021 07:44:15 -0700	[thread overview]
Message-ID: <CAPF-yOboZ7CN3m5Yzfaer7-eNBW64W4pssPgCF0FiX1YKZBjSg@mail.gmail.com> (raw)
In-Reply-To: <db3b305a-641e-ab88-28f9-be52f0703853@univ-grenoble-alpes.fr>

Patrick, are you referring to http://modules.sourceforge.net ?

(Not all build systems are especially happy with its use of LD_LIBRARY_PATH,
I think, fwiw.)

Bill,
can you describe your situation a little better?

- Dan

Patrick Begou via Gcc-help <gcc-help@gcc.gnu.org> schrieb am So., 17. Okt.
2021, 01:59:

> Le 17/10/2021 à 04:16, Bill Cunningham via Gcc-help a écrit :
> >     I am partially complete with a build of gcc-11.2.0. The thing is
> > that I need the system to recognize the gcc driver I am calling on. I
> > will also be working on two glibcs, but first thing first.
> >
> >     There is the system gcc, and the test gcc. Of course I can only
> > get the system gcc to work. Can the $PATH variable be changed to
> > access the test gcc, which btw, is not fully complete? Or can sym
> > links be used in a very skillful manner. I have read both these ways
> > can, somehow, be used. But I would think gcc runtime switches would
> > work. The system is considering these two gccs as different as their
> > triplets are different.
> >
> >
> To uses several flavor of a same software, have a look at the
> environment module. On my cluster It allows users to select gcc6, gcc9
> or gcc10 flavor easily in production, setting PATH,
> LD_LIBRARY_PATH,....etc. with "module load" / "module unload" commands.
>
> Patrick
>
>

  reply	other threads:[~2021-10-17 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-17  2:16 Bill Cunningham
2021-10-17  4:27 ` Dan Kegel
2021-10-17  8:58 ` Patrick Begou
2021-10-17 14:44   ` Dan Kegel [this message]
2021-10-17 15:57     ` Patrick Begou

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=CAPF-yOboZ7CN3m5Yzfaer7-eNBW64W4pssPgCF0FiX1YKZBjSg@mail.gmail.com \
    --to=dank@kegel.com \
    --cc=Patrick.Begou@univ-grenoble-alpes.fr \
    --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).