[aur-general] Arch64

newer
[aur-general] ruby-gtk2 and friends

older
[aur-general] Partially Inactive...

Nathan O

8 Sep 2010 8 Sep '10

12:55 a.m.

What would the best way to compile i686 packages on a 64bit system to test the i686 version? With also maybe a possible few 32-bit only software that I might have to run.

Show replies by date

Brad Fanella

7 Sep 7 Sep

12:53 a.m.

On Tue, Sep 07, 2010 at 05:55:42PM -0500, Nathan O wrote:

...

What would the best way to compile i686 packages on a 64bit system to test the i686 version? With also maybe a possible few 32-bit only software that I might have to run.

Simple. Use a 32-bit chroot. Or send it to me to test. ;-)

Nathan O

8 Sep 8 Sep

1:16 a.m.

I installed Xyne's package, arch32-light. How do I build in it, I am guessing maybe cp the PKGBUILD to somewhere in /opt/arch32? On Mon, Sep 6, 2010 at 5:53 PM, Brad Fanella wrote:

...

On Tue, Sep 07, 2010 at 05:55:42PM -0500, Nathan O wrote:

...
What would the best way to compile i686 packages on a 64bit system to test the i686 version? With also maybe a possible few 32-bit only software that I might have to run.

Simple. Use a 32-bit chroot.

Or send it to me to test. ;-)

Xyne

1:43 a.m.

Nathan O wrote:

...

...
Simple. Use a 32-bit chroot.

Or send it to me to test. ;-)

I installed Xyne's package, arch32-light. How do I build in it, I am guessing maybe cp the PKGBUILD to somewhere in /opt/arch32?

Nathan, just read up on chroots and how to use them, starting with the 32-bit chroot article on the wiki on which arch32-light is based. In this case, yeah, you would copy it to somewhere in /opt/arch32 then chroot into /opt/arch32 and build the package as usual (provided that you already installed pacman and base-devel in the chroot). I don't want to discourage you from asking specific questions when you get stuck but as an Archer you're expected to do some research and testing on your own first. Questions such as "How do I do x?" where "x" is something very general are a sign of laziness. Questions such as "I've tried x, but I get the following error message and I can't find a solution through <some search engine> or the forum. What should I do?" show that you've at least tried to solve it yourself. Don't take this the wrong way either. I'm not annoyed. I'm just trying to encourage you to approach things a little differently.

Nathan O

1:49 a.m.

On Tue, Sep 7, 2010 at 6:43 PM, Xyne wrote:

...

Nathan O wrote:

...
...
Simple. Use a 32-bit chroot.

Or send it to me to test. ;-)

I installed Xyne's package, arch32-light. How do I build in it, I am guessing maybe cp the PKGBUILD to somewhere in /opt/arch32?

Nathan, just read up on chroots and how to use them, starting with the 32-bit chroot article on the wiki on which arch32-light is based. In this case, yeah, you would copy it to somewhere in /opt/arch32 then chroot into /opt/arch32 and build the package as usual (provided that you already installed pacman and base-devel in the chroot).

I don't want to discourage you from asking specific questions when you get stuck but as an Archer you're expected to do some research and testing on your own first. Questions such as "How do I do x?" where "x" is something very general are a sign of laziness. Questions such as "I've tried x, but I get the following error message and I can't find a solution through <some search engine> or the forum. What should I do?" show that you've at least tried to solve it yourself.

Don't take this the wrong way either. I'm not annoyed. I'm just trying to encourage you to approach things a little differently.

I know I looked at the 32bit bundled article, but it didn't mention anything about building AUR packages there.

Xyne

2:07 a.m.

Nathan O wrote:

...

I know I looked at the 32bit bundled article, but it didn't mention anything about building AUR packages there.

A chroot behaves like a normal system. You build packages in the chroot the same way you build packages on the normal system, i.e. by creating or copying PKGBUILD and then running makepkg in the same directory. I wasn't implying that the wiki article had a section that spelt it out explicitly or that everything you needed to know was in that article. What I meant was that you should read up on chroots in general because once you've generally understood them then the answer will become clear.

Nathan O

3:13 a.m.

On Tue, Sep 7, 2010 at 7:07 PM, Xyne wrote:

...

Nathan O wrote:

...
I know I looked at the 32bit bundled article, but it didn't mention anything about building AUR packages there.

A chroot behaves like a normal system. You build packages in the chroot the same way you build packages on the normal system, i.e. by creating or copying PKGBUILD and then running makepkg in the same directory.

I wasn't implying that the wiki article had a section that spelt it out explicitly or that everything you needed to know was in that article. What I meant was that you should read up on chroots in general because once you've generally understood them then the answer will become clear.

I think I found a solution that seems to work for how I want it to. First I used an empty /opt/arch32 dir. I copied makepkg.conf and pacman.conf to /opt/arch32 and made sure they use i686. Then I did:

sudo mkarchroot -C -M <chrootdir>/root base base-devel sudo Now I can do makechrootpkg -r /aur -- -i and it creates the i686 package as well. Maybe we could offer this as an option under the wiki?

