Mail Archives: cygwin/1998/07/11/09:09:15
Hi Fred,
Thanks very much for your response. Unfortunately, it didn't help. I
created the directory path, copied the files, and byacc is still generating
bad files.
Desperate, I removed cygwin32 and reinstalled it as d:\cygnus\b19
(unfortunately, I don't have sufficient space on c:). This did NOT help,
and I'm still having the problem.
Due to the reinstallation, my mount points now look like this:
Device Directory Type Flags
d:\TEMP /tmp native text!=binary
\\.\tape1: /dev/st1 native text!=binary
\\.\tape0: /dev/st0 native text!=binary
\\.\b: /dev/fd1 native text!=binary
\\.\a: /dev/fd0 native text!=binary
d: / native text!=binary
Any ideas at all? This is really bizarre, as I have another system (similar
to the old directory structure, where cygnus is installed in
e:\packages\cygnus\b19), and Cygnus works there! I really wish I knew why.
Could this have some sort of issue with tmp? Perhaps the mount point
doesn't work, and it must be hard-coded? I'm knocking my head against the
wall comparing these two systems, and I just don't see it. (I don't have a
"tmp" directory on the working system)
FYI: The system that's failing is a "fresh" system. Two days ago, I
installed NT V4.0 Workstation, NT Service Pack 3, IE V4.01 SP1, VC++ V5.0,
VC++ Service Pack 3, cygnus, and perl.
Any advice would be greatly appreciated, thanks!
-- Jeff
-----Original Message-----
From: Fred Reimer <Fred DOT Reimer AT Bellsouth DOT net>
To: Jeff Coffler <Jeff DOT Coffler AT software DOT com>; gnu-win32 AT cygnus DOT com
<gnu-win32 AT cygnus DOT com>
Date: Friday, July 10, 1998 9:46 AM
Subject: Re: Problems with Cygnus and paths (default / path, /tmp, and more)
is confusing byacc
>Hope this will help.
>
>Try creating e:\Cygnus\B19\share and copying bison.hairy and bison.simple
to
>this directory. I think the path to these files may be hard-coded in the
>executable, and your root is mounted from e:.
>
>Fred
>
>-----Original Message-----
>From: Jeff Coffler <Jeff DOT Coffler AT software DOT com>
>To: <gnu-win32 AT cygnus DOT com>
>Date: Friday, July 10, 1998 12:22 PM
>Subject: Problems with Cygnus and paths (default / path, /tmp, and more) is
>confusing byacc
>
>
>>Hi folks,
>>
>>I checked the FAQ, and most of the archives, and I have a problem that's
>>stumping me.
>>
>>I'm not using much of the cdk, but I am trying to use byacc (from cygnus
>>b19). It seems that, on certain systems, byacc is generating a .c file
>>that's just plain wrong, given it's input (and the results won't compile
>>using Microsoft VC++ V5.0).
>>
>>Some basic setup stuff:
>>
>>Cygnus is installed in: e:\packages\cygnus (so that the bin directory
is
>>in "e:\Packages\Cygnus\B19\H-i386-cygwin32" - but I don't believe case
>>matters).
>>
>>The stuff I'm trying to build is on e: as well, deep in a directory
>>
>>My /tmp directory: d:\temp (but I tried this half a dozen different
>>ways - bash isn't complaining about my setup)
>>
>>
>>Gleening from the FAQ, my mount points look as follows:
>>
>>Device Directory Type Flags
>>e:\packages\cygnus\b19\h-i386-cygwin32 /usr native
>>text!=binary
>>d:\TEMP /tmp native text!=binary
>>\\.\tape1: /dev/st1 native text!=binary
>>\\.\tape0: /dev/st0 native text!=binary
>>\\.\b: /dev/fd1 native text!=binary
>>\\.\a: /dev/fd0 native text!=binary
>>e: / native text!=binary
>>
>>
>>When I invoke byacc, I don't get any unusual errors. But the resulting
>>output is (clearly) wrong. On a different system (also NT V4.0, with
>>different directory paths), byacc is working fine.
>>
>>Can anyone offer advice?
>>
>>I've also tried with /usr -> e:\packages\cygnus\b19, but that didn't help
>>either. As I said, I'm stumped.
>>
>>Any advice would be greatly appreciated, thanks!
>>
>> -- Jeff
>>
>>
>>-
>>For help on using this list (especially unsubscribing), send a message to
>>"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
>>
>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -