public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Kai Henningsen" <kai@cats.ms>
To: Kai Henningsen <kai@cats.ms>, hark sng- <passhark@hotmail.com>,
	Mumit Khan <khan@xraylith.wisc.EDU>,
	earnie_boyd@yahoo.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: GCC
Date: Thu, 30 Sep 1999 23:42:00 -0000	[thread overview]
Message-ID: <E11Qswb-0007hp-00@charlotte.intern.cats.ms> (raw)
Message-ID: <19990930234200.BH4Tgo8NKJi9qJqf5_jwbP-vJEojH3wYjowhg-ddjlI@z> (raw)
In-Reply-To: <19990914124954.1255.rocketmail@web119.yahoomail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]

On 14 Sep 99, at 5:49, Earnie Boyd wrote:

> --- Kai Henningsen <kai@cats.ms> wrote:
> > On 13 Sep 99, at 8:18, Earnie Boyd wrote:
> >
> > > --- Kai Henningsen <kai@cats.ms> wrote:
> > > -8<-
> > > > Found: f:\cygnus\cygwin-b20\H-i586-cygwin32\bin\cpp.exe
> > > > Found: f:\cygnus\CYGWIN~1\H-I586~1\bin\cpp.exe
> > > -8<-
> > >
> > > This should not be here.  You've moved/copied it from the correct location
> > > underneath lib/gcc-lib/i586-cygwin32/<gcc-version>/.
> >
> > I haven't touched it. Let's see ...
> >
> > bash-2.02$ find //f/cygnus/ -name "*cpp*" 2>/dev/null
> > //f/cygnus/cygwin-b20/H-i586-cygwin32/bin/cpp.exe
> > bash-2.02$
> >
> > ... so *none* of the packages I installed put cpp in gcc-lib. And
> > neither did I get two copies as Mumit said. [*]
> >
>
> _YES_ it did!  Look again!  If it's not there, you've a problem with the
> installation.

I installed the stuff exactly as I reported. Really.

I think I'm gonna wipe and reinstall it, but I really don't understand
how something like that could have gone wrong.

I guess I'm spoiled by "real Unix".

> > bash-2.02$ find //f/cygnus/ -name hggbjhb
> > find: //f/cygnus/cygwin-b20/H-i586-cygwin32/etc: No such file or directory
> > find: //f/cygnus/cygwin-b20/H-i586-cygwin32/i586-cygwin32: No such file or
> > direc
> > tory
> > find: //f/cygnus/cygwin-b20/H-i586-cygwin32/i586-pc-cygwin32: No such file or
> > di
> > rectory
> > find: //f/cygnus/cygwin-b20/H-i586-cygwin32/lib: No such file or directory
> > find: //f/cygnus/cygwin-b20/H-i586-cygwin32/libexec: No such file or
> > directory
> > find: //f/cygnus/cygwin-b20: No such file or directory
> > bash-2.02$
> >
> > Looks like a find (or library) bug.
> >
> >
>
> The directory routines were completely rewritten.  Although, the //f should
> work for backward compatibility it should really be /cygdrive/f/.  Try your
> find with /cygdrive/f instead of //f.

Exactly the same results (modulo pathnames).

> Also, make certain that you have only one cygwin1.dll in your PATH.  Since find

I have.

> is having problems use the FileManager Find tool to check it.  I didn't notice

Find seems to do the right thing, except for the error messages.


Regards - Kai Henningsen

--
http://www.cats.ms
Spuentrup CTI       Fon: +49 251 322311 0
Windbreede 12       Fax: +49 251 322311 99
D-48157 Münster     Mob: +49 161 3223111
Germany             GSM: +49 171 7755060

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~1999-09-30 23:42 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-14  5:48 GCC Earnie Boyd
1999-09-14  6:54 ` Kai Henningsen [this message]
1999-09-30 23:42   ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Earnie Boyd
  -- 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-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
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     ` GCC Mumit Khan
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-
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=E11Qswb-0007hp-00@charlotte.intern.cats.ms \
    --to=kai@cats.ms \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=earnie_boyd@yahoo.com \
    --cc=khan@xraylith.wisc.EDU \
    --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).