Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
ABI_X86="64 32" madness
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Sat Mar 29, 2014 4:53 am    Post subject: ABI_X86="64 32" madness Reply with quote

Tonight's portage updates appear to be a real mess for me on amd64. I don't remember seeing anything in the news, but it appears I now am in the process of ditching my app-emulation/x86-emul-whatevers for

Code:
ABI_X86="64 32"


in my make.conf. The real trouble appears that there a still a number of ebuilds that don't want to build the 32 abi alongside the 64 one until I unmask their unstable version. I think it was wine that set things off.

Did I miss a memo somewhere? I see some threads starting around march of last year when this stuff first started messing with ~amd64 users.
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Sat Mar 29, 2014 5:27 am    Post subject: stuff like this is making things very annoying Reply with quote

I've already run into a couple like this while trying to unmask stuff. I didn't realize that an ebuild marked as stable could also be marked as unstable when a USE flag changed:

Code:
thufir portage # emerge -uDN world
Calculating dependencies... done!

emerge: there are no ebuilds built with USE flags to satisfy "sys-libs/zlib[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?]".
!!! One of the following packages is required to complete your request:
- media-libs/freetype-2.5.3-r1::gentoo (Change USE: -abi_x86_32)
(dependency required by "media-libs/freetype-2.5.3-r1" [ebuild])
(dependency required by "media-libs/harfbuzz-0.9.23[truetype]" [installed])
(dependency required by "x11-libs/pango-1.36.2" [installed])
(dependency required by "x11-libs/gtk+-2.24.22" [installed])
(dependency required by "media-gfx/graphviz-2.26.3-r4[gtk]" [installed])
(dependency required by "app-text/asciidoc-8.6.5[graphviz]" [installed])
(dependency required by "x11-proto/xproto-7.0.25[doc]" [ebuild])
(dependency required by "media-libs/freeglut-2.8.1-r1" [ebuild])
(dependency required by "media-libs/jasper-1.900.1-r5[opengl]" [installed])
(dependency required by "x11-libs/gdk-pixbuf-2.30.6[jpeg2k]" [installed])
thufir portage # emerge -pv zlib

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] sys-libs/zlib-1.2.8-r1  USE="minizip -static-libs" ABI_X86="(64) (-32) (-x32)" 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB
thufir portage # ACCEPT_KEYWORDS="~amd64" emerge -pv zlib

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] sys-libs/zlib-1.2.8-r1  USE="minizip -static-libs" ABI_X86="32* (64) (-x32)" 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Sat Mar 29, 2014 6:17 am    Post subject: Is there an end to this? Reply with quote

Here's what I have in my /etc/portage/package.keywords and the list just seems to keep growing and growing as I try to emerge -uDN world. Either I synch-ed in the middle of something big or the flag fairy forget to mark a bunch of stuff as stable. All of the ebuilds starting with zlib are stable versions that apparently must be marked as unstable in order to build both 32 and 64 bit abi's.

Code:
#abi32 madness
=media-libs/mesa-10.1.0            ~amd64
=x11-proto/xextproto-7.3.0         ~amd64
=x11-proto/xcb-proto-1.10         ~amd64
=x11-proto/xproto-7.0.25         ~amd64
=x11-libs/libxcb-1.10            ~amd64
=app-arch/bzip2-1.0.6-r7         ~amd64
=dev-libs/expat-2.1.0-r4         ~amd64
=media-libs/libpng-1.6.9:0/16         ~amd64
=media-libs/freetype-2.5.3-r1:2         ~amd64
=media-libs/fontconfig-2.11.0-r1:1.0      ~amd64
=sys-libs/ncurses-5.9-r3:5         ~amd64
=media-libs/libjpeg-turbo-1.3.1         ~amd64
=media-libs/libpng-1.2.51:1.2         ~amd64
=dev-libs/udis86-1.7-r2            ~amd64
=media-libs/tiff-3.9.7-r1:3         ~amd64
=sys-devel/llvm-3.4:0/3.4         ~amd64
=dev-libs/libusb-1.0.18:1          ~amd64
=x11-libs/libXdmcp-1.1.1-r1         ~amd64
=dev-libs/libpthread-stubs-0.3-r1      ~amd64
=sys-libs/zlib-1.2.8-r1            ~amd64
=x11-libs/libX11-1.6.2            ~amd64
=x11-proto/kbproto-1.0.6-r1         ~amd64
=x11-proto/xf86bigfontproto-1.2.0-r1      ~amd64
=x11-libs/libXxf86vm-1.1.3         ~amd64
=x11-libs/libXau-1.0.8            ~amd64
=x11-proto/xf86vidmodeproto-2.3.1-r1      ~amd64
=x11-libs/libXext-1.3.2            ~amd64
=x11-proto/inputproto-2.2-r1         ~amd64
=x11-proto/inputproto-2.3         ~adm64
=x11-libs/libdrm-2.4.52            ~adm64
=x11-libs/libXvMC-1.0.8            ~amd64
=x11-libs/libXv-1.0.10            ~amd64
=x11-proto/videoproto-2.3.2         ~amd64
=x11-libs/libXdamage-1.1.4-r1         ~amd64


