[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error

From: Harry Thijssen
Subject: Re: error
Date: Sun, 13 Dec 2020 17:44:24 +0100


Sorry guys

I found it. 
I myself add -o0 to the CFLAGS in my procedure to avoid the start of terminal screen when PSPPIRE is started.  This worked for many years, but not anymore it seems.  I have to look further in this. 

Stay safe

Op zo 13 dec. 2020 om 08:38 schreef Ben Pfaff <>:
I wasn't able to figure anything out by looking at the Makefile (which
was a surprise).

"make -d" and "make -p" print lots of debugging information. You might
be able to figure out
where the funny command comes from using them, or if not, perhaps if
you captured the
output and passed it along we might be able to help.

On Sat, Dec 12, 2020 at 12:07 PM Harry Thijssen <> wrote:
> Hi
> It is on a from scratch fresh installed virtual machine. So nothing available from earlier compilations.  And no traces of earlier installations.
> In fact it is an upgrade from  my procedures, not from an environment.
> I have no clue where it comes from.
> Stay safe
> Op za 12 dec. 2020 om 12:45 schreef John Darrington <>:
>> On Sat, Dec 12, 2020 at 10:24:53AM +0000, Harry Thijssen wrote:
>>      Hi
>>      I am trying to upgrade  my buildproces to openSUSE 15.2.  During build I
>>      get the error:
>>      mv -f $depbase.Tpo $depbase.Plo
>>      libtool: compile:  i686-w64-mingw32-gcc -DHAVE_CONFIG_H -DEXEEXT=\".exe\"
>>      -I. -I.. -I/usr/i686-w64-mingw32/sys-root/mingw/include/cairo
>>      -I/usr/i686-w64-mingw32/sys-root/mingw/include/glib-2.0
>>      -I/usr/i686-w64-mingw32/sys-root/mingw/lib/glib-2.0/include
>>      -I/usr/i686-w64-mingw32/sys-root/mingw/include/pixman-1
>>      -I/usr/i686-w64-mingw32/sys-root/mingw/include
>>      -I/usr/i686-w64-mingw32/sys-root/mingw/include/freetype2
>>      -I/usr/i686-w64-mingw32/sys-root/mingw/include/libpng16
>>      -I/usr/i686-w64-mingw32/sys-root/mingw/include/pango-1.0
>>      -I/usr/i686-w64-mingw32/sys-root/mingw/include/harfbuzz -mms-bitfields
>>      -ggdb -o0 -MT allocator.lo -MD -MP -MF .deps/allocator.Tpo -c allocator.c
>>       -DDLL_EXPORT -DPIC -o .libs/allocator.o
>>      cc1: error: too many filenames given.  Type cc1 --help for usage
>> The argument "-oO" in this command looks suspicious.   Do you know where that came from?
>> Perhaps it was a mistype of -O0 from a previous configuration step.
>> J'

reply via email to

[Prev in Thread] Current Thread [Next in Thread]