Uli Wortmann writes:
>
> Fred> Override.pm overrides it. Simply removing the definition in
> Fred> Override.pm makes things work. This seems to be the most
>
> Hmmh, just a wild guess: I discovered that the calls to getcwd from
> within latex2html use a sloppy syntax, that is &getcwd instead of
> getcwd(). This comes from days before getcwd was defined in
> Override.pm. Can you check that your call in question does indeed call
> getcwd()?
The calls in question are *in* Override.pm, and use the old syntax.
Changing these to the new syntax doesn't help; searching for files
along a path ($TEXINPUTS) doesn't work. The version of getcwd()
defined in Override.pm just doesn't work for me, and
make_directory_absolute() seems pretty close to necessary from where
I'm standing.
> Fred> portable and simplest fix. Is there a platform for which
> Fred> Cwd::getcwd() isn't a working version of getcwd()?
>
> Yup, at least mine :-(
May I ask what you're using? I'm running Solaris 2.6 on an
UltraSPARC. Perhaps Override::getcwd() needs revision?
> Apprently there is prototype mismatch between getenv in Override.pm
> and POSIX.pm. What happens if don't export getenv from Override.pm?
Override::make_directory_absolute() doesn't work, regardless of
whether it uses &getcwd or getcwd(). If this doesn't work, locating
input files located on TEXINPUTS but not in the document directory
doesn't work. This fails for texexpand as well as latex2html.
Having just re-organized my document tree to have less than 200
files in the top-level directory, this is pretty important for me. ;-O
On a related note, l2h doesn't search for the "main" file along
$TEXINPUTS; is there a reason for that? I'm having to give both the
path *and .tex extension* to use a main document file located along
$TEXINPUTS.
-Fred
--
Fred L. Drake, Jr.
[EMAIL PROTECTED]
Corporation for National Research Initiatives
1895 Preston White Drive Reston, VA 20191
