Arch Linux

unixguru

Member

Registered: 2006-05-02

Posts: 85

compile visualboyadvance

I am using the aur PKGBUILD. it's taking a long time to compile and cpu activity is full, took about 45 minutes and still at the same point. should i continue or give up?

unixguru

Member

Registered: 2006-05-02

Posts: 85

Re: compile visualboyadvance

i just found punkrockguy318's package but that doesn't have gvba. can anyone upload a package with the gtk gui.

Snowman

Developer/Forum Fellow

From: Montreal, Canada

Registered: 2004-08-20

Posts: 5,212

Re: compile visualboyadvance

Here it only takes 1-2 minutes to compile. What's your CPU/ amount of RAM?  Do you get high disk activity?

About the package, I've added it to the community repo. Enable the community repo in your pacman.conf and you'll be able to install it with:
# pacman -Sy visualboyadvance
It could take some time (few days) before it reaches your mirror.

BTW, it would be better not to use packages from the old tur repo. They are unmaintained/obsoleted.

unixguru

Member

Registered: 2006-05-02

Posts: 85

Re: compile visualboyadvance

my specs
p4 1.5g
128 megs pc800 rd ram
nvidia riva tnt2 m64 16megs

I have no idea why it's not compiling and the activity led is glowing all the time and cpu usage brings everything to a standstill. Thanks for the package snowman, i really appreciate it. also, i am new to arch and i can't seem to understand these terms. just can anyone briefly describe what aur, abs tur and PKGBUILD are?
Thanks all

mpie

Member

From: 404 Not found

Registered: 2005-03-06

Posts: 649

Re: compile visualboyadvance

it's now in extra with gvba compiled in...

unixguru

Member

Registered: 2006-05-02

Posts: 85

Re: compile visualboyadvance

I downloaded the community package. works great! Thanks all for the help.

omgwtfbyobbq

Member

Registered: 2006-07-04

Posts: 226

Re: compile visualboyadvance

arise thread, thread arise1
there was a bug where a certain cflag (O3? fommit-fred-pointer? funrolloops-ricer?) and the gtk flag would result in the C compiler eating huge amounts of ram with the system eventually freezing iirc. very odd, only work around was to remove the offending cflag for the compilation.