I'm going to to walk away for a while, have a little something to eat, maybe get some sleep and then come back to have some reply tell me about the error of my ways :x
Back to top
View user's profile Send private message
frank9999
n00b
n00b


Joined: 20 Feb 2013
Posts: 61
Location: Germany

PostPosted: Sat Mar 29, 2014 10:41 am    Post subject: Re: ABI_X86="64 32" madness Reply with quote

Welcome in the club of ABI 32 Users ;-)

vaxbrat wrote:

Did I miss a memo somewhere? I see some threads starting around march of last year when this stuff first started messing with ~amd64 users.


No, there was exact nothing...

In general you should NOT use in every case the latest ~AMD64 version of a required package.
This would cause you more problems then realy needed.
For e.g. i would not use ATM =media-libs/freetype-2.5.3-r1:2 instead use =media-libs/freetype-2.5.0.1.
With newer versions freetype you need more packages to be unmasked, and some packages still fail to build with versions >2.5.1.

You need a combination of the first version of a package with that ABI support, but this not in any case the latest ~AMD64 Version.

I wrote here the steps i took last week:
https://bugs.gentoo.org/show_bug.cgi?id=499952#c28
But there are also other ways.

Here is whats actualy left in my package.accept_keywords file:

Code:
##multilib fun part
=sys-libs/e2fsprogs-libs-1.42.8
=sys-fs/e2fsprogs-1.42.8
=media-libs/glew-1.10.0-r2
=sys-libs/ncurses-5.9-r3
=media-libs/libv4l-1.0.0
=media-libs/freetype-2.5.0.1
=media-libs/libvorbis-1.3.3-r1
=media-libs/flac-1.2.1-r5
=media-sound/mpg123-1.18.1
=dev-libs/libffi-3.0.13-r1
=virtual/libffi-3.0.13-r1
=sys-libs/gpm-1.20.7-r2
=sys-devel/clang-3.4-r100
=sys-devel/llvm-3.4
=media-libs/jasper-1.900.1-r6
=sys-libs/gdbm-1.11
=media-libs/libmodplug-0.8.8.4-r1
=media-libs/libdvdnav-4.2.1
=media-libs/libdv-1.0.0-r3
=media-libs/libid3tag-0.15.1b-r4
media-libs/x264
=media-libs/xvid-1.3.2-r1
=media-libs/vo-aacenc-0.1.3
=dev-libs/fribidi-0.19.5-r2
=dev-libs/udis86-1.7-r2
sys-libs/readline
dev-libs/libtasn1
=media-libs/libmpeg2-0.5.1-r2
=media-libs/faad2-2.7-r3
=media-libs/libao-1.2.0
=dev-libs/nettle-2.7.1-r1
=dev-libs/libgpg-error-1.12-r1
=media-libs/libmad-0.15.1b-r8
=media-libs/libtheora-1.1.1-r1
=dev-libs/gmp-5.1.3-r1
=media-libs/openjpeg-1.5.1-r1
=media-libs/libdvdread-4.2.1
=dev-libs/libxml2-2.9.1-r2
=media-sound/lame-3.99.5-r1
=dev-db/sqlite-3.8.4.1
=media-libs/libsamplerate-0.1.8-r1
=media-libs/speex-1.2_rc1-r2
=media-libs/libvisual-0.4.0-r3
=virtual/libintl-0-r1
=x11-libs/libva-1.2.1-r1
=x11-libs/libva-vdpau-driver-0.7.4-r1
=x11-libs/libva-intel-driver-1.2.2-r1
=media-libs/a52dec-0.7.4-r7
=dev-libs/libpcre-8.34
=media-sound/twolame-0.3.13-r1

