Re: [Gm2] gm2 cannot detect itself

[Gaius Mulley]

Martin Kalbfuss <address@hidden> writes:

> Hi,
>
> I’m working on a autoconf macro to detect gm2. The detection runs fine
> and returns the complete path to gm2. In my case it is /opt/gm2/bin/gm2.
> This works, even if it isn’t in PATH, bacaue it checks the two standard
> locations in /opt/gm2 and $HOME/opt. So let's compile? No. It isn’t
> working. Using the complete path to gm2 like
>
>  address@hidden:~/Desktop/sk/schwarzerkaffee/examples
> $ /opt/gm2/bin/gm2 -fmakeall  -o timer_callback timer_callback.mod
> -I../include/SK -l:../src/libsk.a -L/usr/lib -lSDL
>
> results in
>
> gm2 -c -fmakeall0 -ftarget-ranlib=/usr/bin/ranlib
> -ftarget-ar=/usr/bin/ar
> -fobject-path=../include/SK:/opt/gm2/lib/gcc/x86_64-linux-gnu/4.1.2/gm2/pim:/opt/gm2/lib/gcc/x86_64-linux-gnu/4.1.2/gm2/logitech
>  -fmakeall 
> -I../include/SK:/opt/gm2/lib/gcc/x86_64-linux-gnu/4.1.2/gm2/pim:/opt/gm2/lib/gcc/x86_64-linux-gnu/4.1.2/gm2/logitech
>  timer_callback.mod
> make: gm2: Command not found
> make: *** [timer_callback.o] Error 127
>
> gm2 cannot detect itself. I asume, it's the created makefile which uses
> gm2 only instead of the complete path.
>
> Martin

Hi Martin,

thanks for the bug report - now under investigation - I presume the
correct behaviour, in this case, is for the -fmakeall to use argv[0] of
gm2.  However if another gm2 is found along the PATH then which one
should take precedence?

regards,
Gaius