Allegro.cc - Online Community

Allegro.cc Forums » Allegro Development » Allegro 4.2.1 compiler test

This thread is locked; no one can reply to it. rss feed Print
 1   2   3 
Allegro 4.2.1 compiler test
Milan Mimica
Member #3,877
September 2003
avatar
Posted on 10/02/2006 4:44 PM   View Profile

I tried to fix it but makefile concept it too repulsive for me. No success.

--
M.M.
http://sparklet.sf.net

ReyBrujo
Moderator
January 2001
avatar
Posted on 10/02/2006 4:49 PM   View Profile

What is in that line?

--
RB
光子「あたしただ…奪う側に回ろうと思っただけよ」
Mitsuko's last words, Battle Royale

Milan Mimica
Member #3,877
September 2003
avatar
Posted on 10/02/2006 5:12 PM   View Profile
1ifdef UNIX_TOOLS
2 
3$(WINDIR_U)/$(DLL_BASENAME): $(DLL_NAME)
4 cp lib/msvc/$(DLL_BASENAME) $(WINDIR_U)
5 
6$(MSVCDIR_U)/lib/$(IMPLIB_BASENAME): $(IMPLIB_NAME) $(MSVCDIR_U)/lib
7 cp lib/msvc/$(IMPLIB_BASENAME) $(MSVCDIR_U)/lib
8 
9else
10 
11$(WINDIR_U)/$(DLL_BASENAME): $(DLL_NAME)
12 copy lib\msvc\$(DLL_BASENAME) $(WINDIR_D)
13 
14$(MSVCDIR_U)/lib/$(IMPLIB_BASENAME): $(IMPLIB_NAME) $(MSVCDIR_U)/lib
15 copy lib\msvc\$(IMPLIB_BASENAME) $(MSVCDIR_D)\lib
16 
17endif

It complains about lines starting with $(WINDIR_U) and $(MSVCDIR_U).

--
M.M.
http://sparklet.sf.net

ReyBrujo
Moderator
January 2001
avatar
Posted on 10/02/2006 8:39 PM   View Profile

The variables are empty then. I have seen that happen when MINGDIR is not defined. Apparently the makefile is detecting you have unix tools, thus using WINDIR_U instead of WINDIR_D, which is wrong. Do you have sh.exe in your path?

--
RB
光子「あたしただ…奪う側に回ろうと思っただけよ」
Mitsuko's last words, Battle Royale

Evert
Member #794
November 2000
avatar
Posted on 10/03/2006 2:04 AM   View Profile
Quote:

I have seen that happen when MINGDIR is not defined.

Shouldn't it abort with a warning or error in that case? Or is that just for the MinGW port?

Milan Mimica
Member #3,877
September 2003
avatar
Posted on 10/03/2006 2:18 AM   View Profile

That's not the case. UNIX_TOOLS is actually not defined. None of the variables seems to be empty. I even tried to replace variables with values they are supposed to contain and the same error appeared. And as I said, with make-3.80 works fine.

--
M.M.
http://sparklet.sf.net

Evert
Member #794
November 2000
avatar
Posted on 10/03/2006 3:33 AM   View Profile

Ok, so the question is: is this a problem with Allegro's Makefile, or is it a bug in the newer version of make? It starts to sound like the latter, to be honest...

Does the same problem show up with GNU make 3.81 on other platforms, or just with the MinGW version?

Milan Mimica
Member #3,877
September 2003
avatar
Posted on 10/03/2006 6:27 AM   View Profile

I'm using cygwin's make. It fails with the same error on makefile.vc and makefile.mgw.

Yep, it seems to be the problem with the cygwin port of make.
http://lists.gnu.org/archive/html/bug-make/2006-07/msg00018.html
I'll see if I can work around it.

--
M.M.
http://sparklet.sf.net

Evert
Member #794
November 2000
avatar
Posted on 10/03/2006 8:19 AM   View Profile

Ok, in that case I say we document that Cygwin's make 3.81 is broken and tell people to complain to them about it.
I honestly don't want to try dodgy workarounds that may break other platforms.

Milan Mimica
Member #3,877
September 2003
avatar
Posted on 10/03/2006 9:16 AM   View Profile

I agree. I couldn't find a easy way around it. It is still possible that the issue will be fixed in a patched release versioned like 3.81-2 or something... And I'm quite sure it will be fixed in the next release because I saw some patches in make CVS that enable DOS path support in cygwin build of make.

--
M.M.
http://sparklet.sf.net

 1   2   3 


Go to: