CVS commit: pkgsrc/lang/gfortran

[Ryo ONODERA]

Hello,

Hi,

You mean that all lang/gcc{3,4}* should be converted to
gcc4*-{c,c++,fortran,...}?
I feel that it is good idea, but I have no idea about how to convert them now.
I will try to convert them into separate packages.

gcc48 should have gcc48 in the name, so that when fortran based on gcc47
or gcc49 comes along, it can have a sensible name.

I see.
I will rename lang/gfortran to lang/gfortran48.
gcc48-gfortran is not so good, I feel.
Thank you.

it is Fortran compiler from GCC.
First of all, there's reason why Fortran compiler is not "gfortran" already.
The reason is that there is (or was at the time) no consistency across
platforms on which GCC package suits. This means that we have to do some
additional work on compiler selection in general _before_ we touch
anything else in this respect.
Second, if you want to procede with gfortran from GCC48, there exists
one already. It is part of lang/gcc48. I don't mind if you split it into
pieces, but please, do that in such a way that makes sense. In particular,
it should not raise a flow of questions on the difference.
This is another argument in favour of your gfortran package to have name
like "gcc48-gfortran".

Hi,
Thanks for your explanation.
I would like to create the following packages
lang/gcc48 ... meta package for all gcc 4.8.* compilers
lang/gcc48-cc++ ... C and C++ compilers (As far as I understand,
C and C++ compilers cannot be separated for gcc48)
lang/gcc48-gfortran ... Fortran 95/2003/2008 compiler
lang/gcc48-go ... Go language compiler

The go compiler is not buildable under NetBSD/amd64 current (gcc 4.5 and 4.8).

lang/gcc48-java ... Java compiler

The Java compiler does not work properly. ecj1 and some GCC Java programs
have gotten segfault (This segfault is observed with gcc47 too).

lang/gcc48-objc ... Objective C and C++ compiler
for gcc47 or earlier, gcc4?-c and gcc4?-c++ will be separated.
But I am not sure I can create separate packages...

I will commit gcc48, gcc48-cc++, gcc48-fortran, gcc48-objc,
and (new) gcc48-libs later.

--
Ryo ONODERA // ***@yk.rim.or.jp
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3

[Benny Siegert]

Post by Ryo ONODERA

lang/gcc48-go ... Go language compiler

The go compiler is not buildable under NetBSD/amd64 current (gcc 4.5 and 4.8).

What happens if you try? I think it is supposed to work, though I
admit I never tried.

--Benny.

[Ryo ONODERA]

Hello,

Hi,

You mean that all lang/gcc{3,4}* should be converted to
gcc4*-{c,c++,fortran,...}?
I feel that it is good idea, but I have no idea about how to convert them now.
I will try to convert them into separate packages.

gcc48 should have gcc48 in the name, so that when fortran based on gcc47
or gcc49 comes along, it can have a sensible name.

I see.
I will rename lang/gfortran to lang/gfortran48.
gcc48-gfortran is not so good, I feel.
Thank you.

it is Fortran compiler from GCC.
First of all, there's reason why Fortran compiler is not "gfortran" already.
The reason is that there is (or was at the time) no consistency across
platforms on which GCC package suits. This means that we have to do some
additional work on compiler selection in general _before_ we touch
anything else in this respect.
Second, if you want to procede with gfortran from GCC48, there exists
one already. It is part of lang/gcc48. I don't mind if you split it into
pieces, but please, do that in such a way that makes sense. In particular,
it should not raise a flow of questions on the difference.
This is another argument in favour of your gfortran package to have name
like "gcc48-gfortran".

Hi,
Thanks for your explanation.
I would like to create the following packages
lang/gcc48 ... meta package for all gcc 4.8.* compilers
lang/gcc48-cc++ ... C and C++ compilers (As far as I understand,
C and C++ compilers cannot be separated for gcc48)
lang/gcc48-gfortran ... Fortran 95/2003/2008 compiler
lang/gcc48-go ... Go language compiler
lang/gcc48-java ... Java compiler
lang/gcc48-objc ... Objective C and C++ compiler
for gcc47 or earlier, gcc4?-c and gcc4?-c++ will be separated.
But I am not sure I can create separate packages...

My plan is slightly changed, but my change is almost completed
(under NetBSD and OpenBSD).

If you find the problem, please tell me.

I am checking SunOS build.

--
Ryo ONODERA // ***@yk.rim.or.jp
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3