Package Details: g95 0.94-3

Git Clone URL: (read-only, click to copy)
Package Base: g95
Description: A stable, production Fortran 95 compiler available for multiple cpu architectures and operating systems
Upstream URL:
Licenses: GPL
Provides: g95
Submitter: None
Maintainer: drrossum
Last Packager: drrossum
Votes: 28
Popularity: 0.000000
First Submitted: 2006-11-19 15:06
Last Updated: 2016-03-23 22:51

Latest Comments

1 2 3 Next › Last »

lionliy commented on 2015-02-15 19:08

After downloaded and extracted the tarbar file, I successfully build the package file. However I meet following error message while installing the compiled package with "pacman -U "

error: failed to commit transaction (conflicting files)
g95: /lib exists in filesystem


After removed the line " mkdir -p ${pkgdir}/lib " , I rebuilt the package and installed it without any problem. This problem could be caused by the movement from /lib to /usr/lib . Just my wild guess.

lervag commented on 2013-06-07 15:13

This seems to be broken due to lack of the package() function. The package does not install any files.

vic.pozd commented on 2013-02-09 18:59

PSE correct md5sum for 32-bit version (663c7cc38029ab13f6d87ec21295e1fc)
Current version is: G95 (GCC 4.0.3 (g95 0.94!) Jan 17 2013)

duca commented on 2013-02-06 19:26

Thanks for the input, i will get back to speed with updates.

James-T commented on 2013-01-17 22:25

I'm not sure whether there's any solution other than "edit the PGKBUILD file before you try to install", but since development of g95 resumed a few months ago, there are new versions of the current build every few days so the MD5sums in PKGBUILD are not up to date.

duca commented on 2012-07-16 21:03

Thanks for the tips. Package is now updated.

AxPU commented on 2012-07-16 20:38

This package prevents the movement from /lib to /usr/lib that comes with the latest glibc update.

To solve this issue:

- Remove g95 ( "pacman -Rdd g95" this helps keeping all the packages that depend on g95 since we'll install it again later anyway)
- Update your system as described on the Arch Linux main page
- Reinstall g95

To reinstall g95 you have to rebuild the package. On 32 bit systems the current PKGBUILD creates some symlinks as the last step of the build process. Remove only (!) the three following lines from the skript before you run "makepkg -s":

ln -s /usr/lib/crti.o $startdir/pkg/lib
ln -s /usr/lib/crt1.o $startdir/pkg/lib
ln -s /usr/lib/crtn.o $startdir/pkg/lib

They can be found at the end of the PKGBUILD and are not needed anymore since all the /lib directory itself points to /usr/lib now,

Build and install normally, everything should work fine again.

The PKGBUILD file should be updated by the maintainer.

duca commented on 2010-09-21 15:20

Sorry for the delay in the response. Just updated

Anonymous comment on 2010-09-18 14:34

The package in website has been updated. The execute file is i686-pc-linux-gnu-g95 rather than i686-unknown-linux-gnu-g95.

Hope it can be fixed.

Eothred commented on 2010-07-29 07:23

It seems that CMake which I am using runs /usr/bin/c++ for linking instead of g95, which then uses the gcc 4.5 libraries. If I manually changed the config files to make use of g95 instead, it linked without errors. Now I just have to figure out how to change this in the CMakeLists.txt file. Anyone here knows?