[bug #23262] sudo -E gmake install tries to run plmerge for aggregate project on FreeBSD

[Nicola Pero]

Follow-up Comment #1, bug #23262 (project gnustep):

Do you have a reproducible test case ?

Else it's very difficult to say. :-(

My guess is that the problem you are having is due to the
fact that your 'sudo -E make install' is actually building
some software as root; not just installing it.

That's almost certainly due to the fact that you didn't do
a 'make' first - maybe you forgot in that specific case.

The correct procedure is:

 * type 'make' to compile.  This will run plmerge as your local
user, which should work.

 * type 'sudo -E make install' to install.  This will not plmerge because
everything is already built.  It will only install things as root.  If you
invoke this (by mistake) when things are not already built, it will try
building them (it can't install without building) - running plmerge as root,
which seems to fail in your setup. [a few years ago I tried convincing people
to
change 'make install' so that it wouldn't automatically build,
which I think it's confusing, but was voted down big time because
the standard Unix way of doing things is that 'make install' both
builds (if needed) and installs, so we're stuck with that and
you need to be aware of it]

I suspect that that is the case, also because you report that 

> the following line fails by trying to run plmerge:
> sudo -E gmake messages=yes install
> when the following line succeeds (plmerge isn't run):
> sudo -E gmake install messages=yes 

as far as I know the two commands are completely identical.

Did you try them in sequence ?  Then maybe the first one 
failed because it detected that a rebuilt was needed, 
did the rebuilt and failed trying to run plmerge 
(which is the last command), but managed to rebuild enough 
that the second one thought things were built and it didn't
need to build again, so it didn't fail.

Anyway, if you have the problem again, you should:

 * type 'make distclean'.  If you have local files owned by root, 
it would suggest that the 'sudo -E make install' was building, 
not just installing, which is either due to yourself having
forgotten to do a plain 'make' first, or due to sloppy custom
code in your makefiles (which maybe you don't care about though)

 * type 'make messages=yes'

 * type 'sudo -E make install messages=yes'.  This should never fail.  If it
fails, it could be a real problem; please send me
the detailed logs.

Thanks

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?23262>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/