1 |
On Sunday 28 August 2005 01:43 pm, Martin Schlemmer wrote: |
2 |
> On Sun, 2005-08-28 at 12:50 -0400, Mike Frysinger wrote: |
3 |
> > On Sunday 28 August 2005 07:28 am, Martin Schlemmer wrote: |
4 |
> > > On Sun, 2005-08-28 at 01:59 -0400, Mike Frysinger wrote: |
5 |
> > > > On Saturday 27 August 2005 03:38 pm, Martin Schlemmer wrote: |
6 |
> > > > > On Sat, 2005-08-27 at 15:11 -0400, Mike Frysinger wrote: |
7 |
> > > > > > On Saturday 27 August 2005 02:58 pm, Martin Schlemmer wrote: |
8 |
> > > > > > > Which reminds me .. anybody going to scream if I update |
9 |
> > > > > > > elibtoolize() to be able to check if it was already run, and |
10 |
> > > > > > > then bug the portage guys to also add it to econf() ? |
11 |
> > > > > > |
12 |
> > > > > > do what now ? |
13 |
> > > > > |
14 |
> > > > > Make econf handle elibtoolize the same way it does gnuconfig ... |
15 |
> > > > |
16 |
> > > > why ? this would help us embedded peeps with uclibctoolize, but |
17 |
> > > > other than that ... maybe i just havent really sat down to figure out |
18 |
> > > > what elibtoolize does ... |
19 |
> > > |
20 |
> > > Note ... I really don`t think uclibctoolize and the other stuff that |
21 |
> > > was added is really appropriate in libtool.eclass, as they touch |
22 |
> > > config.guess, etc .. maybe it would have been better to update |
23 |
> > > gnuconfig to try and apply the patch if in uclibc profile? |
24 |
> > |
25 |
> > uhh, uclibctoolize doesnt touch config.guess ... it only touches |
26 |
> > ltconfig/configure because libtool does not know about uClibc and thus |
27 |
> > will often disable shared library support when trying to build on a |
28 |
> > uClibc host |
29 |
> |
30 |
> Urk, my fault .. maybe its the macosx stuff then. |
31 |
|
32 |
i make no claims as to the sanity of the OS X libtoolize as i had nothing to |
33 |
do with it :) |
34 |
|
35 |
> Either way, how about |
36 |
> integrating them rather with the default way elibtoolize() work? If you |
37 |
> guys are game, I can do it so that the old still will work, and we can |
38 |
> then drop the call to it and elibtoolize once its integrated into |
39 |
> econf(). |
40 |
|
41 |
if you mean dropping uclibctoolize and integrating all of that stuff into the |
42 |
elibtoolize logic, then sure, feel free ... as long as we keep the patches |
43 |
sep though ... |
44 |
-mike |
45 |
-- |
46 |
gentoo-dev@g.o mailing list |