public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Korn <dkorn@pixelpower.com>
To: 'Elwyn Campbell' <Elwyn.Campbell@nautronix.com.au>,
	"'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: RE: Problems with arm-elf installation for cygwin
Date: Tue, 12 Dec 2000 02:05:00 -0000	[thread overview]
Message-ID: <718D38CAB6E0D011B2C90060970C28A56424FA@EXCHANGESERVER> (raw)

>I'm having problems with installing the gcc cross-compiler under the latest
>version of Cygwin. I have downloaded the latest versions of binutils, gcc
>and newlib.

 ...[snip!]... 
 
>.../gcc/texinfo/makeinfo/makeinfo -I/src/gcc/gcc-2.95.2/gcc -o cpp.info
>/src/gcc/gcc-2.95.2/gcc/cpp.texi
./src/gcc/gcc-2.95.2/gcc/cpp.texi: no such file or directory
>make[1]: *** [cpp.info] Error 2
>make[1]: Leaving directory '/tmp/build/gcc/gcc'
>make: *** [all-gcc] Error 2
>
>I have checked and the file cpp.texi exits and is in the correct directory.

  Yeah. Cygwin does something different when it comes to texinfo, I don't
quite know what. Assuming you've got all the documentation you need already,
the quickest way to get round this problem and carry on compiling is to

  touch gcc.info; touch cpp.info

...works for me, anyway. (Beware; when it comes to installation this will
of course overwrite any installed gcc.info or cpp.info with blank files, so
if you already have working copies of those files, you might want to save
them somewhere.)

        DaveK
--
The Boulder Pledge: "Under no circumstances will I ever purchase anything
offered to me as the result of an unsolicited email message. Nor will I
forward chain letters, petitions, mass mailings, or virus warnings to large
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

             reply	other threads:[~2000-12-12  2:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-12  2:05 David Korn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-11 22:33 Elwyn Campbell

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=718D38CAB6E0D011B2C90060970C28A56424FA@EXCHANGESERVER \
    --to=dkorn@pixelpower.com \
    --cc=Elwyn.Campbell@nautronix.com.au \
    --cc=gcc-help@gcc.gnu.org \
    /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).