[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Path to binary in --help or --version

From: J. Grant
Subject: Re: Path to binary in --help or --version
Date: Tue, 08 Jul 2003 19:34:51 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312


I have different win32 builds, which I do not think are sufficiently different in their --help. I'm not sure if they should do this either.

I thought something appended to the help output such as below would make it clear:

Path to binary: /usr/local/bin/make
Report bugs to <address@hidden>.

It would also be useful to others wishing to determine where the make they are running is actually on the filesystem.


on the 08/07/03 03:21, Paul D. Smith wrote:
%% "J. Grant" <address@hidden> writes:

  >> I'm not sure how you imagine this would work, or what use it would
  >> be.  If you run --version don't you already know that you have
  >> different versions?

  jg> For instance, cygwin make ver 3.80 and msys/mingw make ver 3.80,
  jg> both installed, and used by different build processes.  However,
  jg> there are problems if the alternative one is exectuted by mistake.
  jg> I would like to avoid this.

The Cygwin version of GNU make is not supported by the FSF (this list).
If their --version output is not sufficiently distinct so that you can
tell it's not the "real" GNU make, that's something you should raise
with them: it's definitely a problem.

jg> I thought the full path could be displayed, such as "/usr/bin/make" or jg> whatever. This isnt too hard I expect.

  >> As for the other, make doesn't know its own path.  For example, make
  >> doesn't have the path used during the configure encoded anywhere in its
  >> executable: you can copy the make executable anywhere and it will still
  >> work fine.  It has no external files etc. that it needs to find.  The
  >> only thing it could do would be to emulate the way the system searches
  >> the PATH environment variable and find the first matching binary.

  jg> It does IMO, external calls to "sh", which it needs to find...
  jg> And if cygwin make finds msys/mingw sh, nothing works, etc...

The UNIX version of GNU make does not do any parsing of PATH to find the
shell: the path the shell is included fully qualified in the SHELL
variable (default value is /bin/sh).

If you have a request for the Windows port you should ask on

I'm still not very clear on why you want the path to make.  It seems to
me that checking the version value should be able to tell you much more
easily whether you have the correct version or not.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]