From: Borut R. <bor...@si...> - 2003-03-12 21:45:17
|
> I'm at a win98SE machine with cygwin and mingw32-sdcc, if I use my > Makefile and try to compile, it gets stuck like this and nothing more happens: > --- > C:\Magnus_J\MP\first>make > sdcc -c -V -I c:/sdcc/share/sdcc/include -L c:/sdcc/share/sdcc/lib/small uart.c > + c:\SDCC\BIN\sdcpp -nostdinc -Wall -std=3Dc99 -DSDCC=3D1 -Ic:/sdcc/share/sdcc/include -DSDCC_MODEL_SMALL -DSDCC_mcs51 -D__mcs51 -Ic:\SDCC\share\sdcc\include uart.c This might be connected with changes I made: piping preprocessor output (dates match :-(. Magnus: which version of Makefile are you using? What is the output of make --version? What is the version of Cygwin? Do you run make from a shell or from command prompt? Can you send the stripped version of your Makefile, which reproduce the problem? Have you tried also on others Windows platforms (WinNT, Win2000 or WinXP)? Is behavior the same? > Any good reason to use mingw on cygwin?????????????? The same reason as to use MSVC or BORLANDC: MINGW produces WIN32 native code, which doesn't depend on cygwin stuff, mainly cygwin.dll. As somebody recently wrote, there are also some licensing problems connected with cygwin... Michael: Jesus probably already told you that we already have SDCC ports for MSVC and BORLANDC, which doesn't depend on cygwin and ./configure. this is also documented in sdccman documentation. You can find MSVC project files and BORLANDC makefiles (Makefile.bcc) delivered with sdcc sources. Borut |
From: Borut R. <bor...@si...> - 2003-03-13 19:13:26
|
> However, I did try and build a cygwin-sdcc overnight (source code from = > 20030312) and nothing wrong happens when using cygwin-sdcc and = > cygwin-make in a cygwin-bash-shell, it compiles nicely. > > Using the snapshot-msvc-mingw32-sdcc and cygwin-make in a = > cygwin-bash-shell however reproduces the same neverending stall as from = > a DOS/command prompt. Hmmm, very interesting. So if I understand the situation, everything works on WIN32 if compiled with cygwin gcc, MSVC or BORLANDC, but it fails with MINGW gcc. It sounds to me to be a MINGW library problem (I wouldn't even dare to doubt on gcc code generation ;-). It has definitely something to do with Win98SE, as Bernhard said that everything is OK on Win2000. Did you try to build a MINGW executable on cygwin using -mno-cygwin? It would be interesting to see if the MINGW build on Linux is the same as MINGW build on Cygwin... (an other answer to Johan's question :-) Currently I don't have time to investigate the problem by my self, maybe during the week-end... So any help from other guys is valuable. Borut |
From: Borut R. <bor...@si...> - 2003-03-16 08:35:13
|
Hi, I finally found some time and tried to reproduce a problem on Win98 (I don't have Win98SE), but I couldn't: everything works OK. I tried it with the snapshot sdcc_snapshots\sdcc-snapshot-i586-mingw32msvc-20030315.zip I run make from DOS prompt. I use the same version of make as you do: GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i686-pc-cygwin Following are test files, which I used. Can you try once again with them? --- Makefile ------------- SDCC=d:/sdcc/bin/sdcc SDCCFLAGS=-V %.rel : %.c %.h $(SDCC) -c $(SDCCFLAGS) $< all: main.ihx main.ihx: main.c $(SDCC) -V --model-small\ main.c cp main.ihx MP.hex clean: rm -f *.lst *.rel *.sym *.rst *.adb *.map *.asm *.lnk *.mem *.cdb -------------------------- --- main.c --------------- int main(void) { return 1; } -------------------------- The output from make is: d:/sdcc/bin/sdcc -V --model-small\ main.c + d:\sdcc\bin\sdcpp -nostdinc -Wall -std=c99 -DSDCC=1 -DSDCC_MODEL_SMALL -DSDC C_mcs51 -D__mcs51 -Id:\sdcc\share\sdcc\include main.c + d:\sdcc\bin\asx8051.exe -plosgff main.asm + d:\sdcc\bin\aslink.exe -nf main cp main.ihx MP.hex If the problem still exist, I'm afraid that I can't help you much any more: I don't have Win98SE, to try on them. The problem can also be in system or cygwin settings... But your are more or less on your own now :-( Borut |
From: Bernhard H. <Ber...@be...> - 2003-03-16 08:56:56
|
> I finally found some time and tried to reproduce a problem > on Win98 (I don't have Win98SE), but I couldn't: > everything works OK. Just in time ;-) I was just going to set up the test on Win98 too (even if I didn't expect to find anything). Thanks, Bernhard |
From: Magnus J. <rnd...@rn...> - 2003-03-17 08:33:40
|
> Following are test files, which I used. Can you try once again with > them?=20 Using those as they are with the msvc-mingw32 snapshot dated 20030315, I = get: Makefile:5: *** missing separator. Stop. and adding tabs gets me this: $ make c:/sdcc/bin/sdcc -V --model-small\ main.c + c:\sdcc\bin\sdcpp -nostdinc -Wall -std=3Dc99 -DSDCC=3D1 = -DSDCC_MODEL_SMALL -DSDCC_mcs51 -D__mcs51 -Ic:\sdcc\share\sdcc\include = main.c and nothing more... =3D7 > If the problem still exist, I'm afraid that I can't help you much any > more: I don't have Win98SE, to try on them. The problem can also be > in system or cygwin settings... >=20 > But your are more or less on your own now :-( Great! ;-)=20 |
From: Magnus J. <rnd...@rn...> - 2003-03-17 18:09:18
|
>> If the problem still exist, I'm afraid that I can't help you much any >> more: I don't have Win98SE, to try on them. The problem can also be >> in system or cygwin settings... Ehm, ehm, I'm still a bit dumbstruck. As you wrote system settings I had a look at things and I actually found an exclamation point on the soundcard. It was working in Windows so I hadn't noticed. So, I reinstalled the drivers and guess what, now I can even use the latest version. So, on the count of three, you can all start throwing the rotten eggs and vegetables in my general direction and if there should be any left you can aim those towards Redmond. 1-2-3! |
From: Bernhard H. <bh...@mg...> - 2003-03-18 15:27:15
|
Just received an update info for cygwin 1.3.22-1: > Changes since 1.3.21-1 (worst cygwin release ever): > > - Fix problem which stopped cygwin from running on Windows 9x. > (Corinna Vinschen) Bernhard |
From: Borut R. <bor...@si...> - 2003-03-16 06:58:41
|
> I'm not sure, but the snapshots at sourceforge are > named sdcc-snapshot-i586-mingw32msvc so I'm guessing > what fails on this win98SE machine are sdcc-binaries > compiled with msvc using mingw32 libraries. Don't know > about Borland or gcc with mingw. Wrong. Snapshots are compiled on Linux box using gcc cross compiler to generate the WIN32 native code (MINGW), and linked with MINGW library, which at the end calls msvcrt.dll (C run-time dll). And this is why msvc is a part of the name. (Bernhard, correct me if I'm wrong). In fact, there are two versions of C run-time dlls on WIN32 machines: - CRTDLL.DLL: this one is deprecated and is the only one available on Win95. - MSVCRT.DLL: this was introduced with Win95 Service Pack (Or however it was called, I also don't know tah number), and is newer and recommended to use. CRTDLL.DLL is still available only for backward compatibility. So SDCC can't run on genuine Win95 machines (if everything I wrote is true ;-) But this has nothing to do wit your problem with win98SE machine. As I already wrote, I suspect that this might be a caused by MINGW library. I know that MINGW library, which comes with CygWin, was updated in last few month. Bernhard: which version of MNIGW library is used on Linux build machine? Can it be upgraded to the latest one, to see, if the problem still exist? P.S.: Magnus, you sent the mail to my private address, so I'm redirecting it back to sdcc-user mailing list. Borut -----Original Message----- From: Magnus Johansson [mailto:rnd...@rn...] Sent: Friday, March 14, 2003 9:03 AM To: bor...@si... Subject: Re: [Sdcc-user] Newest versions and Makefiles on win > Hmmm, very interesting. So if I understand the situation, everything > works on WIN32 > if compiled with cygwin gcc, MSVC or BORLANDC, but it fails with > MINGW gcc. It sounds to me to be a MINGW library problem (I wouldn't > even dare to doubt on > gcc code generation ;-). It has definitely something to do with > Win98SE, as Bernhard > said that everything is OK on Win2000. I'm not sure, but the snapshots at sourceforge are named sdcc-snapshot-i586-mingw32msvc so I'm guessing what fails on this win98SE machine are sdcc-binaries compiled with msvc using mingw32 libraries. Don't know about Borland or gcc with mingw. I'll have the computer compile a -mno-cygwin version during the day, but I don't know if it's going to be quick enough for me to reply to you before the weekend starts. |
From: Bernhard H. <Ber...@be...> - 2003-03-16 08:19:05
|
> As I already wrote, I suspect that this might be a caused > by MINGW library. I know that MINGW library, which comes with > CygWin, was updated in last few month. > > Bernhard: which version of MNIGW library is used on Linux build > machine? Can it be upgraded to the latest one, to see, if the > problem still exist? Unfortunately I had to install the mingw32 environment on the CF myself. Therefore we're fortunately building with the latest stable releases: http://sourceforge.net/project/showfiles.php?group_id=2435 binutils-2.13.90-20021006-2-src.tar.gz gcc-3.2-20020817-1.src.tar.gz mingw-runtime-2.4.tar.gz w32api-2.2.tar.gz Bernhard |
From: Magnus J. <rnd...@rn...> - 2003-03-13 09:44:16
Attachments:
Makefile.zip
|
> Magnus: which version of Makefile are you using? What is the output of > make --version? I don't think I can answer the first question, the answer to the second = is: --- GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for i686-pc-cygwin --- > What is the version of Cygwin? Do you run make from a shell or from > command prompt? From cygwin's setup: Cygwin 1.3.20-1, make 3.79.1-7, bash 2.05b-8 (I'll = come to this later). I run it from a DOS/command prompt. > Can you send the stripped version of your Makefile, which reproduce > the problem? Not much to strip, I'm attaching it. > Have you tried also on others Windows platforms (WinNT, Win2000 or > WinXP)? Is behavior the same? No, just win98SE. However, I did try and build a cygwin-sdcc overnight (source code from = 20030312) and nothing wrong happens when using cygwin-sdcc and = cygwin-make in a cygwin-bash-shell, it compiles nicely. Using the snapshot-msvc-mingw32-sdcc and cygwin-make in a = cygwin-bash-shell however reproduces the same neverending stall as from = a DOS/command prompt. And another try with snapshot-msvc-mingw32-sdcc and unxutils-make from a = DOS/command prompt gives the neverending stall.=20 Make-version of unxutils-make: --- GNU Make version 3.78.1, by Richard Stallman and Roland McGrath. Built for Windows32 --- And as the source code from 20030312 worked when compiling under cygwin = I today downloaded the msvc-mingw32-snapshot dated 20030312, and it also = gets me the same stall. |
From: Bernhard H. <Ber...@be...> - 2003-03-13 12:28:18
|
> Using the snapshot-msvc-mingw32-sdcc and cygwin-make in a cygwin-bash-shell > however reproduces the same neverending stall as from a DOS/command prompt. No comment. > And another try with snapshot-msvc-mingw32-sdcc and unxutils-make from a > DOS/command prompt gives the neverending stall. This should work. I decided to download everything needed to copy your setup -- and it works for me. Then I tried it from the cygwin-bash: works for me. With exactly the same versions, but todays (13) snapshot and Win2000. Bernhard |