Nathan O

3:15 a.m.

On Tue, Sep 7, 2010 at 8:13 PM, Nathan O wrote:

...

On Tue, Sep 7, 2010 at 7:07 PM, Xyne wrote:

...
Nathan O wrote:

...
I know I looked at the 32bit bundled article, but it didn't mention anything about building AUR packages there.

A chroot behaves like a normal system. You build packages in the chroot the same way you build packages on the normal system, i.e. by creating or copying PKGBUILD and then running makepkg in the same directory.

I wasn't implying that the wiki article had a section that spelt it out explicitly or that everything you needed to know was in that article. What I meant was that you should read up on chroots in general because once you've generally understood them then the answer will become clear.

I think I found a solution that seems to work for how I want it to. First I used an empty /opt/arch32 dir. I copied makepkg.conf and pacman.conf to /opt/arch32 and made sure they use i686. Then I did:

sudo mkarchroot -C -M <chrootdir>/root base base-devel sudo

Now I can do makechrootpkg -r /aur -- -i and it creates the i686 package as well. Maybe we could offer this as an option under the wiki?

Sorry forgot to add, to change the options like mkarchroot -C

/opt/arch32/pacman.conf and the other options.

Nathan O

5:11 a.m.

On Tue, Sep 7, 2010 at 8:15 PM, Nathan O wrote:

...

On Tue, Sep 7, 2010 at 8:13 PM, Nathan O wrote:

...
On Tue, Sep 7, 2010 at 7:07 PM, Xyne wrote:

...
Nathan O wrote:

...
I know I looked at the 32bit bundled article, but it didn't mention anything about building AUR packages there.

A chroot behaves like a normal system. You build packages in the chroot the same way you build packages on the normal system, i.e. by creating or copying PKGBUILD and then running makepkg in the same directory.

I wasn't implying that the wiki article had a section that spelt it out explicitly or that everything you needed to know was in that article. What I meant was that you should read up on chroots in general because once you've generally understood them then the answer will become clear.

I think I found a solution that seems to work for how I want it to. First I used an empty /opt/arch32 dir. I copied makepkg.conf and pacman.conf to /opt/arch32 and made sure they use i686. Then I did:

sudo mkarchroot -C -M <chrootdir>/root base base-devel sudo

Now I can do makechrootpkg -r /aur -- -i and it creates the i686 package as well. Maybe we could offer this as an option under the wiki?

Sorry forgot to add, to change the options like mkarchroot -C

/opt/arch32/pacman.conf and the other options.

I edited the "Install bundled 32-bit system" and added my tutorial on how to build i686 packages at http://wiki.archlinux.org/index.php/Install_bundled_32-bit_system_in_Arch64#... Feel free to edit it if it isn't easily understood, I tried to write it as simple as I possibly could, though I am not a good at writing articles and such. Thanks, P.S. I hope you think it is a good tutorial.

Xyne

8:03 p.m.

Nathan O wrote:

...

I edited the "Install bundled 32-bit system" and added my tutorial on how to build i686 packages at http://wiki.archlinux.org/index.php/Install_bundled_32-bit_system_in_Arch64#...

Feel free to edit it if it isn't easily understood, I tried to write it as simple as I possibly could, though I am not a good at writing articles and such.

Thanks, P.S. I hope you think it is a good tutorial.

I don't think you should have added it to that article. It is incompatible with the chroot created by the article and the article itself is not about building packages in the chroot. I suggest that you move that section to its own page entitled "building 32-bit packages on a 64-bit system" or something similar.

Nathan O

8:08 p.m.

On Wed, Sep 8, 2010 at 1:03 PM, Xyne wrote:

...

Nathan O wrote:

...
I edited the "Install bundled 32-bit system" and added my tutorial on how to build i686 packages at

http://wiki.archlinux.org/index.php/Install_bundled_32-bit_system_in_Arch64#...

...
Feel free to edit it if it isn't easily understood, I tried to write it

as

...
simple as I possibly could, though I am not a good at writing articles and such.

Thanks, P.S. I hope you think it is a good tutorial.

I don't think you should have added it to that article. It is incompatible with the chroot created by the article and the article itself is not about building packages in the chroot.

I suggest that you move that section to its own page entitled "building 32-bit packages on a 64-bit system" or something similar.

It is done as you suggested :) http://wiki.archlinux.org/index.php/Building_32-bit_packages_on_a_64-bit_sys...

Rémy Oudompheng

9:15 p.m.

Nathan O wrote:

...

It is done as you suggested :) http://wiki.archlinux.org/index.php/Building_32-bit_packages_on_a_64-bit_sys...

Note that devtools (version 0.9.10 in [testing]) contains a ready-to-use /usr/share/devtools/makepkg-i686.conf. -- Rémy.

Nathan O

10:34 p.m.

On Wed, Sep 8, 2010 at 2:15 PM, Rémy Oudompheng wrote:

...

Nathan O wrote:

...
It is done as you suggested :)

http://wiki.archlinux.org/index.php/Building_32-bit_packages_on_a_64-bit_sys...

