[SOLVED] How can I see the value of CARCH?

Arkranur · 2014-01-09 13:53:38

I'm trying to fix the PKGBUILD of libretro-mupen64plus-git in the AUR, and there is something wrong in its build function. The second md5 sum is wrong too, I am aware of that, but in the build function I believe that what's wrong is the value of CARCH. I don't see it in my env list, and I really don't know how I can access its value.

I am not currently using the computer that produces the error (I will post the error message later), but here are the steps I used to reproduce the problem:

1. Frst run

 $ yaourt -S libretro-mupen64plus-git

2. Edit the PKGBUILD and change the second md5 sum to 'SKIP'
3. Let yaourt build the package and hopefully a huge linker error will pop up.

I'm pretty sure the error is in the build function of the PKGBUILD and that it has to do with the make WITH_DYNAREC line since I can build and install the package with two fixes: changing the second md5 sum with the correct one or typing 'SKIP' and deleting everything after the first line of the build function and typing make WITH_DYNAREC=x86.

tl;dr: I just want know how I can see the value of CARCH so that I can fix the PKGBUILD of libretro-mupen64plus-git in the AUR

Last edited by Arkranur (2014-01-09 14:02:06)

Trilby · 2014-01-09 13:56:25

CARCH is defined in /etc/makepkg.conf and it defines the archictecture of the computer the package is being build on (or for).

When troubleshooting, don't use yaourt.

EDIT: this built fine on x86_64. If this is an arm specific issue, you'll have to ask on the archlinuxarm.org forums.

Last edited by Trilby (2014-01-09 13:59:35)

Arkranur · 2014-01-09 13:59:41

Thanks.

And, why not use yaourt? Because it is not a supported package? I'm sorry, I'm kind of new to all of this.

Last edited by Arkranur (2014-01-09 14:04:32)

Arkranur · 2014-01-09 14:04:14

Trilby wrote:

CARCH is defined in /etc/makepkg.conf and it defines the archictecture of the computer the package is being build on (or for).
When troubleshooting, don't use yaourt.
EDIT: this built fine on x86_64. If this is an arm specific issue, you'll have to ask on the archlinuxarm.org forums.

It builds fine on x86 with the changes I mentioned at the end of the post.

Trilby · 2014-01-09 14:04:58

Why not use yaourt? Many reasons - search the forums and you'll find them quickly. In short the two most relevant to the present issue are, one, that while yaourt simplifies simple things, it greatly hinders troubleshooting as it hides/obscures a lot of what is actually happening and sometimes just breaks things. The second (now relevant) reason is that if you are new to using the AUR (especially if you are maintaining packages) you should understand what it going on - by simplifying, again yaourt often obscures.

This is not to say that yaourt isn't very good for experienced users who know what it is doing - it does help automate some of the steps. But don't automate until you understand.

Yet more directly to your question: no it is not a supported package - nothing in the AUR is.

Last edited by Trilby (2014-01-09 14:08:14)

Arkranur · 2014-01-09 14:18:41

Trilby wrote:

Why not use yaourt? Many reasons - search the forums and you'll find them quickly. In short the two most relevant to the present issue are, one, that while yaourt simplifies simple things, it greatly hinders troubleshooting as it hides/obscures a lot of what is actually happening and sometimes just breaks things. The second (now relevant) reason is that if you are new to using the AUR (especially if you are maintaining packages) you should understand what it going on - by simplifying, again yaourt often obscures.
This is not to say that yaourt isn't very good for experienced users who know what it is doing - it does help automate some of the steps. But don't automate until you understand.
Yet more directly to your question: no it is not a supported package - nothing in the AUR is.

Thanks! I didn't know yaourt was hiding stuff. Can you tell me a better way to write my original post without yaourt? I'll try not to automate then.

And, yes, my original question has been answered. The problem in the PKGBUILD was in the CARCH value. Mine is i686 and the source does not build with

make WITH_DYNAREC=i686

but rather with

 make WITH_DYNAREC=x86

Thanks a lot for your help!

Last edited by Arkranur (2014-01-09 14:20:17)

Trilby · 2014-01-09 14:20:16

See here. Use makepkg. Especially when something goes wrong: always check if a makepkg also fails with the PKGBUILD. Makepkg is a supported tool, and is on every arch user's system so we can all be on the same page. Those who use some helper tool (such as yaourt) should also be familiar with how it is really just using makepkg in the background.

Also see `man makepkg` for the easy way to fix the checksum.

Last edited by Trilby (2014-01-09 14:22:00)

Arkranur · 2014-01-09 14:21:55

Trilby wrote:

See here. Use makepkg.
Also see `man makepkg` for the easy way to fix the checksum.

Thanks!

Arch Linux

#1 2014-01-09 13:53:38

[SOLVED] How can I see the value of CARCH?

#2 2014-01-09 13:56:25

Re: [SOLVED] How can I see the value of CARCH?

#3 2014-01-09 13:59:41

Re: [SOLVED] How can I see the value of CARCH?

#4 2014-01-09 14:04:14

Re: [SOLVED] How can I see the value of CARCH?

#5 2014-01-09 14:04:58

Re: [SOLVED] How can I see the value of CARCH?

#6 2014-01-09 14:18:41

Re: [SOLVED] How can I see the value of CARCH?

#7 2014-01-09 14:20:16

Re: [SOLVED] How can I see the value of CARCH?

#8 2014-01-09 14:21:55

Re: [SOLVED] How can I see the value of CARCH?

Board footer