You are not logged in.

#1 2006-09-09 20:48:05

innkeeper
Member
Registered: 2006-07-06
Posts: 11

PKGBUILD issue - ${CARCH} doesn't work

[ "${CARCH}" = "i686" ]   && KARCH=i386
[ "${CARCH}" = "x86_64" ] && KARCH=x86_64

Just doesn't work. That's why KARCH is empty and there is no vmlinuz26 in pkg in the end. I can rewrite PKGBUILD or solve this issue another way but i'm interested where ${CARCH} is setted?

PS
Tried to google but it finds Connecticut Association of Residential Care Homes etc. smile)))

PPS
i used to build my kernel without ABS but it was some problems with nvidia drivers (there were wrong paths for modules directory).. and now i decided to use ABS to avoid any other problems

Offline

#2 2006-09-09 21:41:25

T-Dawg
Forum Fellow
From: Charlotte, NC
Registered: 2005-01-29
Posts: 2,736

Re: PKGBUILD issue - ${CARCH} doesn't work

try using is equal to instead of trying to assign it

[ "${CARCH}" == "i686" ] && KARCH="i386"

Offline

#3 2006-09-09 21:51:46

innkeeper
Member
Registered: 2006-07-06
Posts: 11

Re: PKGBUILD issue - ${CARCH} doesn't work

I belive there is no "==" operator in bash :-) It's not a syntax problem. ${CARCH} is empty ;-)

Offline

#4 2006-09-10 03:30:35

Cam
Member
From: Brisbane, Aus
Registered: 2004-12-21
Posts: 658
Website

Re: PKGBUILD issue - ${CARCH} doesn't work

innkeeper wrote:

I belive there is no "==" operator in bash :-) It's not a syntax problem. ${CARCH} is empty ;-)

both work but your syntax is correct

CARCH should be set in /etc/makepkg.conf which is sourced by /usr/bin/makepkg, check the conf file isn't messed up at all

Offline

#5 2006-09-10 06:29:41

innkeeper
Member
Registered: 2006-07-06
Posts: 11

Re: PKGBUILD issue - ${CARCH} doesn't work

Thanks a lot. Completely forgot about makepkg.conf %-) I was sure that it should be set somewhere like in profile.d etc. So it was setted to "pentium4" :-D

Offline

#6 2006-09-10 07:11:09

Cam
Member
From: Brisbane, Aus
Registered: 2004-12-21
Posts: 658
Website

Re: PKGBUILD issue - ${CARCH} doesn't work

So it was setted to "pentium4"

that'll work for now but when makepkg is made port-friendly your CARCH will need to be set to one of the "supported" archs otherwise makepkg may not build your packages. this is the way it is in frugalware and while the arch devs like to do things themselves, it would be silly to rewrite such basic code to support multiple archs

Offline

Board footer

Powered by FluxBB