The results of your email command are provided below. Attached is your
original message.
- Results:
Ignoring non-text/plain MIME parts
- Done.
--- Begin Message ---
--- End Message ---
___
Autoconf mailing list
[EMAIL PROTECTED]
http://lists.gnu.or
On Sat, 11 Sep 2004, Daniel Jacobowitz wrote:
That, unfortunately, is too convoluted to figure out without real study.
Without a clear example, I simply find the full, real path of the executable
and presume that the standard ../share/${program}/ is correct. Probably
an illuminating example would
Bob Friesenhahn wrote:
>
> On Sat, 11 Sep 2004, Daniel Jacobowitz wrote:
> >> That, unfortunately, is too convoluted to figure out without real study.
> >> Without a clear example, I simply find the full, real path of the executable
> >> and presume that the standard ../share/${program}/ is correc
On Sat, 11 Sep 2004, Bruce Korb wrote:
Bob Friesenhahn wrote:
On Sat, 11 Sep 2004, Daniel Jacobowitz wrote:
That, unfortunately, is too convoluted to figure out without real study.
Without a clear example, I simply find the full, real path of the executable
and presume that the standard ../share/${
Hi Daniel,
> You give it argv[0], BINDIR, and OTHERDIR; it computes the relative
> path between bindir and otherdir, finds your application in $PATH or
> similar, and works out the likely location of otherdir.
Does argv[0] always contain a path on all Unixes? IIRC, some old ones
put just `ls' t
On Sat, 11 Sep 2004, Ralph Corderoy wrote:
You give it argv[0], BINDIR, and OTHERDIR; it computes the relative
path between bindir and otherdir, finds your application in $PATH or
similar, and works out the likely location of otherdir.
Does argv[0] always contain a path on all Unixes? IIRC, some
Ralph Corderoy <[EMAIL PROTECTED]> writes:
> Does argv[0] always contain a path on all Unixes?
No. It contains exactly the string passed in by execve, unmodified. It
can be arbitrary.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Ger
Hi,
I had stopped work on a project which uses autoconf and automake
about 6 months ago. At that time "make distcheck" was working
without any problems. Unfortunately, I do not know which versions
of autoconf and automake I had been using 6 months ago.
I restarted work on the project yesterday,
Hi Andreas,
> Ralph Corderoy <[EMAIL PROTECTED]> writes:
> > Does argv[0] always contain a path on all Unixes?
>
> No. It contains exactly the string passed in by execve, unmodified.
> It can be arbitrary.
I wasn't clear. I realise it isn't always an absolute path, and is
normally whatever's
On Sat, 11 Sep 2004, Ralph Corderoy wrote:
normally whatever's passed to execve(2). I was just trying to point out
that some old Unixes, Xenix? -- I can't remember, effectively strip any
path, absolute or relative, from execve's argument before it turns up in
argv[0], i.e. execve("./ls", ...) and
Following bug was reported against the Debian packaging of
Autoconf. It seems like more of an upstream thing to me, because
Debian has little to do with Mac OS X, so I'm passing it along
instead of taking action myself.
Start of forwarded message
From: Jo
11 matches
Mail list logo
