| Summary: | sci-libs/blas-atlas-3.8.1 - sh: -c: line 0: syntax error near unexpected token `2' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | thewtex <matthew.m.mccormick> |
| Component: | [OLD] Development | Assignee: | Gentoo Science Related Packages <sci> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
thewtex
2008-06-04 03:49:08 UTC
Ok, t looks like you don't define any compile flags for the fortran
compiler (FFLAGS). In this case, the ebuild will choose a default of
-O2. It seems that adding this flag without quotation marks
causes problems on your machine (it does not on mine). I've just added
single quotes to the default FFLAGS in the ebuild and this should
hopefully fix your problem (please re-sync and try again in an hour
or so).
Alternatively, and this is very likely what you would want to do
if you compile fortran code, you could define FFLAGS in your
make.conf. In the simplest case you could just add FFLAGS="${CFLAGS}"
which is what I do.
Best,
Markus
Thanks for the help. I tried syncing and adding FFLAGS, but it is still a no-go. The line is now ./xconfig -d s /var/tmp/paludis/sci-libs-blas-atlas-3.8.1/work/ATLAS/gentoo-build/../ -d b /var/tmp/paludis/sci-libs-blas -atlas-3.8.1/work/ATLAS/gentoo-build -C ac x86_64-pc-linux-gnu-gcc -F ac '-O2 -march=nocona -pipe -DNDEBUG' -C if gfortr an -F if '-O2 -march=nocona -pipe -DNDEBUG' -Ss pmake '$(MAKE) -j3' -Si cputhrchk 0 -b 64 Ahh, the problem is the -DNDEBUG which completely
confuses atlas' build system :-D
> an -F if '-O2 -march=nocona -pipe -DNDEBUG' -Ss pmake '$(MAKE) -j3' -Si
Where does it come from anyway since it is not in your make.conf
(paludis maybe?). Please try removing it and then
it should work.
Best,
Markus
Hazaa! You nailed it. I didn't keep my /etc/make.conf and /etc/paludis/bashrc in sync, which is why it might have been as obvious at first. Sorry about that. Maybe the ebuild can do more advanced parsing of compiler flags since atlas is so particular? Thanks for your help. (In reply to comment #4) > Hazaa! You nailed it. Excellent! > Maybe the ebuild can do more advanced parsing of compiler flags since atlas is > so particular? Compiler flags can be filtered if there are some known problems. However, users should never add pre-processor directives to their CFLAGS since their effect on individual packages is completely undefined. These directives should only be added by the packages' build systems or maybe the ebuild itself in certain cases. I am glad everything works for you again. Best, Markus |
