From: N8TM@aol.com
To: cygwin@sourceware.cygnus.com
Subject: makeinfo barfs at relative path includes and \r line terminators
Date: Fri, 31 Dec 1999 13:28:00 -0000 [thread overview]
Message-ID: <0.9769a2c6.259d5b53@aol.com> (raw)
Message-ID: <19991231132800.DEL39Vw8BplDzTpmcdB_XrIUuqMvGGpHVV1GIEwl4xE@z> (raw)
I'm sure this has been covered earlier, but now that we have been handed
working copies of info.exe (thanks to Chuck Wilson and others), I've found
out the work-arounds to get makeinfo to run on the gcc-2.96 source
distribution:
As I recommended previously, 'gzip -r texinfo' so that you do not attempt to
replace the makeinfo which comes with cygwin.
Remove all \r line terminators from the .texi files in gcc and gcc/f. The
distribution has a number of these, but many of the files have none. I
suppose this could be reported to gcc-bugs, but maybe it's a bug in cygwin
makeinfo as well, that it cannot accept \r where the usual gnu makeinfo does.
Find all the @include's in these files and replace them with absolute paths.
Is this a Windows version-dependent problem? I'm running Windows 2000 RC2,
because it is able to complete the testsuite, which neither W95C nor NT4 SP3
or SP5 could do.
Tim
tprince@computer.org
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-12-31 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-30 17:05 N8TM [this message]
1999-12-31 13:28 ` N8TM
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0.9769a2c6.259d5b53@aol.com \
--to=n8tm@aol.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).