[arch-general] problem compiling for i586 with new makepkg

Aaron Griffin aaronmgriffin at gmail.com
Fri Dec 14 18:42:27 EST 2007

On Dec 14, 2007 5:33 PM, Karolina Lindqvist
<karolina.lindqvist at kramnet.se> wrote:
> There is a problem with compiling with CHOST="i586" with the new
> pacman/makepkg.
> It simply refuses with the message:
>         pkgname is not available for the 'i586' architecture.
>         Note that many packages may need a line added to their PKGBUILD
>         such as arch=('i586').
> To edit each and every PKGBUILD for each and every package and every update
> appears like quite a big work. And since I could not find any option to turn
> that "feature" off, or any hook to SED it in, I just commented it out in
> makepkg. What was the thought with this?

The official packages are not tested for i586. This means that they
will not directly compile without intercession by a user.

Why would we put sed hooks in to fix it when you
can...just...run...sed yourself? Arch _does_ have the whole "helper
scripts are dumb" type philosophy...
Why would we provide one command (makepkg) to replace one command (sed)?

> The -w option is also taken away from makepkg. Why?
> (I found the alternate solution, but still)

I can't recall what -w did. Regardless, it was removed because Dan and
I wanted to remove it. These things are usually covered for a while on
the pacman-dev list, and parties with a vested interest in certain
things would benefit from joining the discussion there. Perhaps, given
valid reasons, we would have kept the option (again, I have no idea
what it did).

More information about the arch-general mailing list