Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#345 w32api-2.3 build from source fails

OTHER
closed
Earnie Boyd
make (27)
wont-fix
Known_bugs
2013-01-22
2003-05-06
James E. Lucas
No

I'm using cygwin bash 2.05b-9 and minGW make 3.79.1

output follows:

gcc -c -O2 -g -I./../include -o largeint.o largeint.c
ar rc liblargeint.a largeint.o
ranlib liblargeint.a
c:/mingw2/bin/make.exe AS="as" CC="gcc"
CPPFLAGS="" CFLAGS="-O2 -g" CXXFLAGS=""
AR="ar" RANLIB="ranlib" LD="ld" DLLTOOL="dlltool"
TAR="tar" TARFLAGS="j" TARFILE
EXT=".tar.bz2" WINDRES="windres" -C ddk
c:\mingw2\bin\make.exe: invalid option -- g
c:\mingw2\bin\make.exe: invalid option --
Usage: c:\mingw2\bin\make.exe [options] [target] ...

***
list of make's options
***

Report bugs to <bug-make@gnu.org>.
c:\mingw2\bin\make.exe[1]: *** [ddk] Error 2
c:\mingw2\bin\make.exe[1]: Leaving directory
`C:/programs/power/mingw/w32api-2.3
/lib'
make: *** [lib] Error 2

-----------------------------------------------------

Version 2.1 compiled fine (and still does). Haven't tried
2.2. I diffed the Makefiles and there haven't been
substantial changes, so I'm scratching my head. I
*looks* like it's getting confused by the "-O2 -g" in the
CFLAGS variable, but I'm not really sure why. Any
takers?

Discussion

  • Luke Dunstan
    Luke Dunstan
    2003-05-07

    Logged In: YES
    user_id=30442

    If you are using Cygwin bash then you should always use
    Cygwin "make" instead of MinGW "make". I think it is a bug
    in MinGW make with handling the CPPFLAGS="" argument,
    but my guess is that it only occurs when you are using
    sh.exe as the shell (instead of command.com/cmd.exe). This
    is the reason why MSYS requires you to use MSYS "make"
    instead of the MinGW one. I haven't looked at this bug myself
    but it is so old that I assume that nobody thinks it is worth
    fixing. Perhaps you could ask on the "make" mailing list if it
    matters to you?

     
  • Luke Dunstan
    Luke Dunstan
    2003-05-07

    • labels: 103945 --> MinGW
    • milestone: --> Known_bugs
    • priority: 5 --> 1
    • status: open --> open-wont-fix
     
  • James E. Lucas
    James E. Lucas
    2003-05-07

    Logged In: YES
    user_id=666734

    Well, to my mind even old bugs ought to be worth fixing. I
    appreciate the info, however. I had pretty much gathered that
    it had to do with differences in how the shells were
    interacting. Nevertheless, since 2.1 compiled okay...

    It seems rather a detriment to MinGWs overall usability to
    have these kinds of discrepancies pop up. I would ask that
    you reconsider and take a look at it. In any event, I intend to
    try my own hand at it when I get a chance, so I appreciate
    you pointing me in the right direction.

     
  • Earnie Boyd
    Earnie Boyd
    2003-05-08

    Logged In: YES
    user_id=15438

    I don't see this as our problem. Your environment is
    preventing you from building. Instead of the Win32 version
    of make you should use the Cygwin version of make.

    Earnie.

     
  • Earnie Boyd
    Earnie Boyd
    2003-05-08

    • status: open-wont-fix --> closed-wont-fix
     
  • Earnie Boyd
    Earnie Boyd
    2013-01-22

    • labels: MinGW --> make
    • status: closed-wont-fix --> closed
    • resolution: --> wont-fix
    • category: --> Known_bugs
    • milestone: Known_bugs --> OTHER