[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: branch-1-5: root-owned libtool files in build tree after relink
From: |
Ralf Wildenhues |
Subject: |
Re: branch-1-5: root-owned libtool files in build tree after relink |
Date: |
Sun, 3 Jul 2005 15:57:04 +0200 |
User-agent: |
Mutt/1.4.1i |
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* relinking if possible,
ACK. branch-2-0/HEAD does relinking in fewer cases. I have not
checked, though, if the set of cases can be reduced further.
> and let it happen in ${TMPDIR:-/tmp} if it has to be done.
Why that? (This is not a rhetorical question)
> 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).
Does that mean relinking will then fail? (I'm sorry, but I don't know
much about systrace yet.)
> That would improve the overall quality of GNU software, too.
It would considerably ease building/packaging, yes. Anything else?
Cheers,
Ralf