Note that devtools (version 0.9.10 in [testing]) contains a ready-to-use /usr/share/devtools/makepkg-i686.conf.

-- Rémy.

I may put that notice in the wiki article I created, though some people may not(use/want to) use testing.

Nathan O

10:41 p.m.

On Wed, Sep 8, 2010 at 3:34 PM, Nathan O wrote:

...

On Wed, Sep 8, 2010 at 2:15 PM, Rémy Oudompheng wrote:

...
Nathan O wrote:

...
It is done as you suggested :)

http://wiki.archlinux.org/index.php/Building_32-bit_packages_on_a_64-bit_sys...

Note that devtools (version 0.9.10 in [testing]) contains a ready-to-use /usr/share/devtools/makepkg-i686.conf.

-- Rémy.

I may put that notice in the wiki article I created, though some people may not(use/want to) use testing.

I added what you pointed out, and gave you credit for it :) Thanks

Pierre Schmitz

9 Sep 9 Sep

3:34 p.m.

On Wed, 8 Sep 2010 21:15:46 +0200, Rémy Oudompheng wrote:

...

Nathan O wrote:

...
It is done as you suggested :) http://wiki.archlinux.org/index.php/Building_32-bit_packages_on_a_64-bit_sys...

Note that devtools (version 0.9.10 in [testing]) contains a ready-to-use /usr/share/devtools/makepkg-i686.conf.

It's now in extra and also contains arch-build. Building packages for i686 or different repos is now as easy as running e.g. extra-i686-build in the PKGBUILD's dir. Just check "pacman -Qql devtools|grep -- -build" to get a list of the different commands. Of course you cannot build x86_64 packages on an i686 system though. Future versions will be more advanced but for now this should be the way to easily build packages in a defined environment. Greetings, Pierre -- Pierre Schmitz, https://users.archlinux.de/~pierre

Nathan O

10 Sep 10 Sep

7:03 a.m.

On Thu, Sep 9, 2010 at 8:34 AM, Pierre Schmitz wrote:

...

On Wed, 8 Sep 2010 21:15:46 +0200, Rémy Oudompheng wrote:

...
Nathan O wrote:

...
It is done as you suggested :)

http://wiki.archlinux.org/index.php/Building_32-bit_packages_on_a_64-bit_sys...

Note that devtools (version 0.9.10 in [testing]) contains a ready-to-use /usr/share/devtools/makepkg-i686.conf.

It's now in extra and also contains arch-build. Building packages for i686 or different repos is now as easy as running e.g. extra-i686-build in the PKGBUILD's dir. Just check "pacman -Qql devtools|grep -- -build" to get a list of the different commands. Of course you cannot build x86_64 packages on an i686 system though.

Future versions will be more advanced but for now this should be the way to easily build packages in a defined environment.

Greetings,

Pierre

-- Pierre Schmitz, https://users.archlinux.de/~pierre https://users.archlinux.de/%7Epierre

Nice, didn't know that anything like this was available, guessing maybe you or somebody created it recently?

Thomas Dziedzic

8 Sep 8 Sep

1:16 a.m.

On Mon, Sep 6, 2010 at 5:53 PM, Brad Fanella wrote:

...

On Tue, Sep 07, 2010 at 05:55:42PM -0500, Nathan O wrote:

...
What would the best way to compile i686 packages on a 64bit system to test the i686 version? With also maybe a possible few 32-bit only software that I might have to run.

Simple. Use a 32-bit chroot.

Or send it to me to test. ;-)

Check out my wrapper for the devtools, called makizushi. https://bbs.archlinux.org/viewtopic.php?id=104483 to build a 64 bit package just do the following: (you might want to change the packager variable, although you don't have to) newchr stable64 mkchr stable64 first command creates a clean chroot in /var/mychroots second command makes the package in the clean chroot

Thomas Dziedzic

1:18 a.m.

On Tue, Sep 7, 2010 at 6:16 PM, Thomas Dziedzic wrote:

...

On Mon, Sep 6, 2010 at 5:53 PM, Brad Fanella wrote:

...
On Tue, Sep 07, 2010 at 05:55:42PM -0500, Nathan O wrote:

...
What would the best way to compile i686 packages on a 64bit system to test the i686 version? With also maybe a possible few 32-bit only software that I might have to run.

Simple. Use a 32-bit chroot.

Or send it to me to test. ;-)

Check out my wrapper for the devtools, called makizushi.

https://bbs.archlinux.org/viewtopic.php?id=104483

to build a 64 bit package just do the following: (you might want to change the packager variable, although you don't have to)

newchr stable64 mkchr stable64

first command creates a clean chroot in /var/mychroots second command makes the package in the clean chroot

Note the newchr only needs to be run one time since the clean chroot will stay on your system until you delete it.

4997

Age (days ago)

5000

Last active (days ago)

List overview

Download

17 comments

6 participants

participants (6)

Brad Fanella
Nathan O
Pierre Schmitz
Rémy Oudompheng
Thomas Dziedzic
Xyne