On 5/15/06, Terry Younkin <[EMAIL PROTECTED]> wrote:
>
>
>
> On 5/15/06 9:55 AM, "Alexander K. Hansen" <[EMAIL PROTECTED]>
> wrote:
>
> > On 5/15/06, Terry Younkin <[EMAIL PROTECTED]> wrote:
> >> Hello List -
> >>
> >> I am still having problems with my updating, and the problem seems to have
> >> remained the same as in my previous email to this list, "Install failed."
> >> During the weekend, I tried to narrow the problem, but I'm sure I'm still
> >> cutting a rather wide swath.
> >>
> >> At first, I was assuming I had more than one instance of "texi2html"
> >> installed, and I do believe there was something wrong there.  However,
> >> numerous installs and removals of that program (via Fink) have me doubting
> >> that the problem is specifically related to texi2html.  What I have noticed
> >> is that whenever an install of "autoconf2.5" is attempted, there is a
> >> failure identical to my original failure.  Although a bit lengthy, here's
> >> the entire log output from Fink Commander when I try to install
> >> "autoconf2.5:"
> >>
> >> **** (Start of paste)
> >>
> >>
> >
> > <snip>
> >
> >> cd doc && make html
> >> texi2html -split_chapter ./autoconf.texi
> >> ** Unknown command [EMAIL PROTECTED]' (left as is) (l. 8)
> >> ** Unknown command [EMAIL PROTECTED]' (left as is) (l. 15550)
> >> ** Unknown command [EMAIL PROTECTED]' (left as is) (l. 15585)
> >> ** Unknown command [EMAIL PROTECTED]' (left as is) (l. 15633)
> >> ** Unknown command [EMAIL PROTECTED]' (left as is) (l. 15641)
> >> texi2html -split_chapter ./standards.texi
> >> install -d -m 755
> >> /sw/src/fink.build/root-autoconf2.5-2.59-7/sw/share/doc/autoconf2.5/html
> >> install -m 644 doc/*.html
> >> /sw/src/fink.build/root-autoconf2.5-2.59-7/sw/share/doc/autoconf2.5/html/
> >> install: doc/*.html: No such file or directory
> >> ### execution of install failed, exit code 71
> >> Removing build lock...
> >> /sw/bin/dpkg-lockwait -r fink-buildlock-autoconf2.5-2.59-7
> >> (Reading database ... 146776 files and directories currently installed.)
> >> Removing fink-buildlock-autoconf2.5-2.59-7 ...
> >> Failed: phase installing: autoconf2.5-2.59-7 failed
> >>
> >>
> >> **** (End of paste)
> >>
> >>
> >> I am finding no information regarding this in the Fink FAQs, nor am I
> >> finding anything through many Google searches.  I am now wondering whether
> >> the problem is described in the line (toward the end of the log):
> >>
> >> "install: doc/*.html: No such file or directory"
> >>
> >> I cannot find a file or directory named "doc/*.html" either.  If indeed 
> >> this
> >> line from the log shows my problem, frankly, I have no idea what to do 
> >> about
> >> it.  Perhaps I am way off base.  What do you all think about this?
> >>
> >>
> >>
> >>
> >>
> >> -- Terry
> >>
> >>
> >>
> >>
> >
> > You don't have doc/*.html because those files are supposed to be
> > created via the texi2html command which is failing.
> >
> > So for this last run, was the texi2html command from the Fink
> > texi2htmlopackage, the system, or is it the same for both?
> >
>
> I shall have to claim ignorance here, Alexander, in that I'm not certain
> what you mean.  For the run you see above, I simply had Fink Commander
> install "autoconf2.5."  Any command was run automatically from that point
> on; I made no input.  I hope this answers your question, but if not, please
> ask again.
>

Hmm...strangely enough, now that I look at it, autoconf2.5 wants
Fink's texi2html to be installed when it builds.  However, if yours
isn't producing a /sw/bin/texi2html executable  that might explain
what's going on.  Try "fink reinstall texi2html", and then run "which
texi2html" and see if Fink's /sw/bin/texi2html shows up.

> > And, you mentioned that your fink-installed texi2html didn't generate
> > a /sw/bin/texi2html executable.  Did you try a "fink rebuild
> > texi2html" and then install it?
>
> I did indeed do a "fink rebuild texi2html."  In fact, I installed and
> reinstalled it several times over the weekend.
>
> You are correct that originally there was no executable.  Subsequent runs
> did install one, however, the name of the file in /sw/bin/ is
> "texi2html.texi2html" rather than "texi2html," which seems odd.

Same here--though I do have /sw/bin/texi2html which is linked to
/sw/bin/texi2html.texi2html.

> Interestingly enough, my desktop G4 (running similar, but not exact,
> software as the PowerBook) has the same file in the same folder.  But what
> is really odd is that the file on the desktop G4 was *not* named
> "texi2html.texi2html" two days ago; rather, it was named "texi2html" when I
> first checked there.  (I have not updated the desktop machine for at least a
> month.)
>
> As you may recall, the PowerBook was originally showing a file in /sw/bin
> named "texi2html" which was a generic looking icon, and "Get Info" could not
> resolve it.  At least now it is an executable, even though named strangely
> in my opinion.
>
>
>

It's set up to be that way deliberately for some reason via the
"alternatives" system--which (I believe) means basically that you can
have several different packages (e.g. of different versions) that
provide a command and Fink picks some version to be the one that
works.

I would guess that what's going on here is that you aren't getting
/sw/bin/texi2html, and the system's /usr/bin/texi2html is being used.
There's a note in the texi2html package description that mentions
incompatibilities with Tiger's built-in version.

-- 
Alexander K. Hansen
Fink Documenter (for now)
Help keep AKH in Fink!  Go to
http://ldx3.psfc.mit.edu/~hansen/
and contribute to the Mini fund.


_______________________________________________
Fink-beginners mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to