Re: [Slackbuilds-users] fontforge

2020-10-21 Thread Jim Diamond via SlackBuilds-users 
On Wed, Oct 21, 2020 at 18:47 (+0100), Dave Woodfall wrote:

> On 21/10/20 13:33,
> B Watson  put forth the proposition:
>> On 10/21/20, Matteo Bernardini  wrote:

>>> I was about to test it, but before trying I just want to be sure that
>>> you have noted this bit in fontforge's README

>>> "NOTE: please remove previous version before building new version."
>> I know from experience that trying to build a new fontforge without
>> following this advice causes a build failure.
>> A question for the maintainer: Why doesn't the SlackBuild check for
>> this and abort or at least warn the user? It could be done with very
>> little code, and would have saved however much time we've collectively
>> spent thinking and writing about it, in this thread.

> I'll add that this week.  I do something similar in Qt5 already.

On behalf of all of us "don't read the instructions if all else has
not failed, and maybe not even then" people, thanks.

Jim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge

2020-10-21 Thread Dave Woodfall 
On 21/10/20 18:47,
Dave Woodfall  put forth the proposition:
> On 21/10/20 13:33,
> B Watson  put forth the proposition:
> > On 10/21/20, Matteo Bernardini  wrote:
> > >
> > > I was about to test it, but before trying I just want to be sure that
> > > you have noted this bit in fontforge's README
> > >
> > > "NOTE: please remove previous version before building new version."
> > I know from experience that trying to build a new fontforge without
> > following this advice causes a build failure.
> > A question for the maintainer: Why doesn't the SlackBuild check for
> > this and abort or at least warn the user? It could be done with very
> > little code, and would have saved however much time we've collectively
> > spent thinking and writing about it, in this thread.
> I'll add that this week.  I do something similar in Qt5 already.
> --
> Dave
> Love is a snowmobile racing across the tundra and then suddenly it flips over,
> pinning you underneath.  At night, the ice weasels come.
>--Friedrich Nietzsche

By the way, this usually only happens after a significant update.
Minor changes don't seem to trigger this.

--
Dave

Love is a snowmobile racing across the tundra and then suddenly it flips over,
pinning you underneath.  At night, the ice weasels come.
 --Friedrich Nietzsche


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge

2020-10-21 Thread Dave Woodfall 
On 21/10/20 13:33,
B Watson  put forth the proposition:
> On 10/21/20, Matteo Bernardini  wrote:
> >
> > I was about to test it, but before trying I just want to be sure that
> > you have noted this bit in fontforge's README
> >
> > "NOTE: please remove previous version before building new version."
> I know from experience that trying to build a new fontforge without
> following this advice causes a build failure.
> A question for the maintainer: Why doesn't the SlackBuild check for
> this and abort or at least warn the user? It could be done with very
> little code, and would have saved however much time we've collectively
> spent thinking and writing about it, in this thread.

I'll add that this week.  I do something similar in Qt5 already.

--
Dave

Love is a snowmobile racing across the tundra and then suddenly it flips over,
pinning you underneath.  At night, the ice weasels come.
 --Friedrich Nietzsche


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge

2020-10-21 Thread B Watson 
On 10/21/20, Matteo Bernardini  wrote:
>
> I was about to test it, but before trying I just want to be sure that
> you have noted this bit in fontforge's README
>
> "NOTE: please remove previous version before building new version."

I know from experience that trying to build a new fontforge without
following this advice causes a build failure.

A question for the maintainer: Why doesn't the SlackBuild check for
this and abort or at least warn the user? It could be done with very
little code, and would have saved however much time we've collectively
spent thinking and writing about it, in this thread.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge

2020-10-21 Thread Jim Diamond via SlackBuilds-users 
On Wed, Oct 21, 2020 at 18:00 (+0200), Matteo Bernardini wrote:

> Il giorno mer 21 ott 2020 alle ore 17:54 Jim Diamond via
> SlackBuilds-users  ha scritto:

>> When I try to compile the most recent update to fontforge on S64-14.2,
>> I get



>> Makefile:1085: recipe for target 'install' failed
>> Failures:
>> fontforge: fontforge.SlackBuild return non-zero


>> Can anyone provide any insight on this?  Or even a report that it
>> successfully compiled for you on S64 14.2?

> I was about to test it, but before trying I just want to be sure
> that you have noted this bit in fontforge's README

> "NOTE: please remove previous version before building new version."