#multilib to workaround rebuild bugs etc.
net-libs/gnutls
dev-lang/python
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Sat Mar 29, 2014 6:41 pm    Post subject: ditching wine Reply with quote

This is way too big a trainwreck to be acceptable. I'm ditching wine and staying back with the emul libs for now
Back to top
View user's profile Send private message
epsilon72
Guru
Guru


Joined: 20 Sep 2007
Posts: 568

PostPosted: Sun Mar 30, 2014 12:25 am    Post subject: Reply with quote

If you're running mostly stable, here is a temporary fix:

/etc/portage/package.mask
Code:
=media-libs/mesa-10.0.4
=virtual/opengl-7.0-r1
=x11-base/xorg-drivers-1.15
=x11-base/xorg-server-1.15.0
=x11-proto/dri2proto-2.8-r1
=x11-proto/glproto-1.4.17
=x11-proto/xf86driproto-2.1.1-r1

EDIT: NEVERMIND, SEE REAL SOLUTION BELOW


Last edited by epsilon72 on Tue Apr 01, 2014 3:56 am; edited 1 time in total
Back to top
View user's profile Send private message
epsilon72
Guru
Guru


Joined: 20 Sep 2007
Posts: 568

PostPosted: Tue Apr 01, 2014 3:54 am    Post subject: Reply with quote

I can't believe I missed this. Earlier I had mistakenly added
Code:
ABI_X86="64 32"

to my make.conf, for wine, rather than just putting it in package.use. Removing the 32 fixes the upgrade for me. Check your make.conf.
Back to top
View user's profile Send private message
PhaytalError
n00b
n00b


Joined: 17 May 2012
Posts: 46

PostPosted: Thu Apr 03, 2014 5:54 pm    Post subject: Reply with quote

I don't understand the complaint here, I have ABI_X86="64 32" in my /etc/portage/make.conf and no issues at all. Even though emul-* stuff pulls in, it all still works just fine.

However, then again I default to ACCEPT_KEYWORDS="~amd64" in my make.conf because "unstable" is kind of a misnomer, as it is pretty stable and absolutely nothing to be afraid of. Seriously, i've been using "unstable" Gentoo since I started using Gentoo back in it's early beginnings. :)
_________________
Linux. Freedom. Power.
Back to top
View user's profile Send private message
epsilon72
Guru
Guru


Joined: 20 Sep 2007
Posts: 568

PostPosted: Thu Apr 03, 2014 6:00 pm    Post subject: Reply with quote

PhaytalError wrote:
...ACCEPT_KEYWORDS="~amd64"...


That probably makes a big difference, since 'unstable' has been exposed to more of the new multilib stuff for a while now. I'm running (mostly) stable.
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Fri Apr 04, 2014 1:07 am    Post subject: unstable can be "quite" unstable at times Reply with quote

Quote:
However, then again I default to ACCEPT_KEYWORDS="~amd64" in my make.conf because "unstable" is kind of a misnomer, as it is pretty stable and absolutely nothing to be afraid of. Seriously, i've been using "unstable" Gentoo since I started using Gentoo back in it's early beginnings. :)


I do unstable on a couple of boxes including a Bonaire class Radeon system but stick with mostly stable on work builds and my primary raid server at home. One of the other boxes is a backup raid server for that one that runs unstable. I agree that unstable is mostly workable most of the time, but I have had more than one painful update bite me in the 10 years of so of my using gentoo.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum