Package Details: gmsh-docs 4.13.1-1

Git Clone URL: https://aur.archlinux.org/gmsh.git (read-only, click to copy)
Package Base: gmsh
Description: TXT, HMTL and PDF doc for Gmsh
Upstream URL: https://gmsh.info
Licenses: GPL-2.0-or-later
Submitter: S1G1
Maintainer: gborzi (carlosal1015, gpettinello)
Last Packager: carlosal1015
Votes: 62
Popularity: 0.010368
First Submitted: 2006-04-04 23:31 (UTC)
Last Updated: 2024-05-25 16:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 Next › Last »

gborzi commented on 2010-10-19 13:01 (UTC)

@Tempel please let me know if it works for you.

gborzi commented on 2010-10-19 12:51 (UTC)

Now the package should build fine without gcc-fortran and with lapack+blas. The problem was in CMakeLists.txt which has been patched. For Linux the configuration checked for Intel optimized lapack and not finding it, checked for atlas-lapack "believing" it was there even when just lapack+blas from extra is installed.

gborzi commented on 2010-10-19 11:55 (UTC)

I tried configuration (i.e. cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr ..) with lapack+blas from extra and without gcc-fortran. It is successful but strangely it gives these lines -- Found Blas(ATLAS) -- Found Lapack(ATLAS) Note: I run ldconfig after installing lapack+blas. But the compilation breaks down because it can't find libatlas. I have to make further investigation.

Tempel commented on 2010-10-18 23:01 (UTC)

Hmm, I have lapack and blas installed from the extra repository (and I reinstalled them to make sure they're not corrupt). So there must be differences between lapack in extra and atlas-lapack.

gborzi commented on 2010-10-18 16:38 (UTC)

I forgot to add that if you have gcc-fortran without lapack+blas the package builds, but at the configuration stage it warns that lapack was not found and some algorithms may not work.

gborzi commented on 2010-10-18 13:25 (UTC)

Hi Tempel, I have reproduced your error message on my system by uninstalling both gcc-fortran and lapack+blas. Perhaps your lapack library got corrupted, or you have non-standard lapack library (e.g. a vendor library) that isn't recognized by gmsh. With atlas-lapack the package builds fine.

Tempel commented on 2010-10-18 04:24 (UTC)

Really? For me, without gcc-fortran, it doesn't complete the cmake command, ending with "-- Configuring incomplete, errors occurred!" Earlier in the same step, it says "CMake Error: your Fortran compiler: "CMAKE_Fortran_COMPILER-NOTFOUND" was not found. Please set CMAKE_Fortran_COMPILER to a valid compiler path or name." To test this, I built it successfully, then cleared out the build directory, then removed gcc-fortran (no other packages were changed). After that, it would not build again. You're right that each .f has a corresponding .c. So could this problem be from vagaries in the cmake system? Is there any reason it might behave differently in two different systems?

gborzi commented on 2010-10-17 11:28 (UTC)

The package builds fine without gcc-fortran. Please note that for each .f source file there is a corresponding .c file in the source tree.

Tempel commented on 2010-10-17 03:31 (UTC)

It looks like gcc-fortran should be in the makedepends.

gborzi commented on 2010-06-24 11:34 (UTC)

In this update the arch is 'any' because this is a architecture-independent package and added "LC_ALL=C" before "make doc" to avoid a bug in texi2dvi.

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 Next › Last »