* Ralf Wildenhues wrote on Sun, Jul 03, 2005 at 10:39:46AM CEST:
>
> I noted a work-around in the MirBSD port of Libtool for root-created
> leftovers in .libs after a `make install' which requires relinking,
*snip*
> Could you confirm that this patch below fixes the issue instead?
FYI: I have app
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
