>> So my next question is: Do you know what parameters are needed so that
>> the
>> Makefile will be created with the right settings (without manually
>> executing g++ after the crashed first make)?
>>
>> Because creating it with:
>> perl Makefile.PL LIBS=-L/usr/lib/e2fsprogs
>
> I would have tried
Alexander Stadler wrote:
> So my next question is: Do you know what parameters are needed so that the
> Makefile will be created with the right settings (without manually
> executing g++ after the crashed first make)?
>
> Because creating it with:
> perl Makefile.PL LIBS=-L/usr/lib/e2fsprogs
I w
>> gcc -c -DPERL_USE_SAFE_PUTENV -U__STRICT_ANSI__ -fno-strict-aliasing
>> -pipe -I/
>> usr/local/include -DUSEIMPORTLIB -O3 -DVERSION=\"0.02\"
>> -DXS_VERSION=\"0.02\"
>> "-I/usr/lib/perl5/5.10/i686-cygwin/CORE" UUID.c
>> rm -f blib/arch/auto/UUID/UUID.dll
>> g++ --shared -Wl,--enable-aut
Alexander Stadler wrote:
> gcc -c -DPERL_USE_SAFE_PUTENV -U__STRICT_ANSI__ -fno-strict-aliasing
> -pipe -I/
> usr/local/include -DUSEIMPORTLIB -O3 -DVERSION=\"0.02\"
> -DXS_VERSION=\"0.02\"
> "-I/usr/lib/perl5/5.10/i686-cygwin/CORE" UUID.c
> rm -f blib/arch/auto/UUID/UUID.dll
> g++ --share
4 matches
Mail list logo