From: Mumit Khan <khan@xraylith.wisc.EDU>
To: "Kai Henningsen" <kai@cats.ms>
Cc: "hark sng-" <passhark@hotmail.com>,
cygwin@sourceware.cygnus.com, Earnie Boyd <earnie_boyd@yahoo.com>
Subject: Re: GCC
Date: Thu, 30 Sep 1999 23:42:00 -0000 [thread overview]
Message-ID: <199909131442.JAA05891@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990930234200.G0hEdl7Fxz-lxKqvQFamynNUX8Ug1ofx2UzCTyY37TY@z> (raw)
In-Reply-To: <E11QXZo-0004UX-00@charlotte.intern.cats.ms>
"Kai Henningsen" <kai@cats.ms> writes:
> On 23 Aug 99, at 11:57, Mumit Khan wrote:
>
> > "hark sng-" <passhark@hotmail.com> writes:
> > > I tried compiling a simple program using Ming32 and Cywin GCC, but in =
> both i
> > > get the CPP program giving me a error message saying: the -remap optio=
> n is
> > > no understood.
>
> Same problem here: just calling cpp without any arguments is
> enough to make this happen (cpp complains about -remap in a
> loop until no more processes).
I believe hark sng-'s problem had to do with having GNAT installed, which
"hijacks" every other installation via a registry entry. See my "fixes"
area for workaround:
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/gcc.html#gcc295-fixes
My next release of gcc will *ignore* these hidden registry entries to avoid
these conflicts. Hopefully GNAT folks will take care and use a more
reasonable key next time (vendor specific versioned key perhaps) to avoid
this problem.
>
> Installation sequence:
>
> 1. B20.1
> 2. Snapshot 19990905
> 3. gcc 2.95
> 4. gcc 2.95 dev-ss
>
> The weird thing is it looks as if it worked for a short time before
> breaking this way.
You need to be sure of that if that is indeed the case (that it worked
for a short period)!
If you don't have GNAT installed, then we obviously need to figure this
out. Please look through the output of:
$ gcc -print-search-dirs
and see where it's looking for things.
$ gcc -print-file-name=specs
should print the full pathname to the specs files.
>
> > 1. For cygwin, provide the output of cygcheck:
> >
> > $ cygcheck -s -r
>
Thanks. These look good.
>
>
> > 3. compiler version and some runtime info:
> >
> > $ gcc -v filename.c
>
> Using builtin specs.
Not the "builtin specs". That means GCC is just not finding what it's
supposed to.
Earnie, the newer versions of gcc provide two different cpp's -- one
goes in <exec_prefix>/bin and other one goes deep into the compiler
directory. GCC uses *only* the second one, and the first one is provided
for other programs or users who may want to run cpp directly (eg., imake).
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-09-30 23:42 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-23 8:50 GCC hark sng-
1999-08-23 9:59 ` GCC Mumit Khan
1999-08-31 23:49 ` GCC Mumit Khan
1999-09-13 8:01 ` GCC Kai Henningsen
1999-09-13 8:54 ` Mumit Khan [this message]
1999-09-14 1:54 ` GCC Kai Henningsen
1999-09-14 9:41 ` GCC Mumit Khan
1999-09-30 23:42 ` GCC Mumit Khan
1999-09-30 23:42 ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Mumit Khan
1999-09-30 23:42 ` GCC Kai Henningsen
1999-08-31 23:49 ` GCC hark sng-
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 11:56 GCC John Emmas
2008-08-18 12:11 ` GCC Hugh Sasse
2008-08-18 12:20 ` GCC John Emmas
2002-05-25 9:46 gcc hongxun lee
2002-01-02 9:14 gcc Givon Zirkind
2002-01-03 16:21 ` gcc Tim Prince
2001-05-07 17:49 gcc Bryan Higgins
2001-05-08 6:00 ` gcc Earnie Boyd
2001-03-31 11:06 gcc John Weeks
2001-03-31 13:06 ` gcc Christopher Faylor
2001-03-31 14:14 ` gcc John Weeks
2001-03-31 14:24 ` gcc Christopher Faylor
2000-11-09 11:01 GCC Earnie Boyd
2000-11-09 7:19 GCC Schaible, Joerg
2000-11-09 7:13 GCC Milan Stanojevic
2000-11-09 7:19 ` GCC Cal Erickson
2000-11-09 10:45 ` GCC Milan Stanojevic
1999-09-14 5:48 GCC Earnie Boyd
1999-09-14 6:54 ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Earnie Boyd
1999-09-13 8:16 GCC Earnie Boyd
1999-09-14 2:00 ` GCC Kai Henningsen
1999-09-14 9:56 ` GCC Michael V. Nikolaev
1999-09-30 23:42 ` GCC Michael V. Nikolaev
1999-09-30 23:42 ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Earnie Boyd
1998-11-29 10:34 Gcc Haynes, Dan
1998-11-29 1:32 Gcc Holger Burkarth
1998-11-03 13:49 gcc marc_auslander
1998-07-08 10:01 GCC Earnie Boyd
1998-07-03 16:33 GCC Bruno da Rocha
1997-12-05 6:13 gcc Mark Young (in6)
1997-10-16 20:09 GCC Earnie Boyd
1997-10-15 17:59 GCC David Vang
1997-10-08 2:57 gcc Brad Haack
1997-09-24 2:09 gcc nazg
1997-09-23 13:38 gcc Earnie Boyd
1997-09-22 9:29 gcc Earnie Boyd
1997-09-22 6:23 gcc nazg
1997-09-20 0:35 gcc young lee
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=199909131442.JAA05891@mercury.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=earnie_boyd@yahoo.com \
--cc=kai@cats.ms \
--cc=passhark@hotmail.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).