Re: bash v2.05b.0 + nmake v7.10.3077 problem
On Thu, Nov 13, 2003 at 06:21:33PM +0100, Hannu E K Nevalainen wrote: Not that I see this to be important; 1. I see CRLF line endings. That confirms that there is something wrong elsewhere (probably at my ISP or someplace between there and the Cygwin list) as where you see cr nl, I see nl nl.. AFAIK, none of the software I use does any mangling in this fashion (and I haven't had the problem before..) 2. No double linefeeds in 'less' nor in the old Win-GUI editor I use (name: PFE). I've downloaded the file from the archives just to make sure I have the right one somewhere. It doesn't change much, though: I still don't see much of anything that might be suspicious in the file. A minimal testcase would be nice.. rlc -- Pollyanna's Educational Constant: The hyperactive child is never absent. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
bash v2.05b.0 + nmake v7.10.3077 problem
Hello, I updated to msvc 7.1. Before I used msvc 6.0 with no problems in compiling from bash. Now nmake has problems to compile in the bash enviroment. The following error occured: Makefile(147) : fatal error U1054: cannot create inline file '' Has anyone the same problems? Is it a problem of nmake or my makefile (i use qmake to generate my makefiles)? Thanks in advance, Lars. -- Lars Monecke http://www.monecke.de -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: bash v2.05b.0 + nmake v7.10.3077 problem
Hello Lars, On Wed, Nov 12, 2003 at 12:15:34PM +0100, Lars Monecke wrote: I updated to msvc 7.1. Before I used msvc 6.0 with no problems in compiling from bash. Now nmake has problems to compile in the bash enviroment. The following error occured: Makefile(147) : fatal error U1054: cannot create inline file '' Has anyone the same problems? Is it a problem of nmake or my makefile (i use qmake to generate my makefiles)? You're giving us very little (way too little) information to help you in any way. Have a look at http://cygwin.com/problems.html and perhaps post things like: * the Makefile (especially line 147 seems to be of interest) * a step-by-step description of what you're doing * whether it works when invoking nmake from the Windows command shell (will help to find out whether it has anything to do with Bash, Cygwin, etc.) rlc -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: bash v2.05b.0 + nmake v7.10.3077 problem
Hello Ronald, here some additional information... Ronald Landheer-Cieslak wrote: * the Makefile (especially line 147 seems to be of interest) Please refer to attachment. But line 147 seems to the end of the file... The Makefile is generated by qmake 1.06c. * a step-by-step description of what you're doing here a the command history: $ qmake $ nmake clean $ nmake The implementation files were compiled but the link command (or before) failed with fatal error U1054. If i open then a cmd and switch to the directory and type nmake, the lib will be linked. I can reproduce this on another machine. * whether it works when invoking nmake from the Windows command shell My compilation works fine with a normal command shell. I diffed the generated Makefiles (under bash and cmd) and the only difference is the uppercase of the c: drive-letter. Some more enviroments (i can send you see full cygcheck.out by email): Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4 Package Version _update-info-dir 00223-1 base-files 2.6-1 cygwin 1.5.5-1 bash 2.05b-16 Best Regards Lars. -- Lars Monecke http://www.monecke.de PGP-Key unterhttp://www.monecke.de/pgp-key.asc# # Makefile for building: dispo-irm-io # Generated by qmake (1.06c) (Qt 3.2.3) on: Thu Nov 13 11:36:51 2003 # Project: io.pro # Template: lib # Command: $(QMAKE) -o Makefile io.pro # ### Compiler, tools and options CC = cl CXX = cl LEX = flex YACC= byacc CFLAGS = -nologo -Zm200 -W3 -MD -Zi -Gm -DUNICODE -DWIN32 -DQT_NO_COMPAT -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_DEBUG -D_DEBUG -DBOOST_SIGNALS_NAMESPACE=boost_signals -DLEDA_PREFIX -DLEDA_STL_ITERATORS -DWIN32 -DNOMINMAX -D_REENTRANT -DBOOST_SIGNALS_STATIC_LINK -DSTD_EXT=stdext -DQT_THREAD_SUPPORT CXXFLAGS= -nologo -GR -GX -wd4100 -Y- -W3 -w34100 -w34189 -MD -Od -Z7 -DUNICODE -DWIN32 -DQT_NO_COMPAT -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_DEBUG -D_DEBUG -DBOOST_SIGNALS_NAMESPACE=boost_signals -DLEDA_PREFIX -DLEDA_STL_ITERATORS -DWIN32 -DNOMINMAX -D_REENTRANT -DBOOST_SIGNALS_STATIC_LINK -DSTD_EXT=stdext -DQT_THREAD_SUPPORT LEXFLAGS= YACCFLAGS =-d INCPATH =-I$(IFCDIR)\include -I$(BOOSTDIR) -I$(LEDADIR)\incl -I$(FLEXLMDIR)\machind -I$(QTDIR)\include -Iuic\\ -Ic:\home\monecke\systems\dispo-irm-1-0-2\src\io -Imoc\win32-msvc.net-debug\\ -Ic:\dev\lib\qt-3.2.3-msvc.net-static\mkspecs\win32-msvc.net LIB = lib /NOLOGO MOC = $(QTDIR)\bin\moc.exe UIC = $(QTDIR)\bin\uic.exe QMAKE = qmake IDC = $(QTDIR)\bin\idc.exe IDL = midl ZIP = zip -r -9 COPY_FILE = copy COPY_DIR= copy DEL_FILE= del DEL_DIR = rmdir MOVE= move CHK_DIR_EXISTS =if not exist MKDIR = mkdir ### Files HEADERS = ..\include\io\csvfile.h \ ..\include\io\infraio.h \ ..\include\io\operatingio.h \ ..\include\io\serviceio.h \ ..\include\io\xmlwriter.h SOURCES = c\csvfile.cpp \ c\infraio.cpp \ c\operatingio.cpp \ c\serviceio.cpp \ c\xmlwriter.cpp OBJECTS = obj\win32-msvc.net-debug\csvfile.obj \ obj\win32-msvc.net-debug\infraio.obj \ obj\win32-msvc.net-debug\operatingio.obj \ obj\win32-msvc.net-debug\serviceio.obj \ obj\win32-msvc.net-debug\xmlwriter.obj FORMS = UICDECLS = UICIMPLS = SRCMOC = OBJMOC = DIST= TARGET = ..\..\bin\win32-msvc.net-debug\dispo-irm-io.lib ### Implicit rules .SUFFIXES: .c .cpp .cc .cxx .C .cpp.obj: $(CXX) -c $(CXXFLAGS) $(INCPATH) -Fo$@ $ .cc.obj: $(CXX) -c $(CXXFLAGS) $(INCPATH) -Fo$@ $ .cxx.obj: $(CXX) -c $(CXXFLAGS) $(INCPATH) -Fo$@ $ .C.obj: $(CXX) -c $(CXXFLAGS) $(INCPATH) -Fo$@ $ .c.obj: $(CC) -c $(CFLAGS) $(INCPATH) -Fo$@ $ ### Build rules all: Makefile $(TARGET) $(TARGET): $(UICDECLS) $(OBJECTS) $(OBJMOC) $(LIB) /OUT:$(TARGET) @ $(OBJECTS) $(OBJMOC) mocables: $(SRCMOC) uicables: $(UICIMPLS) $(UICDECLS) Makefile: io.pro c:\dev\lib\qt-3.2.3-msvc.net-static\mkspecs\win32-msvc.net\qmake.conf ..\include\qmake.include $(QMAKE) -o Makefile io.pro qmake: @$(QMAKE) -o Makefile io.pro dist: $(ZIP) dispo-irm-io.zip $(SOURCES) $(HEADERS) $(DIST) $(FORMS) c:/home/monecke/systems/dispo-irm-1-0-2/src/io/io.pro ..\include\qmake.include uiclean: mocclean: clean: uiclean mocclean
Re: bash v2.05b.0 + nmake v7.10.3077 problem
The attachment you sent has a lot of blank lines in it (at least when I look at it on my Linux box) - is that normal? (i.e. one in two lines is blank). Other than that, I see nothing suspicious in the file.. Could you provide a minimal testcase that reproduces the behaviour? On Thu, Nov 13, 2003 at 01:28:38PM +0100, Lars Monecke wrote: Hello Ronald, here some additional information... Ronald Landheer-Cieslak wrote: * the Makefile (especially line 147 seems to be of interest) Please refer to attachment. But line 147 seems to the end of the file... The Makefile is generated by qmake 1.06c. * a step-by-step description of what you're doing here a the command history: $ qmake $ nmake clean $ nmake The implementation files were compiled but the link command (or before) ^^^ Is it always the same command? If so, which? failed with fatal error U1054. .. and the filename of the file it wants to create is empty? odd.. If i open then a cmd and switch to the directory and type nmake, the lib will be linked. I can reproduce this on another machine. * whether it works when invoking nmake from the Windows command shell My compilation works fine with a normal command shell. I diffed the generated Makefiles (under bash and cmd) and the only difference is the uppercase of the c: drive-letter. Some more enviroments (i can send you see full cygcheck.out by email): Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4 Package Version _update-info-dir 00223-1 base-files 2.6-1 cygwin 1.5.5-1 bash 2.05b-16 I don't know much about nmake, but the only reason I see for it failing under Bash and not under cmd would be a difference in environment.. A minimal test case to reproduce the problem would be nice.. rlc -- Floggings will continue until morale improves. -- anonymous flyer being distributed at Exxon USA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: bash v2.05b.0 + nmake v7.10.3077 problem
On Thu, Nov 13, 2003 at 04:38:17PM +0100, Hannu E K Nevalainen wrote: From: Ronald Landheer-Cieslak Sent: Thursday, November 13, 2003 5:22 PM The attachment you sent has a lot of blank lines in it (at least when I look at it on my Linux box) - is that normal? (i.e. one in two lines is blank). Typical for line endings beeing CRLF - and loading such a file into an editor/viewer that dosn't 'handle' this in a sane manner. i.e. Editor/viewer dependant. That would be right if 1. I didn't use vi 2. I hasn't tried dos2unix on the file rlc -- You have been selected for a secret mission. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: bash v2.05b.0 + nmake v7.10.3077 problem
From: Ronald Landheer-Cieslak Sent: Thursday, November 13, 2003 6:28 PM On Thu, Nov 13, 2003 at 04:38:17PM +0100, Hannu E K Nevalainen wrote: From: Ronald Landheer-Cieslak Sent: Thursday, November 13, 2003 5:22 PM The attachment you sent has a lot of blank lines in it (at least when I look at it on my Linux box) - is that normal? (i.e. one in two lines is blank). Typical for line endings beeing CRLF - and loading such a file into an editor/viewer that dosn't 'handle' this in a sane manner. i.e. Editor/viewer dependant. That would be right if 1. I didn't use vi 2. I hasn't tried dos2unix on the file rlc Not that I see this to be important; 1. I see CRLF line endings. $ od -a Makefile.txt ... 0011340 : sp a l l sp sp cr nl cr nl u n i n s 0011360 t a l l : sp sp cr nl cr nl cr nl 0011375 2. No double linefeeds in 'less' nor in the old Win-GUI editor I use (name: PFE). /Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E -- printf(LocalTime: UTC+%02d\n,(DST)? 2:1); -- --END OF MESSAGE-- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
