1 |
On Sat, 2015-02-07 at 07:53 -0800, Brian Dolbec wrote: |
2 |
> On Sat, 7 Feb 2015 12:34:31 +0000 |
3 |
> Joakim Tjernlund <joakim.tjernlund@×××××××××.se> wrote: |
4 |
> |
5 |
> > X compiling sys-libs/pam with USE="berkdb cracklib" will fail as both berkdb and cracklib installs .la |
6 |
> > files which points to the hosts sysroot |
7 |
> > |
8 |
> > AFAIK this problem is caused by libtool not being informed about the new sysroot. |
9 |
> > |
10 |
> > Adjusting sys-libs/pam ebuild: |
11 |
> > --- pam-1.1.8-r2.ebuild.org 2015-02-07 13:27:55.956949334 +0100 |
12 |
> > +++ pam-1.1.8-r2.ebuild 2015-02-07 13:30:05.171420033 +0100 |
13 |
> > @@ -4,7 +4,7 @@ |
14 |
> > |
15 |
> > EAPI=5 |
16 |
> > |
17 |
> > -inherit libtool multilib multilib-minimal eutils pam toolchain-funcs |
18 |
> > flag-o-matic db-use +inherit autotools libtool multilib |
19 |
> > multilib-minimal eutils pam toolchain-funcs flag-o-matic db-use |
20 |
> > MY_PN="Linux-PAM" |
21 |
> > MY_P="${MY_PN}-${PV}" |
22 |
> > @@ -92,7 +92,8 @@ |
23 |
> > src_prepare() { |
24 |
> > epatch "${FILESDIR}"/${PN}-1.1.8-doc-install.patch #473650 |
25 |
> > |
26 |
> > - elibtoolize |
27 |
> > + #Regenerate libtool files as it is too old for sysroot support |
28 |
> > + eautoreconf |
29 |
> > } |
30 |
> > |
31 |
> > multilib_src_configure() { |
32 |
> > @@ -115,6 +116,7 @@ |
33 |
> > $(use_enable nis) |
34 |
> > --with-db-uniquename=-$(db_findver sys-libs/db) |
35 |
> > --disable-prelude |
36 |
> > + --with-sysroot=yes |
37 |
> > ) |
38 |
> > |
39 |
> > will make the X compile succeed. |
40 |
> > |
41 |
> > I think it could be a good idea to have econf add --with-sysroot=yes automatically when cross building. |
42 |
> > Comments? |
43 |
> > |
44 |
> > Jocke |
45 |
> |
46 |
> Sorry, but this list is for portage, the package manager development, not portage tree ebuilds. I have |
47 |
> been trying to get people to refer to the tree as the gentoo tree (same as the repo name) to help avoid |
48 |
> this confusion. |
49 |
> |
50 |
> This should be submitted to bugzilla, where it will be assigned to the pam maintainer. |
51 |
|
52 |
But PAM does not define econf, right? |
53 |
I am suggesting that econf should hide the sysroot stuff so one does not have to modify every ebuild |
54 |
in the tree. Where does econf belong? |
55 |
|
56 |
Jocke |