Bug 108429

Summary:	fall back on DEFAULT_ABI for --libdir if ABI is not set
Product:	Portage Development	Reporter:	Jeremy Huddleston (RETIRED) <eradicator>
Component:	Core	Assignee:	Portage team <dev-portage>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	amd64
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	ebuild.sh-libdir.patch

Description Jeremy Huddleston (RETIRED) gentoo-dev

2005-10-07 14:00:29 UTC

This is needed for amd64 2006.0 as we are not exporting ABI unless it is not the
default.  This behavior change is being made now that we can use CHOST to
properly determine the toolchain starting with the new eselect-compiler wrapper.

Comment 1 Jeremy Huddleston (RETIRED) gentoo-dev

2005-10-07 14:01:52 UTC

Created attachment 70116 [details, diff]
ebuild.sh-libdir.patch

trivial change

Comment 2 Brian Harring (RETIRED) gentoo-dev

2005-10-07 14:05:38 UTC

Err... seems dumb to me to _not_ export ABI, and instead have the code
automatically check and pull the default ABI from another var when it could've,
(potentially should've?) been exported via the profile...

Comment 3 Jeremy Huddleston (RETIRED) gentoo-dev

2005-10-07 14:55:28 UTC

Ok, fair enough... just trying to get it to match the multilib.eclass method of
falling back to DEFAULT_ABI if it's set.  I'll setup the profile to still set
ABI and we can look for a more permanent solution down the road.