error

2020-12-12 Thread Harry Thijssen
--help for usage cc1: fatal error: .libs/allocator.d: No such file or directory compilation terminated. make[3]: *** [Makefile:3047: allocator.lo] Error 1 make[3]: Leaving directory '/home/pspp/pspp-master-20201212/pspp-1.5.2-ga06dd5/gl' This error is not generated on my openSUSE 15.0 buildpr

warning

2020-12-12 Thread Harry Thijssen
Hi When configuring I get the warning: configure: WARNING: The following optional packages are not installed. You may wish to install them to obtain additional functionality: org.fsf.metainfo.xml will not be translated. Install gettext >=0.20 or appstream. librsvg >= 2.44 required for high

Re: error

2020-12-12 Thread Ben Pfaff
s given. Type cc1 --help for usage > cc1: fatal error: .libs/allocator.d: No such file or directory > compilation terminated. > make[3]: *** [Makefile:3047: allocator.lo] Error 1 > make[3]: Leaving directory > '/home/pspp/pspp-master-20201212/pspp-1.5.2-ga06dd5/gl' > > This error is not generated on my openSUSE 15.0 buildproces. Any clues what > this can be? > > Stay safe >

Re: warning

2020-12-12 Thread Ben Pfaff
The former doesn't seem important to me either. For the latter, I'm surprised that installing librsvg is not the solution. I would expect it to be. It might not be worth spending time on, though, because I'm working on a series of patches that, as a side effect, drops the dependency on librsvg. O

Re: error

2020-12-12 Thread John Darrington
So you have : COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) which suggest that this rogue string is coming from one of the variables $(AM_CPPFLAGS) (CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) Try printing the values of those a

Re: error

2020-12-12 Thread John Darrington
On Sat, Dec 12, 2020 at 02:27:08PM +0100, 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

Re: error

2020-12-12 Thread John Darrington
On Sat, Dec 12, 2020 at 10:24:53AM +, 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\"

Re: error

2020-12-12 Thread John Darrington
On Sat, Dec 12, 2020 at 05:17:49PM +, Harry Thijssen wrote: It seems this is beyond my skills. How can I print them? I don't see them with "printenv" You could, for example add a rule to print these values. Something similar to show_cppflags: echo $(CPPFLAGS) There a

Re: error

2020-12-12 Thread Harry Thijssen
It seems this is beyond my skills. How can I print them? I don't see them with "printenv" Stay save Op za 12 dec. 2020 om 15:54 schreef John Darrington < j...@darrington.wattle.id.au>: > So you have : > > COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \ > $(CPPFL

Re: warning

2020-12-12 Thread Harry Thijssen
Hi I found that the version installed is from the opensuse libraries is 2.36. Which is indeed lower as 2.44. So that is correct. Stay safe Op za 12 dec. 2020 om 18:27 schreef Ben Pfaff : > The former doesn't seem important to me either. > > For the latter, I'm surprised that installing librsv

Re: error

2020-12-12 Thread Harry Thijssen
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

Re: warning

2020-12-12 Thread Friedrich Beckmann
Hi Harry, i think you can ignore both. I figured out that Copy and Paste will work with higher dpi when librsvg above 2.44 is used. Not that important. Fritz > Am 12.12.2020 um 11:28 schrieb Harry Thijssen : > > Hi > > When configuring I get the warning: > > configure: WARNING: The following

Re: error

2020-12-12 Thread 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 m