You are not logged in.
Hi!
In my makepkg.conf I have:
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"
#-- Exclusive: will only run on -march=x86-64
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CFLAGS="-march=amdfam10 -O2 -pipe" #Arch wiki says this
CXXFLAGS="${CFLAGS}"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j5"
and when I try to makepkg for smting (for example arora) I get:
...
g++ -c -m64 -pipe -march=x86-64 -mtune=generic -O2...
My gcc is 4.3.3. AMD Phenom II x4 910 processor.
Why is this two -march are different?
Offline
Do you get this for all packages or just that one?
Offline
It's the only one package. And it fails to build every time on different files with the same error. And if I just enter ./src/arora-build and run qmake && make it does compile ok.
The error example:
.obj/moc_settings.o: file not recognized: File truncated
collect2: ld returned 1 exit status
P.S. PKGBUILD is community/arora-git
Last edited by vit (2009-05-06 18:02:36)
Offline
It probably needs some sed usage to tell it to listen to CFLAGS.
Offline
Isn't it the packet ussue?
sed? Is it that GNU/sed (stream editor)? As I understand you I should use a command to replace wrong flags in input to flags I need?
Offline
I guess the PKGBUILD needs a fix the CFLAGS that build process sees. You can do that with sed (replace the inbuilt CFLAGS with $CFLAGS), but it may be easier just to put a comment on the AUR page asking the maintainer to look into it.
Offline