On Thu, 2007-06-28 at 11:38 +0200, Helge Hafting wrote:
> The fix is to let root run a
> "chown -R your_username *" in the top build directory.
> After that, you own all the files and can compile without root's help again.
You got it! Solved, thanks.
I was wondering why I had to wait so long afte
Darren Freeman wrote:
Hi all,
why does "make install" under Linux have so much work to do? It seems to
be linking and building docs etc.
Surely this stuff is meant to be done by "make". Since I have to run
"make install" as root, I generally prefer not to have actual processing
being done here.
> "Darren" == Darren Freeman <[EMAIL PROTECTED]> writes:
Darren> I'm far from an expert on what a makefile should do under each
Darren> target, I'm just commenting on the overall volume of work
Darren> being done by the install target.
There are a lot of commands passing by, but basically thi
On Thu, 2007-06-28 at 07:45 +0200, Jean-Marc Lasgouttes wrote:
> > "Darren" == Darren Freeman <[EMAIL PROTECTED]> writes:
>
> Darren> Hi all, why does "make install" under Linux have so much work
> Darren> to do? It seems to be linking and building docs etc.
>
> Darren> Surely this stuff is m
> "Darren" == Darren Freeman <[EMAIL PROTECTED]> writes:
Darren> Hi all, why does "make install" under Linux have so much work
Darren> to do? It seems to be linking and building docs etc.
Darren> Surely this stuff is meant to be done by "make". Since I have
Darren> to run "make install" as ro
Hi all,
why does "make install" under Linux have so much work to do? It seems to
be linking and building docs etc.
Surely this stuff is meant to be done by "make". Since I have to run
"make install" as root, I generally prefer not to have actual processing
being done here.
Have fun,
Darren
