public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: mark@solcom.co.uk
To: gnu-win32@cygnus.com, noer@cygnus.com
Subject: Re: Gnuwin32 b18 "make from source" bugs and fixes.
Date: Mon, 01 Sep 1997 18:30:00 -0000	[thread overview]
Message-ID: <Chameleon.873104463.mark@sulu> (raw)

This article was execllent. Does everyone who tries to 
re-compile the source under NT get these problems, or are a 
few (a lot) of us doing something silly and obvious wrong?

I am now trying to compile GCC as a mips ans m68k cross 
compiler, and would like to build a similar list to the 
above. 

I am using the config options,

--target=m68k-coff and --target=mips-big-ecoff

both configurations stop at the "make-all" stage with the 
following error :-

/src/tcl/unix/../generic/../win/tclWinPort.h:29: sys/timeb.h: 
No such 
file or directory
gcc: Internal compiler error: program cpp got fatal signal 33
make: *** [regexp.o] Error 1
make: *** [all] Error 2
make: *** [all-tcl] Error 2

Can anyone help, Pleaseee?
_______________________________________________
Mark G Hannah          Email:mark@solcom.co.uk
 
SolCom Systems
SolCom House           Tel: +44 1506 461707
Meikle Road            Fax: +44 1506 461717
Kirkton Campus
Livingston             http://www.solcom.co.uk
EH54 7DE               9/1/97  9:50:40 AM
_______________________________________________


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1997-09-01 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-01 18:30 mark [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-08-17  5:12 Tage Westlund

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=Chameleon.873104463.mark@sulu \
    --to=mark@solcom.co.uk \
    --cc=gnu-win32@cygnus.com \
    --cc=noer@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).