Thanks Tim. Meanwhile I have looked at the output, and found that the actual error message is as follows:
> > configure.ac:3814: error: `\r' is already registered with AC_CONFIG_FILES. > > autoconf/status.m4:848: AC_CONFIG_FILES is expanded from... > > configure.ac:3814: the top level > > Autom4te::FileUtils::xsystem(/usr/autotool/devel/share/autoconf/Autom4te/FileU tils.pm:29 Indeed a problem with an EOL character. However, I don't really know what to do with the above error message, and what the next debugging step could/should be. Any ideas? Thanks a lot. -Mario P.S.: How can I set the "cygwin mount point to text mode"? ----- Original Message ----- From: "Tim Van Holder" <[EMAIL PROTECTED]> To: "Mailing Lists" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, April 01, 2004 09:59 Subject: Re: already registered with AC_CONFIG_FILES > Mailing Lists wrote: > > Hi all! > > > > I am trying to compile some software (VLC from the VideoLAN project) on W2K/CygWin. Unfortunately, during the config, I get an > > error. I have already contacet the VideoLAN malining list, but to no avail. I will also contact the CygWin mailing list, but for the > > time being I hope to get some help here. > > > > This is the error message I get: > > > > ' is already registered with AC_CONFIG_FILES. > > autoconf/status.m4:848: AC_CONFIG_FILES is expanded from... > > configure.ac:3814: the top level > > Autom4te::FileUtils::xsystem(/usr/autotool/devel/share/autoconf/Autom4te/FileU tils.pm:29 > > > > Please note the single single-quote at the beginning of the error message. I have included the command line after the main body of > > this post. > > The single quote suggests that a carriage return character is causing > trouble, so one of the files being processed by autoconf or automake is > probably in DOS text format but expected to be in Unix text format. Try > setting the cygwin mount point to text mode, or re-extracting the source > files using options that will do the DOS-to-Unix conversion for you > (e.g. -a for unzip). > > Having said that, this _probably_ should not occur, so it may be a bug.
