Problems with cvs and diff

Problems with cvs and diff

[Ken Miller]

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

I recently installed cvs and the Cygnus Gnu utilties, and immediately
ran into the following problem while trying to commit changes to a cvs
archive:

[c:\src\logman]cvs commit
cvs commit: Examining .
cvs commit: Examining testing
cvs commit: Committing .

Log message unchanged or not specified
a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining
dirs
Action: (continue)
Checking in LogManager.cc;
c:/src/cvsroot/LogMan/LogManager.cc,v  <--  LogManager.cc
new revision: 1.6; previous revision: 1.5
diff.exe: write error                      <------ ERROR HERE
ci: c:/src/cvsroot/LogMan/LogManager.cc,v: diff failed
ci aborted
cvs commit: could not check in LogManager.cc

I looked at the diff source, and found that the problem occurs in the
check_stdout() function in diff.c.  It is complaining that stdout is an
invaild file handle.  What gives with this?  I'm not sure how to fix the
problem, so I'm wondering if anyone else out there is having the same
problem.

I'm using CVS 1.9, RCS 5.7 and the latest Cygnus utilities from
ftp.cygnus.com.

Anyone help?

Cheers!

    -klm.

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

Re: Problems with cvs and diff

[Jim Balter]

Ken Miller wrote:
> 
> I recently installed cvs and the Cygnus Gnu utilties, and immediately
> ran into the following problem while trying to commit changes to a cvs
> archive:
> 
> [c:\src\logman]cvs commit
> cvs commit: Examining .
> cvs commit: Examining testing
> cvs commit: Committing .
> 
> Log message unchanged or not specified
> a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining
> dirs
> Action: (continue)
> Checking in LogManager.cc;
> c:/src/cvsroot/LogMan/LogManager.cc,v  <--  LogManager.cc
> new revision: 1.6; previous revision: 1.5
> diff.exe: write error                      <------ ERROR HERE
> ci: c:/src/cvsroot/LogMan/LogManager.cc,v: diff failed
> ci aborted
> cvs commit: could not check in LogManager.cc
> 
> I looked at the diff source, and found that the problem occurs in the
> check_stdout() function in diff.c.  It is complaining that stdout is an
> invaild file handle.

How do you get that?  check_stdout prints "write error" if either there
was an I/O error on a previous write (in which case it is too late
to know what sort of error it was) or if fclose fails.  You couldn't
know that fclose failed with "invalid file handle" just looking at the
source.

> What gives with this?  I'm not sure how to fix the
> problem, so I'm wondering if anyone else out there is having the same
> problem.
> 
> I'm using CVS 1.9, RCS 5.7 and the latest Cygnus utilities from
> ftp.cygnus.com.
> 
> Anyone help?

Victor Griswold posted here about the work he did on RCS and CVS to
get them to work properly with cygwin, at least with binary files;
I don't recall whether he encountered other problems.  You might
check the archives.

--
<J Q B>
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Installation problem with gcc and ld

[Bernd Prager]

I try to install the devtools of gnu-win32.
By testing of compilation I get always
the error msg:
"LD.EXE: target coff-go32 not found"

In FAQ I found that coff is an image format.
Maybe I'm a little confused by the vast quantity
of new information, but what image was meaned?
Otherwise I did'nt found any "coff-go32" file in
my distribution. Have I to recompile some
libs?

Thanks for your help!
Bernd
_____________________________________________________________________
Bernd Prager
GECKO mbH; Wismarsche Str.3, 18057 Rostock; Germany					
http://www.gecko.de

PGP Key fingerprint = 83 54 6A 3B 7A 9D 6C 0E F3 41 CE 99 11 30 B7 D6
public key by mailto:bpr@gecko.de?Subject=SendPGPKey
_____________________________________________________________________
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

still installation problems

[Bernd Prager]

Hallo,

I'm still trying the installation of GNU-WIN32.

The first problem with missing "coff-go32" seems to was
a mixed installation with DJGPP. So I removed
both packages and reinstalled the WIN-32 distribution.

I unpacked all.tar.gz in one directory with the
preconfigured subdirs, set PATH to ".../H-i386-cygwin32/bin/"
and GCC_EXEC_PREFIX to ".../H-i386-cygwin32/lib/gcc-lib/"
and get follwing result with gcc:

bash$ gcc tst.c
gcc: installation problem, cannot exec `cpp': No such file or directory
gcc: Internal compiler error: program cpp got fatal signal 127

Any ideas what this means, what happend or what I can do or search for?

Thanks,
Bernd
_____________________________________________________________________
Bernd Prager
GECKO mbH; Wismarsche Str.3, 18057 Rostock; Germany					
http://www.gecko.de

PGP Key fingerprint = 83 54 6A 3B 7A 9D 6C 0E F3 41 CE 99 11 30 B7 D6
public key by mailto:bpr@gecko.de?Subject=SendPGPKey
_____________________________________________________________________
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: still installation problems

[collver]

> I unpacked all.tar.gz in one directory with the
> preconfigured subdirs, set PATH to ".../H-i386-cygwin32/bin/"
> and GCC_EXEC_PREFIX to ".../H-i386-cygwin32/lib/gcc-lib/"
> and get follwing result with gcc:
> 
> bash$ gcc tst.c
> gcc: installation problem, cannot exec `cpp': No such file or directory
> gcc: Internal compiler error: program cpp got fatal signal 127
> 
> Any ideas what this means, what happend or what I can do or search for?

  Try looking at your batch file where you set the environment 
variables.


This may fail because of the lowercase variable name:
  set gcc_exec_prefix=c:\cygnus\H-i386-cygwin32\lib\gcc-lib\

This may fail because the spaces before the path will actually be 
stored in the variable:
  set GCC_EXEC_PREFIX =     c:\cygnus\H-i386-cygwin32\lib\gcc-lib\

This ought to work:
  set GCC_EXEC_PREFIX=c:\cygnus\H-i386-cygwin32\lib\gcc-lib\
Ben.
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".