[aur-general] moving the cross32 chain into community
heftig and me thought it would be convenient to have a cross32 chain in community in order to more easily and cleanly (hurr hurr, cross32 and clean in the same sentence!) build lib32 packages and to enable building of wine-wow64 (mail incoming). This would include: cross32-binutils, cross32-gcc, lib32-glibc-devel from AUR. Before making this move I wanted to gather some opinions because I know some people really, really hate lib32, bin32 and cross32 and love chroots to death. -- Sven-Hendrik
On Sat, Jul 17, 2010 at 15:54, Sven-Hendrik Haase <sh@lutzhaase.com> wrote:
heftig and me thought it would be convenient to have a cross32 chain in community in order to more easily and cleanly (hurr hurr, cross32 and clean in the same sentence!) build lib32 packages and to enable building of wine-wow64 (mail incoming).
This would include: cross32-binutils, cross32-gcc, lib32-glibc-devel from AUR.
Before making this move I wanted to gather some opinions because I know some people really, really hate lib32, bin32 and cross32 and love chroots to death.
-- Sven-Hendrik
Personally, I use and enjoy a chroot. However, I think there would be a lot of value in having binary packages available for the purposes of cross-compilation between arches. Sounds good! -- Ranguvar [Devin Cofer]
On 07/18/2010 01:54 AM, Sven-Hendrik Haase wrote:
heftig and me thought it would be convenient to have a cross32 chain in community in order to more easily and cleanly (hurr hurr, cross32 and clean in the same sentence!) build lib32 packages and to enable building of wine-wow64 (mail incoming).
This would include: cross32-binutils, cross32-gcc, lib32-glibc-devel from AUR.
we never supported splitting packages into -devel. so what about adding the headers into lib32-glibc instead? -- Ionuț
Hi, Can you delete rapidsvn [1] please, i searched the AUR before uploading, but like an idiot didn't search the official repo's. Apologies for my stupidity [1] http://aur.archlinux.org/packages.php?ID=14933 Thanks, Simon
On Sun, Jul 18, 2010 at 1:30 PM, s_stoakley@hotmail.co.uk <s_stoakley@hotmail.co.uk> wrote:
Hi, Can you delete rapidsvn [1] please, i searched the AUR before uploading, but like an idiot didn't search the official repo's. Apologies for my stupidity
[1] http://aur.archlinux.org/packages.php?ID=14933
Thanks, Simon
Done. :)
Could you delete powder-toy-beta [1] please, I've just taken it over and the name has changed (dropped the beta) so it's uploaded as a separate pkg [2] ) Thanks Simon [1] http://aur.archlinux.org/packages.php?ID=38500 [2] http://aur.archlinux.org/packages.php?ID=39203
Could you delete powder-toy-beta [1] please, I've just taken it over and the name has changed (dropped the beta) so it's uploaded as a separate pkg [2] ) Thanks Simon [1] http://aur.archlinux.org/packages.php?ID=38500 [2] http://aur.archlinux.org/packages.php?ID=39203
On Mon, Jul 26, 2010 at 4:41 PM, Simon Stoakley <s_stoakley@hotmail.co.uk> wrote:
Could you delete powder-toy-beta [1] please, I've just taken it over and the name has changed (dropped the beta) so it's uploaded as a separate pkg [2] )
Thanks Simon
[1] http://aur.archlinux.org/packages.php?ID=38500 [2] http://aur.archlinux.org/packages.php?ID=39203
Done. :)
On Sun, 2010-07-18 at 00:54 +0200, Sven-Hendrik Haase wrote:
heftig and me thought it would be convenient to have a cross32 chain in community in order to more easily and cleanly (hurr hurr, cross32 and clean in the same sentence!) build lib32 packages and to enable building of wine-wow64 (mail incoming).
This would include: cross32-binutils, cross32-gcc, lib32-glibc-devel from AUR. Hi, list. I'm the maintainer of these packages. Actually, to build something more or less complex with them in a clean way you'll need (apart from headers) cross32-pkg-config (unpublished) and .pc files for your dependencies in /opt/lib32/usr/lib/pkgconfig.
On 18.07.2010 15:05, Mikhail Vorozhtsov wrote:
On Sun, 2010-07-18 at 00:54 +0200, Sven-Hendrik Haase wrote:
heftig and me thought it would be convenient to have a cross32 chain in community in order to more easily and cleanly (hurr hurr, cross32 and clean in the same sentence!) build lib32 packages and to enable building of wine-wow64 (mail incoming).
This would include: cross32-binutils, cross32-gcc, lib32-glibc-devel from AUR. Hi, list. I'm the maintainer of these packages. Actually, to build something more or less complex with them in a clean way you'll need (apart from headers) cross32-pkg-config (unpublished) and .pc files for your dependencies in /opt/lib32/usr/lib/pkgconfig.
What's become of this? No cross32-pkg-config and no more opinions either?
participants (7)
-
Evangelos Foutras
-
Ionuț Bîru
-
Mikhail Vorozhtsov
-
Ranguvar
-
s_stoakley＠hotmail.co.uk
-
Simon Stoakley
-
Sven-Hendrik Haase