Arch Linux

sacarde

Member

Registered: 2006-07-14

Posts: 389

error building from AUR (ppc)

Hi,
   in my archppc I try to build unshield from AUR

I have change ARCH in PKGBUILD, but I have error:

BUILDSCRIPT non è definito! Assicurarsi di aver aggiornato /etc/makepkg.conf

I view that I have /etc/makepkg.conf.new
then I renamed ..new into makepkg.conf

but now error is:
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
make: *** No targets specified and no makefile found.  Stop.
==> ERRORE: Compilazione interrotta.

can you help me ?

jskier

Member

From: Minnesota, USA

Registered: 2003-07-30

Posts: 383

Website

Re: error building from AUR (ppc)

I had the same problem too... I found that downgrading to the previous version of pacman fixed this (why, I don't know).

---

--
JSkier

Snowman

Developer/Forum Fellow

From: Montreal, Canada

Registered: 2004-08-20

Posts: 5,212

Re: error building from AUR (ppc)

check the config.log file. there's probably  a more descriptive error message there.

losinggeneration

Member

From: Iowa

Registered: 2008-02-01

Posts: 6

Website

Re: error building from AUR (ppc)

Try editing /etc/makepkg.conf and change -mtune=generic to -mtune=common (or whatever cpu you like. a reference here of possible values http://gcc.gnu.org/onlinedocs/gcc/RS_00 … tions.html)

sacarde

Member

Registered: 2006-07-14

Posts: 389

Re: error building from AUR (ppc)

ok
-mtune=common

works OK

p.s.
which suggest for:

apple G4  7447A, altivec supported

losinggeneration

Member

From: Iowa

Registered: 2008-02-01

Posts: 6

Website

Re: error building from AUR (ppc)

ok
-mtune=common

works OK

p.s.
which suggest for:

apple G4  7447A, altivec supported

-mtune=G4 instead of -mtune=common of course
You can also add -mabi=altivec -maltivec if you'd like. It compiles with that, but I'm not sure if it will help any since the compiler was built with --disable-multilib.

Also, you may want to file a bug report or ask on the mailing list if it's fixed. I mentioned it in IRC right after posting that but didn't get a reply.