README?  No speak English.
:-(


My bad.  No, I didn't read it.  And yes, it compiled nicely after
removing the previous version.  Thanks for the quick reply.  I have
been lulled into a false sense of security because "sbocheck ;
sboupdate ..." has been so automatic.  The fact it works so well is, I
guess, both a good thing and a bad thing.

Also thanks to Tim Dickson for getting back.

Jim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge

2020-10-21 Thread Tim Dickson via SlackBuilds-users 

it compiled just fine on my 64bit slackware 14.2
Tim

On 21/10/2020 16:54, Jim Diamond via SlackBuilds-users wrote:

When I try to compile the most recent update to fontforge on S64-14.2,
I get


libtool: install: (cd /tmp/SBo/package-fontforge/usr/lib64 && { ln -s -f 
libgunicode.so.5.0.0 libgunicode.so.5 || { rm -f libgunicode.so.5 && ln -s 
libgunicode.so.5.0.0 libgunicode.so.5; }; })
libtool: install: (cd /tmp/SBo/package-fontforge/usr/lib64 && { ln -s -f 
libgunicode.so.5.0.0 libgunicode.so || { rm -f libgunicode.so && ln -s 
libgunicode.so.5.0.0 libgunicode.so; }; })
libtool: install: /usr/bin/ginstall -c .libs/libgunicode.lai 
/tmp/SBo/package-fontforge/usr/lib64/libgunicode.la
libtool: warning: remember to run 'libtool --finish /usr/lib64'
make[3]: Leaving directory '/tmp/SBo/fontforge-20190801/Unicode'
make[2]: Leaving directory '/tmp/SBo/fontforge-20190801/Unicode'
Making install in gutils
make[2]: Entering directory '/tmp/SBo/fontforge-20190801/gutils'
make[3]: Entering directory '/tmp/SBo/fontforge-20190801/gutils'
make[3]: Nothing to be done for 'install-data-am'.
  /usr/bin/mkdir -p '/tmp/SBo/package-fontforge/usr/lib64'
  /bin/sh ../libtool   --mode=install /usr/bin/ginstall -c   libgutils.la 
'/tmp/SBo/package-fontforge/usr/lib64'
libtool: warning: relinking 'libgutils.la'
libtool: install: (cd /tmp/SBo/fontforge-20190801/gutils; /bin/sh 
"/tmp/SBo/fontforge-20190801/libtool"  --silent --tag CC --mode=relink gcc -O2 
-fPIC -Wl,--no-undefined -Werror=implicit-function-declaration -Werror=int-conversion 
-I/tmp/SBo/freetype-2.10.0/src/truetype -I/tmp/SBo/freetype-2.10.0/include 
-I/tmp/SBo/freetype-2.10.0/include/freetype -pthread -I/usr/include/glib-2.0 
-I/usr/lib64/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 
-I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-I/usr/include/libdrm -I/usr/include/libpng16 -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib

-2

  .0/include -I/usr/include/libxml2 -I/usr/include/python2.7 -pthread 
-version-info 3:1:0 -no-undefined -o libgutils.la -rpath /usr/lib64 
libgutils_la-dlist.lo libgutils_la-fsys.lo libgutils_la-g_giomime.lo 
libgutils_la-gcol.lo libgutils_la-gimage.lo libgutils_la-gimageread.lo 
libgutils_la-gimagereadbmp.lo libgutils_la-gimagereadgif.lo 
libgutils_la-gimagereadjpeg.lo libgutils_la-gimagereadpng.lo 
libgutils_la-gimagereadras.lo libgutils_la-gimagereadrgb.lo 
libgutils_la-gimagereadtiff.lo libgutils_la-gimagereadxbm.lo 
libgutils_la-gimagereadxpm.lo libgutils_la-gimagewritebmp.lo 
libgutils_la-gimagewritegimage.lo libgutils_la-gimagewritejpeg.lo 
libgutils_la-gimagewritepng.lo libgutils_la-gimagewritexbm.lo 
libgutils_la-gimagewritexpm.lo libgutils_la-gio.lo libgutils_la-giofile.lo 
libgutils_la-giotrans.lo libgutils_la-gutils.lo libgutils_la-gwwintl.lo 
libgutils_la-prefs.lo libgutils_la-unicodelibinfo.lo -lgif -ljpeg -lpng -ltiff 
-lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lcairo

 -l

  pangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig 
-lfreetype -lXft -lSM -lICE -lreadline -ltermcap -lfreetype -lz -lgio-2.0 
-lgobject-2.0 -lglib-2.0 -lxml2 ../Unicode/libgunicode.la -lX11 -lm 
-inst-prefix-dir /tmp/SBo/package-fontforge)
.libs/libgutils_la-fsys.o: In function `getFontForgeUserDir':
fsys.c:(.text+0x1775): undefined reference to `smprintf'
fsys.c:(.text+0x17c5): undefined reference to `smprintf'
collect2: error: ld returned 1 exit status
libtool:   error: error: relink 'libgutils.la' with the above command before 
installing it
make[3]: *** [install-libLTLIBRARIES] Error 1
Makefile:559: recipe for target 'install-libLTLIBRARIES' failed
make[3]: Leaving directory '/tmp/SBo/fontforge-20190801/gutils'
make[2]: *** [install-am] Error 2
Makefile:952: recipe for target 'install-am' failed
make[2]: Leaving directory '/tmp/SBo/fontforge-20190801/gutils'
make[1]: *** [install-recursive] Error 1
Makefile:788: recipe for target 'install-recursive' failed
make[1]: Leaving directory '/tmp/SBo/fontforge-20190801'
make: *** [install] Error 2
Makefile:1085: recipe for target 'install' failed
Failures:
   fontforge: fontforge.SlackBuild return non-zero


Can anyone provide any insight on this?  Or even a report that it
successfully compiled for you on S64 14.2?

Thanks.

 Jim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/





--
This

Re: [Slackbuilds-users] fontforge

2020-10-21 Thread Matteo Bernardini 
Il giorno mer 21 ott 2020 alle ore 17:54 Jim Diamond via
SlackBuilds-users  ha scritto:
>
> When I try to compile the most recent update to fontforge on S64-14.2,
> I get
>
> 
> libtool: install: (cd /tmp/SBo/package-fontforge/usr/lib64 && { ln -s -f 
> libgunicode.so.5.0.0 libgunicode.so.5 || { rm -f libgunicode.so.5 && ln -s 
> libgunicode.so.5.0.0 libgunicode.so.5; }; })
> libtool: install: (cd /tmp/SBo/package-fontforge/usr/lib64 && { ln -s -f 
> libgunicode.so.5.0.0 libgunicode.so || { rm -f libgunicode.so && ln -s 
> libgunicode.so.5.0.0 libgunicode.so; }; })
> libtool: install: /usr/bin/ginstall -c .libs/libgunicode.lai 
> /tmp/SBo/package-fontforge/usr/lib64/libgunicode.la
> libtool: warning: remember to run 'libtool --finish /usr/lib64'
> make[3]: Leaving directory '/tmp/SBo/fontforge-20190801/Unicode'
> make[2]: Leaving directory '/tmp/SBo/fontforge-20190801/Unicode'
> Making install in gutils
> make[2]: Entering directory '/tmp/SBo/fontforge-20190801/gutils'
> make[3]: Entering directory '/tmp/SBo/fontforge-20190801/gutils'
> make[3]: Nothing to be done for 'install-data-am'.
>  /usr/bin/mkdir -p '/tmp/SBo/package-fontforge/usr/lib64'
>  /bin/sh ../libtool   --mode=install /usr/bin/ginstall -c   libgutils.la 
> '/tmp/SBo/package-fontforge/usr/lib64'
> libtool: warning: relinking 'libgutils.la'
> libtool: install: (cd /tmp/SBo/fontforge-20190801/gutils; /bin/sh 
> "/tmp/SBo/fontforge-20190801/libtool"  --silent --tag CC --mode=relink gcc 
> -O2 -fPIC -Wl,--no-undefined -Werror=implicit-function-declaration 
> -Werror=int-conversion -I/tmp/SBo/freetype-2.10.0/src/truetype 
> -I/tmp/SBo/freetype-2.10.0/include 
> -I/tmp/SBo/freetype-2.10.0/include/freetype -pthread -I/usr/include/glib-2.0 
> -I/usr/lib64/glib-2.0/include -I/usr/include/pango-1.0 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
> -I/usr/lib64/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 
> -I/usr/lib64/glib-2.0/include -I/usr/include/libdrm -I/usr/include/libpng16 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz 
> -I/usr/include/glib-2.0 -I/usr/lib64/glib
 -2
>  .0/include -I/usr/include/libxml2 -I/usr/include/python2.7 -pthread 
> -version-info 3:1:0 -no-undefined -o libgutils.la -rpath /usr/lib64 
> libgutils_la-dlist.lo libgutils_la-fsys.lo libgutils_la-g_giomime.lo 
> libgutils_la-gcol.lo libgutils_la-gimage.lo libgutils_la-gimageread.lo 
> libgutils_la-gimagereadbmp.lo libgutils_la-gimagereadgif.lo 
> libgutils_la-gimagereadjpeg.lo libgutils_la-gimagereadpng.lo 
> libgutils_la-gimagereadras.lo libgutils_la-gimagereadrgb.lo 
> libgutils_la-gimagereadtiff.lo libgutils_la-gimagereadxbm.lo 
> libgutils_la-gimagereadxpm.lo libgutils_la-gimagewritebmp.lo 
> libgutils_la-gimagewritegimage.lo libgutils_la-gimagewritejpeg.lo 
> libgutils_la-gimagewritepng.lo libgutils_la-gimagewritexbm.lo 
> libgutils_la-gimagewritexpm.lo libgutils_la-gio.lo libgutils_la-giofile.lo 
> libgutils_la-giotrans.lo libgutils_la-gutils.lo libgutils_la-gwwintl.lo 
> libgutils_la-prefs.lo libgutils_la-unicodelibinfo.lo -lgif -ljpeg -lpng 
> -ltiff -lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lcairo 
 -l
>  pangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 
> -lfontconfig -lfreetype -lXft -lSM -lICE -lreadline -ltermcap -lfreetype -lz 
> -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lxml2 ../Unicode/libgunicode.la -lX11 -lm 
> -inst-prefix-dir /tmp/SBo/package-fontforge)
> .libs/libgutils_la-fsys.o: In function `getFontForgeUserDir':
> fsys.c:(.text+0x1775): undefined reference to `smprintf'
> fsys.c:(.text+0x17c5): undefined reference to `smprintf'
> collect2: error: ld returned 1 exit status
> libtool:   error: error: relink 'libgutils.la' with the above command before 
> installing it
> make[3]: *** [install-libLTLIBRARIES] Error 1
> Makefile:559: recipe for target 'install-libLTLIBRARIES' failed
> make[3]: Leaving directory '/tmp/SBo/fontforge-20190801/gutils'
> make[2]: *** [install-am] Error 2
> Makefile:952: recipe for target 'install-am' failed
> make[2]: Leaving directory '/tmp/SBo/fontforge-20190801/gutils'
> make[1]: *** [install-recursive] Error 1
> Makefile:788: recipe for target 'install-recursive' failed
> make[1]: Leaving directory '/tmp/SBo/fontforge-20190801'
> make: *** [install] Error 2
> Makefile:1085: recipe for target 'install' failed
> Failures:
>   fontforge: fontforge.SlackBuild return non-zero
>
>
> Can anyone provide any insight on this?  Or even a report that it
> successfully compiled for you on S64 14.2?

I was about to test it, but before trying I just want to be sure that
you have noted this bit in fontforge's README

"NOTE: please remove previous version before building new version."

have you done that?

Matteo

[Slackbuilds-users] fontforge

2020-10-21 Thread Jim Diamond via SlackBuilds-users 
When I try to compile the most recent update to fontforge on S64-14.2,
I get


libtool: install: (cd /tmp/SBo/package-fontforge/usr/lib64 && { ln -s -f 
libgunicode.so.5.0.0 libgunicode.so.5 || { rm -f libgunicode.so.5 && ln -s 
libgunicode.so.5.0.0 libgunicode.so.5; }; })
libtool: install: (cd /tmp/SBo/package-fontforge/usr/lib64 && { ln -s -f 
libgunicode.so.5.0.0 libgunicode.so || { rm -f libgunicode.so && ln -s 
libgunicode.so.5.0.0 libgunicode.so; }; })
libtool: install: /usr/bin/ginstall -c .libs/libgunicode.lai 
/tmp/SBo/package-fontforge/usr/lib64/libgunicode.la
libtool: warning: remember to run 'libtool --finish /usr/lib64'
make[3]: Leaving directory '/tmp/SBo/fontforge-20190801/Unicode'
make[2]: Leaving directory '/tmp/SBo/fontforge-20190801/Unicode'
Making install in gutils
make[2]: Entering directory '/tmp/SBo/fontforge-20190801/gutils'
make[3]: Entering directory '/tmp/SBo/fontforge-20190801/gutils'
make[3]: Nothing to be done for 'install-data-am'.
 /usr/bin/mkdir -p '/tmp/SBo/package-fontforge/usr/lib64'
 /bin/sh ../libtool   --mode=install /usr/bin/ginstall -c   libgutils.la 
'/tmp/SBo/package-fontforge/usr/lib64'
libtool: warning: relinking 'libgutils.la'
libtool: install: (cd /tmp/SBo/fontforge-20190801/gutils; /bin/sh 
"/tmp/SBo/fontforge-20190801/libtool"  --silent --tag CC --mode=relink gcc -O2 
-fPIC -Wl,--no-undefined -Werror=implicit-function-declaration 
-Werror=int-conversion -I/tmp/SBo/freetype-2.10.0/src/truetype 
-I/tmp/SBo/freetype-2.10.0/include -I/tmp/SBo/freetype-2.10.0/include/freetype 
-pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz 
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pango-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/harfbuzz 
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libdrm 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2
 .0/include -I/usr/include/libxml2 -I/usr/include/python2.7 -pthread 
-version-info 3:1:0 -no-undefined -o libgutils.la -rpath /usr/lib64 
libgutils_la-dlist.lo libgutils_la-fsys.lo libgutils_la-g_giomime.lo 
libgutils_la-gcol.lo libgutils_la-gimage.lo libgutils_la-gimageread.lo 
libgutils_la-gimagereadbmp.lo libgutils_la-gimagereadgif.lo 
libgutils_la-gimagereadjpeg.lo libgutils_la-gimagereadpng.lo 
libgutils_la-gimagereadras.lo libgutils_la-gimagereadrgb.lo 
libgutils_la-gimagereadtiff.lo libgutils_la-gimagereadxbm.lo 
libgutils_la-gimagereadxpm.lo libgutils_la-gimagewritebmp.lo 
libgutils_la-gimagewritegimage.lo libgutils_la-gimagewritejpeg.lo 
libgutils_la-gimagewritepng.lo libgutils_la-gimagewritexbm.lo 
libgutils_la-gimagewritexpm.lo libgutils_la-gio.lo libgutils_la-giofile.lo 
libgutils_la-giotrans.lo libgutils_la-gutils.lo libgutils_la-gwwintl.lo 
libgutils_la-prefs.lo libgutils_la-unicodelibinfo.lo -lgif -ljpeg -lpng -ltiff 
-lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lcairo -l
 pangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig 
-lfreetype -lXft -lSM -lICE -lreadline -ltermcap -lfreetype -lz -lgio-2.0 
-lgobject-2.0 -lglib-2.0 -lxml2 ../Unicode/libgunicode.la -lX11 -lm 
-inst-prefix-dir /tmp/SBo/package-fontforge)
.libs/libgutils_la-fsys.o: In function `getFontForgeUserDir':
fsys.c:(.text+0x1775): undefined reference to `smprintf'
fsys.c:(.text+0x17c5): undefined reference to `smprintf'
collect2: error: ld returned 1 exit status
libtool:   error: error: relink 'libgutils.la' with the above command before 
installing it
make[3]: *** [install-libLTLIBRARIES] Error 1
Makefile:559: recipe for target 'install-libLTLIBRARIES' failed
make[3]: Leaving directory '/tmp/SBo/fontforge-20190801/gutils'
make[2]: *** [install-am] Error 2
Makefile:952: recipe for target 'install-am' failed
make[2]: Leaving directory '/tmp/SBo/fontforge-20190801/gutils'
make[1]: *** [install-recursive] Error 1
Makefile:788: recipe for target 'install-recursive' failed
make[1]: Leaving directory '/tmp/SBo/fontforge-20190801'
make: *** [install] Error 2
Makefile:1085: recipe for target 'install' failed
Failures:
  fontforge: fontforge.SlackBuild return non-zero


Can anyone provide any insight on this?  Or even a report that it
successfully compiled for you on S64 14.2?

Thanks.

Jim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge

2019-08-24 Thread Willy Sudiarto Raharjo 
> One of sources for fontforge is
> http://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.10.0.tar.lz
> 
> It doesn't exist, now it's:
> https://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.10.1.tar.xz

Thanks
fixed in my branch


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] fontforge

2019-08-23 Thread Alexander Verbovetsky 
Hello,

One of sources for fontforge is
http://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.10.0.tar.lz

It doesn't exist, now it's:
https://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.10.1.tar.xz

Best regards,
Alexander
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread Didier Spaier 
On 10/5/18 7:46 PM, Rich Shepard wrote:
>   I have an older desktop (never activeated) with an Asus Sabertooth 990fx
> motherboard and AMD FX-8150 CPU. I'll install 14.2 on it when the new hard
> drive arrives, apply all patches, and then try to build the SBo packages.
> This hardware is from 2011, not 2018 and I'm sure that will make a
> difference.

None of the error messages you showed can lead to make such an assumption,
let alone be sure of that.

The *only* way to make sure would be to make a clean 14.2 installation with
all patches applied and see what you get building the packages from the
SBo slackbuilds.

But yes ,make a clean install on the old box and see what happens.
At least that will be a first step in the good direction.

Didier
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread Rich Shepard 

On Fri, 5 Oct 2018, Didier Spaier wrote:


I am pretty sure you are *not* building an a *clean* 64-bit only system
with *no multilib* but with all patches listed in the ChangeLog applied.


Didier,

  I installed the multilibs this past Wednesday. I had issues last week with
SBo packages not building.


Until you reinstall from scratch Slackware64-14.2 and do *not* install on it
any package not shipped in Slackware but those built from SlackBuilds that
you downloaded from https://slackwbuilds.org, you are just making people
trying to help you on this list waste their time.


  I have an older desktop (never activeated) with an Asus Sabertooth 990fx
motherboard and AMD FX-8150 CPU. I'll install 14.2 on it when the new hard
drive arrives, apply all patches, and then try to build the SBo packages.
This hardware is from 2011, not 2018 and I'm sure that will make a
difference.

Regards,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread Arnaud 
> Rich,
> 
> I am pretty sure you are *not* building an a *clean* 64-bit only system with
> *no multilib* but with all patches listed in the ChangeLog applied.
> 
> Until you reinstall from scratch Slackware64-14.2 and do *not* install on it
> any package not shipped in Slackware but those built from SlackBuilds that
> you downloaded from https://slackwbuilds.org, you are just making people
> trying to help you on this list waste their time.
> 
> Didier

I'll go further :

My suggestion, Rich, has been already presented in this thread.
It is to create a chrooted clean 64-14.2 fully patched installation.

 * Create a destination directory, for example : /srv/slackware/
 * Simply go to a source directory, remove all kdei languages you won't use (or
all of kdei) :
slackware64-14.2/slackware64$ installpkg --root=/srv/slackware/ */*.t?z
 * Then go inside it :
$ chroot /srv/slackware/ bash -l
 * You'd better mount /proc /dev and /sys
 * Here you configure slackpkg, and update your all chrooted slackware for
recent patches. (don't forget to copy /etc/resolv.conf
into /srv/slackware/etc/resolv.conf to get network working inside the chroot).

 * Then you build whatever you need, installing dependencies.
 * And when you're finished, you remove all locally built installed packages for
the next package you'll try to install.
I'd advise installing python3 and leaving it there, many python
SlackBuilds are silently building for python3 if it is installed, and it might
be what you want for your box, and python3 being present does not pose any
side problem anyway.

The packages you built on the chrooted environment should work on your
multilib box without any problem, if they don't then your slackware install is
somehow broken.

I started doing this after having troubles building too many packages,
multilib is a problem for some slackbuilds (for some time I used to
move /usr/lib/ into something like /usr/lib32/ before building a problematic
packages, just to be sure it found only /usr/lib64/, but it *is* ugly).
Furthermore you have a way better control over what you are building
against.

If *that* still fails, then you have a pretty good reason to ask for help.
Else, trying to figure out what may be wrong with your specific box, with your
specific environment, with your specific packages installed, is going to be very
hard, and most of the time not very useful.

The advantage of chroot over a VM is that it is wy easier to setup, and it
takes less disk space too, and less resources (it's completely passive : it does
nothing when you do nothing). And mostly, for what you're doing (build packages
for your box) there are no disadvantages.

I'll clean and send a script that does all this stuff automagically.

-- 
Arnaud 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread Didier Spaier 
Rich,

I am pretty sure you are *not* building an a *clean* 64-bit only system with
*no multilib* but with all patches listed in the ChangeLog applied.

Until you reinstall from scratch Slackware64-14.2 and do *not* install on it
any package not shipped in Slackware but those built from SlackBuilds that
you downloaded from https://slackwbuilds.org, you are just making people
trying to help you on this list waste their time.

Didier

On 10/5/18 6:27 PM, Rich Shepard wrote:
> On Fri, 5 Oct 2018, David Woodfall wrote:
> 
>>>   From a suggestion provided by someone here for a different package.
>>
>> Don't ask for support for slackbuilds that don't originate from
>> slackbuilds.org. I spent a wasted few hours yesterday trying to find
>> a solution to fix it since I maintain it. If you want help with
>> someone else's build then go to them and don't waste my time.
> 
> Dave,
> 
>   I was not sufficiently clear. This was a suggestion offered for another
> SBo package. The package maintaier offered the same syntax for the
> slackbuild script, LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \, as you did.
> 
>   Several respondents on the mail list have offered suggestions for the few
> packages that won't build on this new hardware, including Willy's advice to
> upgrade the BIOS firmware, which I did.
> 
>   If a problem is not related to a slackbuild script I would not be asking
> for help from the SBo mail list.
> 
> Rich

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread David Woodfall 
On Friday 5 October 2018 09:27,
Rich Shepard  put forth the proposition:
> On Fri, 5 Oct 2018, David Woodfall wrote:
>
> > >   From a suggestion provided by someone here for a different package.
> >
> > Don't ask for support for slackbuilds that don't originate from
> > slackbuilds.org. I spent a wasted few hours yesterday trying to find
> > a solution to fix it since I maintain it. If you want help with
> > someone else's build then go to them and don't waste my time.
>
> Dave,
>
>   I was not sufficiently clear. This was a suggestion offered for another
> SBo package. The package maintaier offered the same syntax for the
> slackbuild script, LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \, as you did.

I said to use GLIB_CFLAGS with '-I', not LDFLAGS with '-L'.
Totally different things. You stated that the script already had
GLIB_CFALGS in it.

I have built and used fontforge on multilib many times with no
problems at all. Something in your system is screwy.

Anyway I've spent enough time on this.

>   Several respondents on the mail list have offered suggestions for the few
> packages that won't build on this new hardware, including Willy's advice to
> upgrade the BIOS firmware, which I did.
>
>   If a problem is not related to a slackbuild script I would not be asking
> for help from the SBo mail list.
>
> Rich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>



--
Dave

Cinemuck, n.:
  The combination of popcorn, soda, and melted chocolate which
covers the floors of movie theaters.
-- Rich Hall, "Sniglets"

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread Rich Shepard 

On Fri, 5 Oct 2018, David Woodfall wrote:


  From a suggestion provided by someone here for a different package.


Don't ask for support for slackbuilds that don't originate from
slackbuilds.org. I spent a wasted few hours yesterday trying to find
a solution to fix it since I maintain it. If you want help with
someone else's build then go to them and don't waste my time.


Dave,

  I was not sufficiently clear. This was a suggestion offered for another
SBo package. The package maintaier offered the same syntax for the
slackbuild script, LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \, as you did.

  Several respondents on the mail list have offered suggestions for the few
packages that won't build on this new hardware, including Willy's advice to
upgrade the BIOS firmware, which I did.

  If a problem is not related to a slackbuild script I would not be asking
for help from the SBo mail list.

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread David Woodfall 
On Friday 5 October 2018 08:24,
Rich Shepard  put forth the proposition:
> On Fri, 5 Oct 2018, David Woodfall wrote:
>
> > Eh? Which version and where did you get it? Current version for 14.2 is
> > 20170731 and there is no GLIB_CFLAGS in there. I had to double check again
> > that because I maintain it.
>
> Dave,
>
>   From a suggestion provided by someone here for a different package.

Don't ask for support for slackbuilds that don't originate from
slackbuilds.org. I spent a wasted few hours yesterday trying to find
a solution to fix it since I maintain it. If you want help with
someone else's build then go to them and don't waste my time.

> > Aside from that you could also try using CPPFLAGS with the setting.
>
>   Okay.
>
> > Which application needed it? It's not the most user-friendly thing in the
> > world, for new users anyway. Font editing is in a realm of its own.
>
>   Last year some time I needed to convert no-longer-supported fonts (Type1?) 
> to .odf
> and fontforge did the trick.
>
>   Also in realms of their own are typography, page layout, and similar arts
> best left to experts. :-)
>
> Best regards,
>
> Rich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>



--
Dave

You will be surprised by a loud noise.

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread Rich Shepard 

On Fri, 5 Oct 2018, David Woodfall wrote:


Aside from that you could also try using CPPFLAGS with the setting.


Dave,

  Unfortunately this makes no difference.

Thanks again for all your efforts,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread David Woodfall 
On Friday 5 October 2018 08:24,
Rich Shepard  put forth the proposition:
> On Fri, 5 Oct 2018, David Woodfall wrote:
>
> > Eh? Which version and where did you get it? Current version for 14.2 is
> > 20170731 and there is no GLIB_CFLAGS in there. I had to double check again
> > that because I maintain it.
>
> Dave,
>
>   From a suggestion provided by someone here for a different package.

Ah well, I have no idea what is in that so I can't really help any
further.

> > Aside from that you could also try using CPPFLAGS with the setting.
>
>   Okay.
>
> > Which application needed it? It's not the most user-friendly thing in the
> > world, for new users anyway. Font editing is in a realm of its own.
>
>   Last year some time I needed to convert no-longer-supported fonts (Type1?) 
> to .odf
> and fontforge did the trick.
>
>   Also in realms of their own are typography, page layout, and similar arts
> best left to experts. :-)
>
> Best regards,
>
> Rich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>



--
Dave

"Laughter is the closest distance between two people."
-- Victor Borge

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread Rich Shepard 

On Fri, 5 Oct 2018, David Woodfall wrote:


Eh? Which version and where did you get it? Current version for 14.2 is
20170731 and there is no GLIB_CFLAGS in there. I had to double check again
that because I maintain it.


Dave,

  From a suggestion provided by someone here for a different package.


Aside from that you could also try using CPPFLAGS with the setting.


  Okay.


Which application needed it? It's not the most user-friendly thing in the
world, for new users anyway. Font editing is in a realm of its own.


  Last year some time I needed to convert no-longer-supported fonts (Type1?) to 
.odf
and fontforge did the trick.

  Also in realms of their own are typography, page layout, and similar arts
best left to experts. :-)

Best regards,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread David Woodfall 
On Friday 5 October 2018 07:41,
Rich Shepard  put forth the proposition:
> On Thu, 4 Oct 2018, David Woodfall wrote:
>
> > After doing some building and diffing what sticks out is that in your
> > log make is including
> >
> > /usr/lib/glib-2.0/include/glibconfig.h
> >
> > Whereas my log shows
> >
> > /usr/lib64/glib-2.0/include/glibconfig.h
> >
> > This is also on a 14.2 multilib system.
> >
> > Can you test the following change in the slackbuild just after the
> > CFLAGS= and CXXFLAGS= lines add:
> >
> > GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \
> >
> > If that doesn't work you could try exporting the variable and remove
> > the '\' on the end.
>
> Dave,
>
>   That added GLIB_CFLAGS line is already in the build script.

Eh? Which version and where did you get it? Current version for 14.2
is 20170731 and there is no GLIB_CFLAGS in there. I had to double
check again that because I maintain it.

Aside from that you could also try using CPPFLAGS with the setting.

> What I find
> puzzling is that so many other libraries are built before this one fails. If
> the makefile was looking in /usr/lib/ rather than /usr/lib64/ I'd expect the
> build to fail at the first library.

No always true. I forced it to look in /usr/lib and it didn't fail
until the point that yours did, quite far into the build.

>   Regardless, I don't need fontforge on the new desktop. Perhaps some time
> in the future it might be needed, but the probability is quite low.

Which application needed it? It's not the most user-friendly thing in
the world, for new users anyway. Font editing is in a realm of its own.

>   My focus is getting a working server/workstation and I need to focus on
> critical files. Perhaps when 15.0 comes out all these issues will go away.
>
>   Thanks very much for your efforts with fontforge.
>
> Best regards,
>
> Rich

--
Dave

A copy of the universe is not what is required of art; one of the
damned things is ample.
-- Rebecca West

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-05 Thread Rich Shepard 

On Thu, 4 Oct 2018, David Woodfall wrote:


After doing some building and diffing what sticks out is that in your
log make is including

/usr/lib/glib-2.0/include/glibconfig.h

Whereas my log shows

/usr/lib64/glib-2.0/include/glibconfig.h

This is also on a 14.2 multilib system.

Can you test the following change in the slackbuild just after the
CFLAGS= and CXXFLAGS= lines add:

GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \

If that doesn't work you could try exporting the variable and remove
the '\' on the end.


Dave,

  That added GLIB_CFLAGS line is already in the build script. What I find
puzzling is that so many other libraries are built before this one fails. If
the makefile was looking in /usr/lib/ rather than /usr/lib64/ I'd expect the
build to fail at the first library.

  Regardless, I don't need fontforge on the new desktop. Perhaps some time
in the future it might be needed, but the probability is quite low.

  My focus is getting a working server/workstation and I need to focus on
critical files. Perhaps when 15.0 comes out all these issues will go away.

  Thanks very much for your efforts with fontforge.

Best regards,

Rich

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-04 Thread David Woodfall 
On Thursday 4 October 2018 23:54,
Dave Woodfall  put forth the proposition:
> On Wednesday 3 October 2018 14:03,
> Rich Shepard  put forth the proposition:
> > On Wed, 3 Oct 2018, David Woodfall wrote:
> >
> > > Could you please make a build log and attach it to a reply here?
> >
> > Dave,
> >
> >   An xzipped build log is attached. I'm really interested in learning what
> > insights are hidden from me in the log.
> >
> > Thanks,
> >
> > Rich
>
> After doing some building and diffing what sticks out is that in your
> log make is including
>
> /usr/lib/glib-2.0/include/glibconfig.h
>
> Whereas my log shows
>
> /usr/lib64/glib-2.0/include/glibconfig.h
>
> This is also on a 14.2 multilib system.
>
> Can you test the following change in the slackbuild just after the
> CFLAGS= and CXXFLAGS= lines add:
>
> GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \
>
> If that doesn't work you could try exporting the variable and remove
> the '\' on the end.

If you export it, it needs to go somewhere /above/ the CFLAGS= line.

> It's a bit of a long shot but it may help. Something in your
> environment seems to be causing the build process to think it's not
> x86_64 for some reason. As others have said, you may want to think
> about building packages in a non-multilib VM when this kind of thing
> happens. I tend to use a chrooted installation for this because it
> takes no extra software and you don't need to boot anything to use
> it either.
>
> --
> Dave

--
Dave

Ankh if you love Isis.

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-04 Thread David Woodfall 
On Wednesday 3 October 2018 14:03,
Rich Shepard  put forth the proposition:
> On Wed, 3 Oct 2018, David Woodfall wrote:
>
> > Could you please make a build log and attach it to a reply here?
>
> Dave,
>
>   An xzipped build log is attached. I'm really interested in learning what
> insights are hidden from me in the log.
>
> Thanks,
>
> Rich

After doing some building and diffing what sticks out is that in your
log make is including

/usr/lib/glib-2.0/include/glibconfig.h

Whereas my log shows

/usr/lib64/glib-2.0/include/glibconfig.h

This is also on a 14.2 multilib system.

Can you test the following change in the slackbuild just after the
CFLAGS= and CXXFLAGS= lines add:

GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \

If that doesn't work you could try exporting the variable and remove
the '\' on the end.

It's a bit of a long shot but it may help. Something in your
environment seems to be causing the build process to think it's not
x86_64 for some reason. As others have said, you may want to think
about building packages in a non-multilib VM when this kind of thing
happens. I tend to use a chrooted installation for this because it
takes no extra software and you don't need to boot anything to use
it either.

--
Dave

"I'm not under the alkafluence of inkahol that some thinkle peep I am.
It's just the drunker I sit here the longer I get."

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Rich Shepard 

On Wed, 3 Oct 2018, David Woodfall wrote:


Could you please make a build log and attach it to a reply here?


Dave,

  An xzipped build log is attached. I'm really interested in learning what
insights are hidden from me in the log.

Thanks,

Rich

build.log.xz
Description: Binary data
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Rich Shepard 

On Wed, 3 Oct 2018, David Woodfall wrote:


This line:

LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \

Try adding that under the CXXFLAGS= line in the slackbuild. It's
worth remembering as the first thing to try on a multilib system when
a build fails.


Dave,

  Didn't help with fontforge. Will try now with more important packages such
as OpenBLAS.

Thanks,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Rich Shepard 

On Wed, 3 Oct 2018, Matteo Bernardini wrote:


it could mean also that you:


  

Thank you, Matteo,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Rich Shepard 

On Wed, 3 Oct 2018, Daniel Prosser wrote:


Did you try following the instructions in the FAQ yet?


Dan,

  Yes. adding that additional library directive made no difference with
fontforge; will try with the other packages now.


It that doesn't work, building in a VM or LXC container is much less
disruptive than reinstalling the OS on your "production" machine.


  The new host is not yet the production machine. I'm trying to get it
there. :-)

Regards,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread David Woodfall 
On Wednesday 3 October 2018 13:16,
Rich Shepard  put forth the proposition:
> On Wed, 3 Oct 2018, Matteo Bernardini wrote:
>
> > so it seems that in your case it is actually applicable: try building it
> > on a pure 64 system (here I build my packages on virtual machines).
>
> Matteo,
>
>   What makes a 64-bit system 'pure?' 14-2 was installed on a virgin disk and
> this morning I added the multilibs because adobe-reader works on only 32-bit
> systems.
>
> Rich

You could try creating a 64 bit chrooted environment to build
packages in. I do that for a few things that fail on multilib.

Basically you install slackware into a directory. Once done, you can
get a root login by typing:

chroot /path/to/chroot /bin/bash

installpkg has a --root option which you can use to installl packages
anywhere you like.

--
Dave

Three great scientific theories of the structure of the universe are
the molecular, the corpuscular and the atomic.  A fourth affirms, with
Haeckel, the condensation or precipitation of matter from ether --
whose existence is proved by the condensation or precipitation ... A
fifth theory is held by idiots, but it is doubtful if they know any
more about the matter than the others.
-- Ambrose Bierce, "The Devil's Dictionary"

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Rich Shepard 

On Thu, 4 Oct 2018, Willy Sudiarto Raharjo wrote:


Non Multilibs is a pure 64-bit system


  Okay.

Thanks,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread David Woodfall 
On Wednesday 3 October 2018 12:58,
Rich Shepard  put forth the proposition:
> On Wed, 3 Oct 2018, sborg63 wrote:
>
> > With multilib you could get confusion between /usr/lib
> > and /usr/lib64. Maybe it should be looking in /usr/lib64.
>
>   This could be, but glib is found in /usr/lib64.
>
> > Have you considered this: https://www.slackbuilds.org/faq/#multilib
>
>   Don't see anything applicable.

This line:

LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \

Try adding that under the CXXFLAGS= line in the slackbuild. It's
worth remembering as the first thing to try on a multilib system when
a build fails.

Dave

> > Plus, if the new box is the latest of the latest hardware-wise, it is
> > maybe worth considering running current because of its more 'current'
> > kernel. I had to do this whenever I got a new laptop; the hardware was
> > much better supported as well as more recent software (the openblas thread
> > springs to mind).
>
>   I have been thinking this is an issue. In the past I've always built
> systems that were back from the bleeding edge. This time my budget allowed
> me to buy components near the top, but below the 'gamers' level. Since I'm
> getting build errors on packages that built with no errors on portables with
> 64-bit CPUs (but not the fastest, most expensive models) the hardware
> newness might well be the factor.
>
>   I'll look into upgrading to current.
>
> Thanks,
>
> Rich

--
Dave

A physicist is an atom's way of knowing about atoms.
-- George Wald

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Matteo Bernardini 
Il giorno mer 3 ott 2018 alle ore 22:17 Willy Sudiarto Raharjo
 ha scritto:
>
> >   What makes a 64-bit system 'pure?' 14-2 was installed on a virgin disk
> > and
> > this morning I added the multilibs because adobe-reader works on only
> > 32-bit
> > systems.
>
> Non Multilibs is a pure 64-bit system

it could mean also that you:
1) create a virtual machine (with whatever hypervisor you prefer, but
this is not the main scope of this answer so I won't elaborate on
this);
2) install a full slackware64-14.2 and NOTHING ELSE;
3) update it to the latest patches;
4) shut it down;
5) copy the virtual machine file somewhere (or do a snapshot or
whatever the hypervisor you use for your virtual machine allows, but
this is not the main scope of this answer so I won't elaborate on
this);
6) turn it on again;
7) build the package you need on the virtual machine and copy it where
you need it;
8) turn it off again;
9) restore the virtual machine from the copy you have done.
10) start again from point 6) as needed.
This way you will always have a "pure" platform to build your packages.
In alternative to points 7 to 10 you can also install slackrepo in the
virtual machine and use that (but this is not the main scope of this
answer so I won't elaborate on this).
good luck!
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Daniel Prosser 
Did you try following the instructions in the FAQ yet?

http://slackbuilds.org/faq/#multilib

It that doesn't work, building in a VM or LXC container is much less disruptive 
than reinstalling the OS on your "production" machine.

Dan
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread David Woodfall 
On Wednesday 3 October 2018 11:19,
Rich Shepard  put forth the proposition:
>   fontforge-20170731 built on my 14-2/x86 desktop but fails to complete on
> the new 14-2/x86_64 box (with AlienBOB's multilibs installed). The cause of
> the error is not obvious to me looking at the output:
>
> collabclientui.c:462:1: note: in expansion of macro ‘G_DEFINE_TYPE’
>  G_DEFINE_TYPE (CollabSessionCallbacks, collab_sessioncallbacks, 
> G_TYPE_OBJECT)
>  ^
> In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0,
>  from /usr/include/glib-2.0/glib/gtypes.h:32,
>  from /usr/include/glib-2.0/glib/galloca.h:32,
>  from /usr/include/glib-2.0/glib.h:30,
>  from ../fontforge/ffglib.h:27,
>  from ../fontforge/collabclientpriv.h:67,
>  from collabclientui.c:29:
> /usr/include/glib-2.0/glib/gmacros.h:182:53: error: size of array 
> ‘_GStaticAssertCompileTimeAssertion_2’ is negative
>  #define G_STATIC_ASSERT(expr) typedef char G_PASTE 
> (_GStaticAssertCompileTimeAssertion_, __COUNTER_
>  ^
> /usr/include/glib-2.0/glib/gmacros.h:179:47: note: in definition of macro 
> ‘G_PASTE_ARGS’
>  #define G_PASTE_ARGS(identifier1,identifier2) identifier1 ## identifier2
>^
> /usr/include/glib-2.0/glib/gmacros.h:182:44: note: in expansion of macro 
> ‘G_PASTE’
>  #define G_STATIC_ASSERT(expr) typedef char G_PASTE 
> (_GStaticAssertCompileTimeAssertion_, __COUNTER_
> ^
> /usr/include/glib-2.0/glib/gthread.h:256:5: note: in expansion of macro 
> ‘G_STATIC_ASSERT’
>  G_STATIC_ASSERT (sizeof *(location) == sizeof (gpointer));   \
>  ^
> /usr/include/glib-2.0/gobject/gtype.h:1972:7: note: in expansion of macro 
> ‘g_once_init_leave’
>g_once_init_leave (_define_type_id__volatile, g_define_type_id); \
>^
> /usr/include/glib-2.0/gobject/gtype.h:1729:117: note: in expansion of macro 
> ‘_G_DEFINE_TYPE_EXTENDED_END’
>  ED(TN, t_n, T_P, _f_, _C_) _G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, 
> _f_) {_C_;} _G_DEFINE_T
>   
>^
> /usr/include/glib-2.0/gobject/gtype.h:1587:43: note: in expansion of macro 
> ‘G_DEFINE_TYPE_EXTENDED’
>  #define G_DEFINE_TYPE(TN, t_n, T_P)   G_DEFINE_TYPE_EXTENDED (TN, t_n, 
> T_P, 0, {})
>^
> collabclientui.c:462:1: note: in expansion of macro ‘G_DEFINE_TYPE’
>  G_DEFINE_TYPE (CollabSessionCallbacks, collab_sessioncallbacks, 
> G_TYPE_OBJECT)
>  ^
> Makefile:2403: recipe for target 'libfontforgeexe_la-collabclientui.lo' failed
> make[3]: *** [libfontforgeexe_la-collabclientui.lo] Error 1
> make[3]: Leaving directory '/tmp/SBo/fontforge-20170731/fontforgeexe'
> Makefile:2524: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory '/tmp/SBo/fontforge-20170731/fontforgeexe'
> Makefile:1580: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/tmp/SBo/fontforge-20170731'
> Makefile:1417: recipe for target 'all' failed
> make: *** [all] Error 2
>
>   Please suggest how I should proceed to fix this.
>
> Rich

Hi

I've just tested this on my multilib laptop and it built fine. It's
not really obvious where the problem is from the output.

Could you please make a build log and attach it to a reply here?

You can make one by:

./fontforge.SlackBuild 2>&1 | tee build.log

Thanks

--
Dave

Conscience is the inner voice that warns us somebody is looking
-- H. L. Mencken

.--.  oo
   ()//
~'


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Willy Sudiarto Raharjo 
>   What makes a 64-bit system 'pure?' 14-2 was installed on a virgin disk
> and
> this morning I added the multilibs because adobe-reader works on only
> 32-bit
> systems.

Non Multilibs is a pure 64-bit system


-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Rich Shepard 

On Wed, 3 Oct 2018, Matteo Bernardini wrote:


so it seems that in your case it is actually applicable: try building it
on a pure 64 system (here I build my packages on virtual machines).


Matteo,

  What makes a 64-bit system 'pure?' 14-2 was installed on a virgin disk and
this morning I added the multilibs because adobe-reader works on only 32-bit
systems.

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Matteo Bernardini 
Il giorno mer 3 ott 2018 alle ore 21:58 Rich Shepard
 ha scritto:
>
> On Wed, 3 Oct 2018, sborg63 wrote:
>
> > With multilib you could get confusion between /usr/lib
> > and /usr/lib64. Maybe it should be looking in /usr/lib64.
>
>This could be, but glib is found in /usr/lib64.
>
> > Have you considered this: https://www.slackbuilds.org/faq/#multilib
>
>Don't see anything applicable.

in your log (for some reason that I won't investigate) you got this line

"In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0,"

that file is much different compared to /usr/lib64/glib-2.0/include/glibconfig.h

so it seems that in your case it is actually applicable: try building
it on a pure 64 system (here I build my packages on virtual machines).

Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error

2018-10-03 Thread Rich Shepard 

On Wed, 3 Oct 2018, sborg63 wrote:


With multilib you could get confusion between /usr/lib
and /usr/lib64. Maybe it should be looking in /usr/lib64.


  This could be, but glib is found in /usr/lib64.


Have you considered this: https://www.slackbuilds.org/faq/#multilib


  Don't see anything applicable.


Plus, if the new box is the latest of the latest hardware-wise, it is
maybe worth considering running current because of its more 'current'
kernel. I had to do this whenever I got a new laptop; the hardware was
much better supported as well as more recent software (the openblas thread
springs to mind).


  I have been thinking this is an issue. In the past I've always built
systems that were back from the bleeding edge. This time my budget allowed
me to buy components near the top, but below the 'gamers' level. Since I'm
getting build errors on packages that built with no errors on portables with
64-bit CPUs (but not the fastest, most expensive models) the hardware
newness might well be the factor.

  I'll look into upgrading to current.

Thanks,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Fontforge build error; SlackBuilds-users Digest, Vol 150, Issue 4

2018-10-03 Thread sborg63 
On Wed, 03 Oct 2018 18:19:57 +
slackbuilds-users-requ...@slackbuilds.org wrote:

> Date: Wed, 3 Oct 2018 11:19:54 -0700 (PDT)
> From: Rich Shepard 
> To: slackbuilds-users@slackbuilds.org
> Subject: [Slackbuilds-users] Fontforge build error
> Message-ID: 
> Content-Type: text/plain; format=flowed; charset=ISO-8859-7

>   fontforge-20170731 built on my 14-2/x86 desktop but fails to
>   complete on the new 14-2/x86_64 box (with AlienBOB's multilibs
>  installed). 
..
> In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0,

With multilib you could get confusion between /usr/lib
and /usr/lib64. Maybe it should be looking in /usr/lib64.

Have you considered this: https://www.slackbuilds.org/faq/#multilib

Plus, if the new box is the latest of the latest hardware-wise, it is
maybe worth considering running current because of its more 'current'
kernel. I had to do this whenever I got a new laptop;  the hardware was
much better supported as well as more recent software (the openblas
thread springs to mind).

hth 

rob
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Fontforge build error

2018-10-03 Thread Rich Shepard 

  fontforge-20170731 built on my 14-2/x86 desktop but fails to complete on
the new 14-2/x86_64 box (with AlienBOB's multilibs installed). The cause of
the error is not obvious to me looking at the output:

collabclientui.c:462:1: note: in expansion of macro ‘G_DEFINE_TYPE’
 G_DEFINE_TYPE (CollabSessionCallbacks, collab_sessioncallbacks, G_TYPE_OBJECT)
 ^
In file included from /usr/lib/glib-2.0/include/glibconfig.h:9:0,
 from /usr/include/glib-2.0/glib/gtypes.h:32,
 from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from ../fontforge/ffglib.h:27,
 from ../fontforge/collabclientpriv.h:67,
 from collabclientui.c:29:
/usr/include/glib-2.0/glib/gmacros.h:182:53: error: size of array 
‘_GStaticAssertCompileTimeAssertion_2’ is negative
 #define G_STATIC_ASSERT(expr) typedef char G_PASTE 
(_GStaticAssertCompileTimeAssertion_, __COUNTER_
 ^
/usr/include/glib-2.0/glib/gmacros.h:179:47: note: in definition of macro 
‘G_PASTE_ARGS’
 #define G_PASTE_ARGS(identifier1,identifier2) identifier1 ## identifier2
   ^
/usr/include/glib-2.0/glib/gmacros.h:182:44: note: in expansion of macro 
‘G_PASTE’
 #define G_STATIC_ASSERT(expr) typedef char G_PASTE 
(_GStaticAssertCompileTimeAssertion_, __COUNTER_
^
/usr/include/glib-2.0/glib/gthread.h:256:5: note: in expansion of macro 
‘G_STATIC_ASSERT’
 G_STATIC_ASSERT (sizeof *(location) == sizeof (gpointer));   \
 ^
/usr/include/glib-2.0/gobject/gtype.h:1972:7: note: in expansion of macro 
‘g_once_init_leave’
   g_once_init_leave (_define_type_id__volatile, g_define_type_id); \
   ^
/usr/include/glib-2.0/gobject/gtype.h:1729:117: note: in expansion of macro 
‘_G_DEFINE_TYPE_EXTENDED_END’
 ED(TN, t_n, T_P, _f_, _C_) _G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, 
_f_) {_C_;} _G_DEFINE_T

 ^
/usr/include/glib-2.0/gobject/gtype.h:1587:43: note: in expansion of macro 
‘G_DEFINE_TYPE_EXTENDED’
 #define G_DEFINE_TYPE(TN, t_n, T_P)   G_DEFINE_TYPE_EXTENDED (TN, t_n, 
T_P, 0, {})
   ^
collabclientui.c:462:1: note: in expansion of macro ‘G_DEFINE_TYPE’
 G_DEFINE_TYPE (CollabSessionCallbacks, collab_sessioncallbacks, G_TYPE_OBJECT)
 ^
Makefile:2403: recipe for target 'libfontforgeexe_la-collabclientui.lo' failed
make[3]: *** [libfontforgeexe_la-collabclientui.lo] Error 1
make[3]: Leaving directory '/tmp/SBo/fontforge-20170731/fontforgeexe'
Makefile:2524: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/tmp/SBo/fontforge-20170731/fontforgeexe'
Makefile:1580: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/fontforge-20170731'
Makefile:1417: recipe for target 'all' failed
make: *** [all] Error 2

  Please suggest how I should proceed to fix this.

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge-20170731 has library issue [RESOLVED]

2017-09-25 Thread Rich Shepard 

On Mon, 25 Sep 2017, Rich Shepard wrote:


 On a fully patched 14.2 system trying to build fontforge-20170731 throws
this error:


  Mea culpa! I totally forgot to remove the prior version before building
the new one. After removing the old version the new one successfully built.

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] fontforge-20170731 has library issue

2017-09-25 Thread Rich Shepard 

  On a fully patched 14.2 system trying to build fontforge-20170731 throws
this error:

.libs/libgutils_la-gimagereadxpm.o: In function `findnextkey':
gimagereadxpm.c:(.text+0x9b): undefined reference to `ff_unicode_utype'
.libs/libgutils_la-gimagereadxpm.o: In function `GImageReadXpm':
gimagereadxpm.c:(.text+0x4ec): undefined reference to `ff_unicode_utype'
.libs/libgutils_la-giohosts.o: In function `_GIO_LookupHost':
giohosts.c:(.text+0x4fe): undefined reference to `ff_unicode_utype'
collect2: error: ld returned 1 exit status
libtool:   error: error: relink 'libgutils.la' with the above command before 
installing it
Makefile:1313: recipe for target 'install-libLTLIBRARIES' failed
make[3]: *** [install-libLTLIBRARIES] Error 1
make[3]: Leaving directory '/tmp/SBo/fontforge-20170731/gutils'
Makefile:1749: recipe for target 'install-am' failed
make[2]: *** [install-am] Error 2
make[2]: Leaving directory '/tmp/SBo/fontforge-20170731/gutils'
Makefile:1580: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/fontforge-20170731'
Makefile:1877: recipe for target 'install' failed
make: *** [install] Error 2

  Please advise how to fix it.

Regards,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge 2017 update

2017-08-06 Thread King Beowulf 
On 08/06/2017 12:10 PM, David Woodfall wrote:
>>> On 08/05/2017 09:23 PM, B Watson wrote:
 On 8/5/17, King Beowulf  wrote:

> Bah. The 2017 release is just a git snapshot. The 2017 version needs
> gnulib which it git clones on the fly, so
> ./bootstrap --skip-git --skip-po
> doesn't work (amoung no git found error). gnulib in SBo is older so
> not
> sure I have time to go down that rabbit hole.

 I'm the gnulib SBo maintainer... gnulib doesn't do releases, I'm
 using the
 same snapshot "release" that's in Debian unstable (and also the latest
 Ubuntu). Does the new fontforge give a minimum version (snapshot date)
 that it requires?

 Not too much stuff in SBo requires gnulib. I wouldn't mind updating
 it to
 a newer snapshot, but it'd be nice to use a snapshot that's widely
 used &
 known not to be broken (which is why I used the version from
 Deb/Ubuntu).
>>>
>>> I haven't had a chance to try the SBo version of gnulib with the latest
>>> fontforge.  I just noticed that the new release of fontforge pulls in a
>>> git snapshot if its bootstrap script doesn't find it.  The 2015
>>> fontforge doesn't use gnulib.  Better to let David figure that out since
>>> I do need to worry about my own 35 or so scripts.
>>>
>>> -Ed
>>
>> I noticed that it also does a git clone of uthash.
>>
>> fontforge-20170731 builds OK with gnulib-20140202 and uthash-2.0.2.
>>
>> Lilypond builds OK with that fontforge installed and appears to run
>> normally, although I've never used it before so it's hard for me to
>> tell if it works properly. Both frescobaldi and rosegarden build and
>> appear to run fine using that lilypond, so I will update the fontforge
>> slackbuild.
>>
>> Dave
> 
> Changed the uthash version to 1.9.9 to match what we have on sbo.
> 
> Dave
>

Thanks, Dave.

-Ed





signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge 2017 update

2017-08-06 Thread David Woodfall 

On 08/05/2017 09:23 PM, B Watson wrote:

On 8/5/17, King Beowulf  wrote:


Bah. The 2017 release is just a git snapshot. The 2017 version needs
gnulib which it git clones on the fly, so
./bootstrap --skip-git --skip-po
doesn't work (amoung no git found error). gnulib in SBo is older so not
sure I have time to go down that rabbit hole.


I'm the gnulib SBo maintainer... gnulib doesn't do releases, I'm using the
same snapshot "release" that's in Debian unstable (and also the latest
Ubuntu). Does the new fontforge give a minimum version (snapshot date)
that it requires?

Not too much stuff in SBo requires gnulib. I wouldn't mind updating it to
a newer snapshot, but it'd be nice to use a snapshot that's widely used &
known not to be broken (which is why I used the version from Deb/Ubuntu).


I haven't had a chance to try the SBo version of gnulib with the latest
fontforge.  I just noticed that the new release of fontforge pulls in a
git snapshot if its bootstrap script doesn't find it.  The 2015
fontforge doesn't use gnulib.  Better to let David figure that out since
I do need to worry about my own 35 or so scripts.

-Ed


I noticed that it also does a git clone of uthash.

fontforge-20170731 builds OK with gnulib-20140202 and uthash-2.0.2.

Lilypond builds OK with that fontforge installed and appears to run
normally, although I've never used it before so it's hard for me to
tell if it works properly. Both frescobaldi and rosegarden build and
appear to run fine using that lilypond, so I will update the fontforge
slackbuild.

Dave


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge 2017 update

2017-08-05 Thread King Beowulf 
On 08/05/2017 09:23 PM, B Watson wrote:
> On 8/5/17, King Beowulf  wrote:
> 
>> Bah. The 2017 release is just a git snapshot. The 2017 version needs
>> gnulib which it git clones on the fly, so
>> ./bootstrap --skip-git --skip-po
>> doesn't work (amoung no git found error). gnulib in SBo is older so not
>> sure I have time to go down that rabbit hole.
> 
> I'm the gnulib SBo maintainer... gnulib doesn't do releases, I'm using the
> same snapshot "release" that's in Debian unstable (and also the latest
> Ubuntu). Does the new fontforge give a minimum version (snapshot date)
> that it requires?
> 
> Not too much stuff in SBo requires gnulib. I wouldn't mind updating it to
> a newer snapshot, but it'd be nice to use a snapshot that's widely used &
> known not to be broken (which is why I used the version from Deb/Ubuntu).

I haven't had a chance to try the SBo version of gnulib with the latest
fontforge.  I just noticed that the new release of fontforge pulls in a
git snapshot if its bootstrap script doesn't find it.  The 2015
fontforge doesn't use gnulib.  Better to let David figure that out since
I do need to worry about my own 35 or so scripts.

-Ed



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge 2017 update

2017-08-05 Thread B Watson 
On 8/5/17, King Beowulf  wrote:

> Bah. The 2017 release is just a git snapshot. The 2017 version needs
> gnulib which it git clones on the fly, so
> ./bootstrap --skip-git --skip-po
> doesn't work (amoung no git found error). gnulib in SBo is older so not
> sure I have time to go down that rabbit hole.

I'm the gnulib SBo maintainer... gnulib doesn't do releases, I'm using the
same snapshot "release" that's in Debian unstable (and also the latest
Ubuntu). Does the new fontforge give a minimum version (snapshot date)
that it requires?

Not too much stuff in SBo requires gnulib. I wouldn't mind updating it to
a newer snapshot, but it'd be nice to use a snapshot that's widely used &
known not to be broken (which is why I used the version from Deb/Ubuntu).
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge 2017 update

2017-08-05 Thread King Beowulf 
On 08/05/2017 03:15 PM, Rich Shepard wrote:
> On Sat, 5 Aug 2017, Eric Pratt wrote:
> 
>> But on the download page, if you get that same page I'm seeing, don't
>> click on the source code link. Click on the GNU+Linux link instead.
>> Following a very unintuitive chain of links, ​you end up here:
>> https://github.com/fontforge/fontforge/releases
> 
> Eric,
> 
>   Now I see how you reached that page. When I clicked on the GNU+Linux link
> I saw only two links: 'Donate' and 'Subscribe/Confirm and Download.' The
> latter took me to a page with a 'continue this way link' and then to a page
> with 'Ubuntu,' 'Compiling from Github,' and 'Installing from an rpm.' I did
> not follow that last link because I wanted a tarball, not an rpm.
> 
>   However, under the rpm files are the source file.
> 
> Thanks for taking it one step further than I did.
> 
> Rich
> 

Bah. The 2017 release is just a git snapshot. The 2017 version needs
gnulib which it git clones on the fly, so
./bootstrap --skip-git --skip-po
doesn't work (amoung no git found error). gnulib in SBo is older so not
sure I have time to go down that rabbit hole.

I'm going to kick this can down the road to the slackbuild script
maintainer...

-Ed



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge 2017 update

2017-08-05 Thread Edward Koenig 

> On Aug 5, 2017, at 2:19 PM, Eric Pratt  wrote:
> 
>> On Sat, Aug 5, 2017 at 1:55 PM, Rich Shepard  
>> wrote:
> 
>> On Sat, 5 Aug 2017, King Beowulf wrote:
>> 
>>> Fontforge has a new 2017 release.  Is there any issues I need to be aware
>>> of, or is there a particular reason the SBo version is still 2015?
>> 
>> Ed,
>> 
>>   I go to the fontforge web site  and
>> navigate to the Download page where the only two links take me to a page
>> with a link on how to contribute to the project, not the source itself. What
>> have I missed?
>> 
>> Rich
> 
> I'm not sure what page you're seeing.  When I clicked your link then clicked 
> "Download," it took me to a page with a number of links.  The page and even 
> the whole site is pretty counter-intuitive.  Some of the links are underlined 
> with a bold orange line and some aren't underlined at all.  The pages modify 
> themselves in place when clicking on certain things.  There are submit 
> buttons that seem to not give you options to not get spammed but you can 
> click them with not form input to bypass them.  Links appear where things 
> used to be and even the statically placed links are poorly placed.  It's a 
> pretty bad site.
> 
> But on the download page, if you get that same page I'm seeing, don't click 
> on the source code link.  Click on the GNU+Linux link instead.  Following a 
> very unintuitive chain of links, ​you end up here:
> 
>   https://github.com/fontforge/fontforge/releases
> 
> ​There you can see the latest release in various formats, including a 
> tarball.​
> 

Indeed. I have no idea what the webmaster/developer is smoking but he/she needs 
to stop.  

Since they are on github, I just search there directly.  

Looks like the newer releases have a bootstrap script to generate configure 
etc.  If I get the today I might give it a shot and see what happens. 

-Ed

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge 2017 update

2017-08-05 Thread Rich Shepard 

On Sat, 5 Aug 2017, King Beowulf wrote:


Fontforge has a new 2017 release.  Is there any issues I need to be aware
of, or is there a particular reason the SBo version is still 2015?


Ed,

  I go to the fontforge web site  and
navigate to the Download page where the only two links take me to a page
with a link on how to contribute to the project, not the source itself. What
have I missed?

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] fontforge 2017 update

2017-08-05 Thread King Beowulf 
Fontforge has a new 2017 release.  Is there any issues I need to be
aware of, or is there a particular reason the SBo version is still 2015?

(why, yes, I am too lazy to search the list ...)

-Ed



signature.asc
Description: OpenPGP digital signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge fails to compile

2016-08-09 Thread Fernando Lopez 
thanks will update.

On Tue, Aug 9, 2016 at 1:04 AM, Matteo Bernardini <
matteo.bernard...@gmail.com> wrote:

> 2016-08-09 8:58 GMT+02:00 Fernando Lopez :
> > I can download fine manually from the site...
> >
> >
> > Processing fontforge
> >
> > fontforge:
> > Found fontforge-20150824.tar.gz in /var/cache/sbopkg.
> > Found cidmaps.tgz in /var/cache/sbopkg.
> > fontforge not found in /var/cache/sbopkg.
> > --2016-08-09 00:55:43--
> > http://mirrors.slackware.com/slackware/slackware-current/
> source/l/freetype/freetype-2.6.3.tar.xz
> > Resolving mirrors.slackware.com (mirrors.slackware.com)...
> 207.223.116.213
> > Connecting to mirrors.slackware.com
> > (mirrors.slackware.com)|207.223.116.213|:80... connected.
> > HTTP request sent, awaiting response... 404 Not Found
> > 2016-08-09 00:55:43 ERROR 404: Not Found.
> >
> >
> > fontforge:
> > Would you like to continue processing the rest of the
> > queue or would you like to abort?  If this failed
> > package is a dependency of another package in the queue
> > then it may not make sense to continue.
> >
> > (Y)es to continue, (N)o to abort, (R)etry the build?:
>
>
> hi Fernando,
>
> I think your SBo local repository is not up-to-date as the link to the
> freetype tarball in the fontforge.info file has been updated a couple
> of weeks ago...
>
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 


Regards,
Fernando Lopez Jr.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge fails to compile

2016-08-09 Thread Matteo Bernardini 
2016-08-09 8:58 GMT+02:00 Fernando Lopez :
> I can download fine manually from the site...
>
>
> Processing fontforge
>
> fontforge:
> Found fontforge-20150824.tar.gz in /var/cache/sbopkg.
> Found cidmaps.tgz in /var/cache/sbopkg.
> fontforge not found in /var/cache/sbopkg.
> --2016-08-09 00:55:43--
> http://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.6.3.tar.xz
> Resolving mirrors.slackware.com (mirrors.slackware.com)... 207.223.116.213
> Connecting to mirrors.slackware.com
> (mirrors.slackware.com)|207.223.116.213|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2016-08-09 00:55:43 ERROR 404: Not Found.
>
>
> fontforge:
> Would you like to continue processing the rest of the
> queue or would you like to abort?  If this failed
> package is a dependency of another package in the queue
> then it may not make sense to continue.
>
> (Y)es to continue, (N)o to abort, (R)etry the build?:


hi Fernando,

I think your SBo local repository is not up-to-date as the link to the
freetype tarball in the fontforge.info file has been updated a couple
of weeks ago...

Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] fontforge fails to compile

2016-08-09 Thread Fernando Lopez 
I can download fine manually from the site...


Processing fontforge

fontforge:
Found fontforge-20150824.tar.gz in /var/cache/sbopkg.
Found cidmaps.tgz in /var/cache/sbopkg.
fontforge not found in /var/cache/sbopkg.
--2016-08-09 00:55:43--
http://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.6.3.tar.xz
Resolving mirrors.slackware.com (mirrors.slackware.com)... 207.223.116.213
Connecting to mirrors.slackware.com
(mirrors.slackware.com)|207.223.116.213|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2016-08-09 00:55:43 ERROR 404: Not Found.


fontforge:
Would you like to continue processing the rest of the
queue or would you like to abort?  If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

(Y)es to continue, (N)o to abort, (R)etry the build?:
-- 


Regards,
Fernando Lopez Jr.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge

2015-07-19 Thread korgman 

On 19/07/2015 02:54 πμ, Steve Wood wrote:

Is anyone else having issues with downloading the fontforge tarball
from SBo? It's making it hard to install lilypond.


README says: remove old version before building. Maybe is this?

But here cidmaps.tgz is missing and fontforge is down here for maintenance.

I  am using old version of lilypond (for personal reasons: lazy to upgrade.)
lilypond-2.16.2-i686-2_SBo

with fontforge 2012 version (from slackware-14.0 repo!) I don't remember the 
reason I was sticking with this. Probably, again lazy, but maybe not :p
14.0/fontforge-20120731_b-i686-1_SBo.txz

Grab it from here if you want it
http://clavisound.no-ip.info/tgz/14.0/fontforge-20120731_b-i686-1_SBo.txz

One version behind.
potrace-1.11-i686-1_SBo vs 1.12
t1utils-1.38-i686-1_SBo vs 1.39

Current versions
guile1.8-1.8.8-i686-1_SBo
mftrace-1.2.18-i686-1_SBo


I'll try to compile it from the git source.


In those cases I try to mix the repos. I am using old version from SBo (if 14.1 
i go 14.0)

It's easy to find the mix either with update in sbopkg or with grep LOCATION 
/var/log/packages/* if you are using a folder with version number.
PACKAGE LOCATION: 
/home/myhome/SlackBuilds/14.0/fontforge-20120731_b-i686-1_SBo.txz
 

Steve


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

[Slackbuilds-users] fontforge

2015-07-18 Thread Steve Wood 
Is anyone else having issues with downloading the fontforge tarball
from SBo? It's making it hard to install lilypond.

I'll try to compile it from the git source.

Steve


-- 
Steve Wood
email: st...@woodathon.com
xmpp: stevel...@hot-chilli.jabber.net
phone: 203.841.9792
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Re: [Slackbuilds-users] fontforge for 12.2 still looking for freetype from 12.1

2008-12-15 Thread Robby Workman 
On Thu, 11 Dec 2008 19:33:20 +0100
Thomas Morper thomdi...@aktiivi.ath.cx wrote:

 Just a trivial bug:
 
 The fontforge buildscript from the 12.2 tree still tries to include
 the older freetype version 2.3.5 from Slackware 12.1


I've got this one queued up with a version bump for when we open the
submission form back up.  For now, I don't have time to test whether
that version of fontforge will build with freetype-2.3.7 (though I
suspect it will), so I don't want to update the build script and
possibly introduce a new problem.

-RW


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/