| 1 |
On Thu, 12 Mar 2020 11:23:04 +0100 |
| 2 |
Alexis Ballier <aballier@g.o> wrote: |
| 3 |
|
| 4 |
> On Thu, 2020-03-12 at 09:06 +0100, haubi@g.o wrote: |
| 5 |
> > As this native Win32 support is considered highly experimental still, |
| 6 |
> > I |
| 7 |
> > would like to apply the libtool patches for parity via elibtoolize |
| 8 |
> > only, |
| 9 |
> > without applying them in sys-devel/libtool itself yet. |
| 10 |
> > |
| 11 |
> |
| 12 |
> IIRC you need to do it this way, experimental or not: elibtoolize is |
| 13 |
> needed for packages whose autotools have been generated with an old |
| 14 |
> libtool (ie all of them for now). eautoreconf should call elibtoolize, |
| 15 |
> so, after having this in elt-patches, better focus on upstreaming this |
| 16 |
> in libtool itself so that the need for elibtoolize fades away with |
| 17 |
> time. |
| 18 |
> |
| 19 |
> You will probably run into the same issues as in the old days with BSD: |
| 20 |
> not all packages run elibtoolize and you do not have a sane way to |
| 21 |
> force this besides editing ebuilds. |
| 22 |
|
| 23 |
I've long wanted to automatically apply elibtoolize to fix other |
| 24 |
cross-compile issues. I did come up with a rough prototype and it did |
| 25 |
work though I imagine it might break some packages. Maybe it should be |
| 26 |
opt-out rather than opt-in? |
| 27 |
|
| 28 |
Without looking into the meat of the libtool patches themselves, the |
| 29 |
changes seem good. |
| 30 |
|
| 31 |
-- |
| 32 |
James Le Cuirot (chewi) |
| 33 |
Gentoo Linux Developer |
Archives