On Sun, 3 Jul 2005, Thorsten Glaser wrote:
> >Maybe something cheap like this?
> >
> ># 4096 = 0x1000, 262144 = 0x4, 83886080 = 0x500
> >_LT_AC_TAGVAR(archive_cmds, $1)='img_base=`expr ${RANDOM-$$} % 4096 / 2 \*
> >262144 + 83886080`~
> > $CC -shared $pic_f
Todd Vierling dixit:
>I'm fine with this; same reasoning. Thorsten, if you have time to test,
>please do; I'm about to go on a personal trip for a week and don't have time
>for more code testing until then.
Okay. I'm dancing on more than one wedding at the same time tho, and I
would have to rebo
Ralf Wildenhues dixit:
>Just in case you did not know: The ~ in the *_cmds variables will just
>effectively become && when executed. Except the commands are printed
>only right before they are executed.
Ah, okay.
>So if this is MSVC, one could just put in our support for it .. once
>we're throu
Ralf Wildenhues dixit:
>> @@ -3157,6 +3178,17 @@ case $host_os in
>> ;;
>> esac
>> ;;
>> + interix3*)
>> +# Hack: On Interix 3.x, we cannot compile PIC because of a broken gcc.
>> +# Instead, shared libraries are loaded at an image base (0x1000 by
>> +# default) and
I snipped all the stuff we have agreed upon or need further outside
input.
* Thorsten Glaser wrote on Sun, Jul 03, 2005 at 10:39:38PM CEST:
> Ralf Wildenhues dixit:
>
> >Would it maybe be beneficial if Libtool allowed to specify an image
> >base? (I'm not quite sure we want this -- unless a cent
Hi Thorsten, Todd, others,
Just a couple of comments/questions to the patch:
* Thorsten Glaser wrote on Sun, Jul 03, 2005 at 09:22:03PM CEST:
>
> 2005-07-03Thorsten Glaser <[EMAIL PROTECTED]>
>
> * libtool.m4: Add support for Interix (Microsoft Services
> for Unix) 3.0/3.5 bas
>-- Forwarded message --
>From: Todd Vierling <[EMAIL PROTECTED]>
>Message-ID: <[EMAIL PROTECTED]>
>Date: Sun, 3 Jul 2005 14:59:26 -0400 (Eastern Daylight Time)
>Subject: Re: Regarding libtool/Interix/pkgsrc®
[...]
>I hereby release my Interix-specific libtool changes into the pub
Dixi:
>2005-07-03 Thorsten Glaser <[EMAIL PROTECTED]>
>
> * libtool.m4: Add support for Interix (Microsoft Services
> for Unix) 3.0/3.5 based systems using gcc as compiler.
> Originally from NetBSD(R) pkgsrc(R).
Sorry, forgot to mention: this is against branch-1-5.
//mi
Hi Bob,
* Bob Friesenhahn wrote on Sat, Jul 02, 2005 at 10:11:58PM CEST:
> On Sat, 2 Jul 2005, Ralf Wildenhues wrote:
>
> >Do you guys mind if I run libtool.m4 and ltmain.m4sh through `unexpand',
> >and remove all trailing white space (all branches)?
>
> You are saying you want to convert space
* Ralf Wildenhues wrote on Sun, Jul 03, 2005 at 06:58:29PM CEST:
> I have applied these patches to HEAD/branch-2-0 and branch-1-5
> respectively.
Another tidbit: apparently some BSD linker write to stdout on this
test -- now put in config.log. Applied to all branches.
Regards,
Ralf
* m
I have applied these patches to HEAD/branch-2-0 and branch-1-5
respectively. Mostly comment language cleanups, some indentation,
an $() -> ` ` fix, all pretty straightforward.
Regards,
Ralf
2005-07-03 Thorsten Glaser <[EMAIL PROTECTED]>
* config/ltmain.m4sh (func_extract_archives, fun
On Sun, 3 Jul 2005, Thorsten Glaser wrote:
Writing to the build directory at installation time is bad, really
bad, and for our base system builds (which does contain several
libtool'd stuff, such as libgcj) I am already preventing this by
using systrace(1).
I certainly agree that writing to th
Hi Thorsten,
* Thorsten Glaser wrote on Sun, Jul 03, 2005 at 03:06:06PM CEST:
> Ralf Wildenhues dixit:
>
> >I noted a work-around in the MirBSD port of Libtool for root-created
> >leftovers in .libs after a `make install' which requires relinking,
>
> I would rather like to see a way to *PREVENT
Ralf Wildenhues dixit:
>> and let it happen in ${TMPDIR:-/tmp} if it has to be done.
>
>Why that? (This is not a rhetorical question)
Because in that case you do not write to the build directory
at installation time.
>> Writing to the build directory at installation time is bad, really
>> bad,
Ralf Wildenhues dixit:
>Hi Thorsten, Marc, others,
>
>I noted a work-around in the MirBSD port of Libtool for root-created
>leftovers in .libs after a `make install' which requires relinking,
I would rather like to see a way to *PREVENT* relinking if possible,
and let it happen in ${TMPDIR:-/tmp}
Hi Thorsten, Marc, others,
I noted a work-around in the MirBSD port of Libtool for root-created
leftovers in .libs after a `make install' which requires relinking,
namely this patch (which is part of a larger patch), with this ID:
| +# $MirOS: ltmain.in,v 1.15 2005/05/14 16:16:25 tg Exp $
| @@ -2
16 matches
Mail list logo
