| 1 |
> On Tue, 20 Sep 2016 15:32:05 |
| 2 |
> > Alexis Ballier <aballier@g.o> wrote: |
| 3 |
> > |
| 4 |
> On Tue, 20 Sep 2016 16:21:36 +0100 |
| 5 |
> James Le Cuirot <chewi@g.o> wrote: |
| 6 |
> |
| 7 |
> > On Tue, 20 Sep 2016 17:13:50 +0200 |
| 8 |
> > Alexis Ballier <aballier@g.o> wrote: |
| 9 |
> > |
| 10 |
> > > On Tue, 20 Sep 2016 13:58:32 +0100 |
| 11 |
> > > James Le Cuirot <chewi@g.o> wrote: |
| 12 |
> > > |
| 13 |
> > > > On Tue, 20 Sep 2016 09:15:50 +0200 |
| 14 |
> > > > Michał Górny <mgorny@g.o> wrote: |
| 15 |
> > > > |
| 16 |
> > > > > That said, I don't find the current solution really optimal. A |
| 17 |
> > > > > lot of ebuilds (mine, for example) are not using elibtoolize, |
| 18 |
> > > > > and I expect that they may randomly fail for some people in |
| 19 |
> > > > > corner cases. But I don't feel like adding another eclass to |
| 20 |
> > > > > all ebuilds in the tree is a good idea. |
| 21 |
> > > > > |
| 22 |
> > > > > Portage already does some configure updates in econf. How |
| 23 |
> > > > > about we move the whole thing straight into Portage, |
| 24 |
> > > > > implicitly activated by econf? That would certainly increase |
| 25 |
> > > > > coverage, remove some QA violations from ECLASSDIR and |
| 26 |
> > > > > possibly solve the problem long-term. |
| 27 |
> > > > > |
| 28 |
> > > > > What do you think? |
| 29 |
> > > > |
| 30 |
> > > > I support this. I don't know if it's as big a problem as it was |
| 31 |
> > > > when I last looked at it but cross-compiling often failed |
| 32 |
> > > > without the sysroot patch. Much like you, before becoming a |
| 33 |
> > > > dev, I did not want to file a whole string of bug reports |
| 34 |
> > > > requesting that elibtoolize be added to loads of ebuilds. |
| 35 |
> > > > |
| 36 |
> > > |
| 37 |
> > > |
| 38 |
> > > there is a simple solution to this: profile.bashrc :) |
| 39 |
> > |
| 40 |
> > Indeed, I did some godawful things with bashrc that make my own eyes |
| 41 |
> > bleed but I stopped short of adding elibtoolize. It might work but |
| 42 |
> > if it would work that reliably, why not make it standard? |
| 43 |
> > |
| 44 |
> |
| 45 |
> yes it should; not sure why previous attempts aborted |
| 46 |
|
| 47 |
I've just started cross-compiling again for the first time in about two |
| 48 |
years. Now I remember why I couldn't rely on bashrc for this. |
| 49 |
elibtoolize comes from the libtool eclass and you can't inherit |
| 50 |
additional eclasses from bashrc. I've already been bitten by this issue |
| 51 |
on several ebuilds today such as dev-lang/orc-0.4.26-r1. What can I do |
| 52 |
to help drive this forwards? |
| 53 |
|
| 54 |
-- |
| 55 |
James Le Cuirot (chewi) |
| 56 |
Gentoo Linux Developer |
Archives