public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ifc USE flag, fortran support and some general notes about multi-compiler support
Date: Wed, 25 Aug 2004 15:25:10 -0500	[thread overview]
Message-ID: <1093465509.25119.4.camel@localhost> (raw)
In-Reply-To: <412CF14E.7040106@ifm.liu.se>

[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]

On Wed, 2004-08-25 at 15:06, Anton Starikov wrote:

<snip>

> So, has it sense to think about implementing some abstract 
> multi-compiler support? at least for Fortran guys.
> But generally, probably, it could be just let say "minor compiler 
> support", which means, for C and F you still have gcc and g77 (gfortran 
> in future)  as a main compiler of the system, but you can also choose 
> some kind of minor compiler. Now it almost work in such way with ICC.
> ICC behaves just as some kind of minor compiler and some software that 
> can be compiled with ICC will be compiled with icc.

This should be added to gcc-config, so it can support independent
language compilers.

<snip>

> So, there is coming in mind some idea of different approach. Transparent 
>   level of multicompiler support. OK, it is not granted. 
> But...scientific guys use to live in not granted world :)
> It probably looks like:
> 1) You have two more flags: "altcc" and "altfc"
> 2) somewhere (in make.conf for ex) you have specify :
> ALTCC=C-compiler-which-I-really-like
> ALTCXX=C++-compiler-which-I-really-like
> ALTF77=F77-compiler-which-I-really-like
> ALTF90=F90-compiler-which-I-really-like
> ALTCFLAGS="optimize-it-to-make-a-rocket"
> ALTF77LAGS="optimize-it-to-make-a-rocket"

Yep. Some alternative compilers have their own configuration files for
compiler-specific flags, however. They should still draw the generic
flags from make.conf, such as CFLAGS, CXXFLAGS or FFLAGS (fortran).

<snip>

> Ebuild just check for "altcc" and "altfc" flags in USE, if they are, it 
> force configure or whatever else to use it. Thats done. Of course you 
> can't be sure that it will be compiled on all possible alternative 
> compilers, but you can try :)

Nah, USE isn't the right place for it. Ebuilds should respect the
environment variables selecting compilers, such as CC, CXX, FC and so
forth. The USE flags should be for other things, e.g. patches that are
required for a specific compiler to work.
-- 
Donnie Berkholz
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-25 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 20:06 [gentoo-dev] ifc USE flag, fortran support and some general notes about multi-compiler support Anton Starikov
2004-08-25 20:25 ` Donnie Berkholz [this message]
2004-08-25 20:28   ` Donnie Berkholz
2004-08-25 21:26     ` Anton Starikov
2004-08-25 22:59       ` Donnie Berkholz
2004-08-26  0:31         ` Anton Starikov
2004-08-26  0:47         ` Anton Starikov
2004-08-25 21:12   ` Anton Starikov
2004-08-25 23:46 ` Olivier Fisette
2004-08-26  0:37   ` Anton Starikov

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=1093465509.25119.4.camel@localhost \
    --to=spyderous@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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