[Slackbuilds-users] Another build error: glabels

[Rich Shepard]

I would really like to understand why I'm having difficulties building SBo
packages on my new desktop. It's running 14-2/x86_64, has an
8-core/16-thread CPU, 32G memory, and AlienBOB's multilibs for 14.2.

This is the glabels error:

lgl-db.c:134:1: note: in expansion of macro 'G_DEFINE_TYPE'
G_DEFINE_TYPE (lglDbModel, lgl_db_model, G_TYPE_OBJECT);
^
In file included from /usr/include/glib-2.0/glib/gthread.h:32:0,
from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
from /usr/include/glib-2.0/glib.h:32,
from lgl-db.h:24,
from lgl-db.c:23:
/usr/include/glib-2.0/glib/gatomic.h:122:5: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
(gpointer) __atomic_load_4 ((atomic), __ATOMIC_SEQ_CST); \
^
/usr/include/glib-2.0/glib/gthread.h:251:7: note: in expansion of macro 'g_atomic_pointer_get'
(!g_atomic_pointer_get (location) && \
^
/usr/include/glib-2.0/gobject/gtype.h:1958:7: note: in expansion of macro 'g_once_init_enter'
if (g_once_init_enter (&g_define_type_id__volatile)) \
^
/usr/include/glib-2.0/gobject/gtype.h:1729:60: note: in expansion of macro '_G_DEFINE_TYPE_EXTENDED_BEGIN'
#define G_DEFINE_TYPE_EXTENDED(TN, t_n, T_P, _f_, _C_) _G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n,
^
/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, {})
^
lgl-db.c:134:1: note: in expansion of macro 'G_DEFINE_TYPE'
G_DEFINE_TYPE (lglDbModel, lgl_db_model, 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 lgl-db.h:24,
from lgl-db.c:23:
/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 (&g_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, {})
^
lgl-db.c:134:1: note: in expansion of macro 'G_DEFINE_TYPE'
G_DEFINE_TYPE (lglDbModel, lgl_db_model, G_TYPE_OBJECT);
^
Makefile:583: recipe for target 'lgl-db.lo' failed
make[2]: *** [lgl-db.lo] Error 1
make[2]: Leaving directory '/tmp/SBo/glabels-3.4.0/libglabels'
Makefile:509: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/glabels-3.4.0'
Makefile:439: recipe for target 'all' failed
make: *** [all] Error 2

All help welcome!

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

[Willy Sudiarto Raharjo]

  I would really like to understand why I'm having difficulties building
SBo
packages on my new desktop. It's running 14-2/x86_64, has an
8-core/16-thread CPU, 32G memory, and AlienBOB's multilibs for 14.2.

glabels works fine here on pure x86_64

SUMMARY LOG
Using the SBo repository for Slackware 14.2
Queue Process: Download and build

glabels:
MD5SUM check for glabels-3.4.0.tar.xz ... OK
Building package glabels-3.4.0-x86_64-1_SBo.tgz ... OK

[Rich Shepard]

Post by Willy Sudiarto Raharjo
glabels works fine here on pure x86_64

Willy,

I need the multilibs library for some applications I regularly use. I
think that I need to upgrade to -current, upgrade Eric's multilibs, and try
again.

Regards,

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

[Willy Sudiarto Raharjo]

  I need the multilibs library for some applications I regularly use. I
think that I need to upgrade to -current, upgrade Eric's multilibs, and try
again.

I'm not sure whether upgrading to -current will solve the issue, but
yeah, you can try it first on a vm

[414N]

Hi Rich,

I've got no problems too building glabels on a Slackware64 14.2 system
with Eric's multilib packages installed.

The compilation process outputs a lot of warnings, but none of them
blocks the build.

What compiler is picked up by the configure script? Could it be LLVM?

You can see it in the summary after all the configure "checking for ..."
messages.

If it is gcc, what version are you using? Is it 
"gcc-5.5.0_multilib-x86_64-1alien"?


Alan Alberghini

SBo clone: GitHub <https://github.com/414n/slackbuilds.org>

Post by Rich Shepard

Post by Willy Sudiarto Raharjo
glabels works fine here on pure x86_64

Willy,
  I need the multilibs library for some applications I regularly use. I
think that I need to upgrade to -current, upgrade Eric's multilibs, and try
again.
Regards,
Rich
_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Rich Shepard]

Post by 414N
I've got no problems too building glabels on a Slackware64 14.2 system
with Eric's multilib packages installed.
If it is gcc, what version are you using? Is it 
"gcc-5.5.0_multilib-x86_64-1alien"?

Alan,

The issue seems to be the newness of the hardware, most likely the CPU;
perhaps also the motherboard. Packages that have built with no issues on the
three 64-bit portables here that are older will not build on this new
system.

A couple of examples. OpenBLAS (which I need for GRASS, the spatial
analysis tool) would not build until I added a line to the build script
specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of
high-performance CPUs that were first released last year. Adding that target
allowed OpenBLAS to build.

AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced
some failure issues just running. He fixed that by uupgrading the 14.2's
kernel to one in the 4.14 series.

In order to build GnuCash I need goffice/goffice8, and neither will build
on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and
quickly.) All this seems to point to support for a CPU released well after
the basic (and fully patched) 14.2 was released.

Unless Those Who Know tell me not to upgrade to -current, just upgrade the
kernel (and it's been more than 15 years since I built a custom kernel from
kernel.org source; not since 2003 when I switched from Red Hat 7.4 to
Slackware-8.0) I'll do the upgrade this coming weekend. After learning how
best to do this.

Thanks,

Rich

[Didier Spaier]

Do what you want, but you probably will spare yourself a lot of issues
(and many among us a lot of support provided for free to no avail)
trying first to just install a genuine (not multilib) Slackware 14.2
and build these packages. Then if you encounter issues due to a too old
kernel, you will be able to install (not build) a newer kernel. IIRC you
can just install a kernel for Slackware-current in Slackware 14.2, if I
am wrong please someone corrects me.

I am not convinced that you be well prepared to run neither -current nor
multilib, finding yourself how to sort the issues that can arise. You
would need to first make a lot of thorough reading, like e.g.
http://docs.slackware.com/slackware:multilib
Thorough reading means understand not only the "how" but also the "why"
of what you read instead of just apply blindly a recipe.

Best,

Didier

PS If you need to run some 32-bit applications, it's usually possible
to find other ones providing very similar features, else it's much easier
to fire up a virtual machine with a 32-bit Slackware than to maintain a
multilib system. And with 32G of RAM running virtual machines is
not an issue at all

Post by 414N
I've got no problems too building glabels on a Slackware64 14.2 system
with Eric's multilib packages installed.
If it is gcc, what version are you using? Is it 
"gcc-5.5.0_multilib-x86_64-1alien"?

Alan,
  The issue seems to be the newness of the hardware, most likely the CPU;
perhaps also the motherboard. Packages that have built with no issues on the
three 64-bit portables here that are older will not build on this new
system.
  A couple of examples. OpenBLAS (which I need for GRASS, the spatial
analysis tool) would not build until I added a line to the build script
specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of
high-performance CPUs that were first released last year. Adding that target
allowed OpenBLAS to build.
  AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced
some failure issues just running. He fixed that by uupgrading the 14.2's
kernel to one in the 4.14 series.
  In order to build GnuCash I need goffice/goffice8, and neither will build
on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and
quickly.) All this seems to point to support for a CPU released well after
the basic (and fully patched) 14.2 was released.
  Unless Those Who Know tell me not to upgrade to -current, just upgrade the
kernel (and it's been more than 15 years since I built a custom kernel from
kernel.org source; not since 2003 when I switched from Red Hat 7.4 to
Slackware-8.0) I'll do the upgrade this coming weekend. After learning how
best to do this.
Thanks,
Rich
_______________________________________________
SlackBuilds-users mailing list
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

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

[Rich Shepard]

Post by Didier Spaier
Do what you want, but you probably will spare yourself a lot of issues
(and many among us a lot of support provided for free to no avail)
trying first to just install a genuine (not multilib) Slackware 14.2
and build these packages. Then if you encounter issues due to a too old
kernel, you will be able to install (not build) a newer kernel. IIRC you
can just install a kernel for Slackware-current in Slackware 14.2, if I
am wrong please someone corrects me.

Didier,

I hit those build issues over the past week, well before I installed the
multilib paackages yesterday. I installed the latter only to enable running
adobe-reader (and, perhaps, jpilot), taking a break from the more important
packages that wouldn't build.

The BIOS version is no older than a year ago; I'd need to check it again
but when installed I recall seeing the version data as earlier this year or
late last autumn.

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

[David Spencer]

  The issue seems to be the newness of the hardware, most likely the CPU;

That is true *only* with your OpenBLAS build. You have found a really
good solution, thank you, I'm sure this will be helpful for other people.

  AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced
some failure issues just running. He fixed that by uupgrading the 14.2's
kernel to one in the 4.14 series.

The failure issues with Ryzen CPUs were random segfaults and lockups,
*not* repeatable build failures when building specific packages.

The solutions for those random segfaults and lockups are
- upgrade your motherboard's bios
- in your bios, disable C6 power saving
see https://www.google.com/search?q=ryzen+c6+bug
- use a newer kernel

But that *won't* fix your glabels and Fontforge build problems.

Your glabels and Fontforge problems seem to have a single common cause

  In order to build GnuCash I need goffice/goffice8, and neither will build
on this new box.

-- and probably the same with goffice too, although you haven't shared a
build log yet.

It looks to me like maybe a problem with your glib2 package.
What version of glib2 do you have installed?
Have you upgraded some Gnome libraries?
Is your glib2 compat32 package the same version as your main glib2 package?

I'm wondering if, for example, you might have installed the -current
version of multilib onto your 14.2 Slackware 64 system.

Maybe it would be worth doing 'removepkg glib2-compat32' and then trying
those builds again.

Unless Those Who Know tell me not to upgrade to -current

Do not upgrade to -current. Upgrading to -current is the quickest known
way of creating a lot of build failures that nobody has ever seen before
and that nobody can fix.

Cheers
-D.

[Willy Sudiarto Raharjo]

  The issue seems to be the newness of the hardware, most likely the CPU;
perhaps also the motherboard. Packages that have built with no issues on the
three 64-bit portables here that are older will not build on this new
system.
  A couple of examples. OpenBLAS (which I need for GRASS, the spatial
analysis tool) would not build until I added a line to the build script
specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of
high-performance CPUs that were first released last year. Adding that target
allowed OpenBLAS to build.
  AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced
some failure issues just running. He fixed that by uupgrading the 14.2's
kernel to one in the 4.14 series.
  In order to build GnuCash I need goffice/goffice8, and neither will build
on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and
quickly.) All this seems to point to support for a CPU released well after
the basic (and fully patched) 14.2 was released.
  Unless Those Who Know tell me not to upgrade to -current, just upgrade
the
kernel (and it's been more than 15 years since I built a custom kernel from
kernel.org source; not since 2003 when I switched from Red Hat 7.4 to
Slackware-8.0) I'll do the upgrade this coming weekend. After learning how
best to do this.

Hi Rich

I have had the same issue on my main desktop which is Ryzen-based CPU.
The issue was solved by upgrading the firmware for the motherboard to
the latest version and now i have no more issue with the Ryzen.

[Rich Shepard]

I have had the same issue on my main desktop which is Ryzen-based CPU. The
issue was solved by upgrading the firmware for the motherboard to the
latest version and now i have no more issue with the Ryzen.

Thanks, Willy. The firmware is less than a year old, but I'll look for the
most current and upgrade to it.

Best regards,

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

[Rich Shepard]

I have had the same issue on my main desktop which is Ryzen-based CPU. The
issue was solved by upgrading the firmware for the motherboard to the
latest version and now i have no more issue with the Ryzen.

Willy,

I just downloaded the BIOS firmware from 2018-09-21. That's certainly
newer than the installed version. Will upgrade this morning and try building
some packages. I have a spatial interpolation model to run first so it will
be a bit before I get to the hardware issues.

Thanks again for the pointer,

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

[Rich Shepard]

Post by Rich Shepard
I just downloaded the BIOS firmware from 2018-09-21. That's certainly
newer than the installed version. Will upgrade this morning and try
building some packages. I have a spatial interpolation model to run first
so it will be a bit before I get to the hardware issues.

Status update.

The original BIOS firmware on the motherboard (an Asus Prime X470-Pro) was
version 4018 dated 2018-07-12. I just upgraded it to version 4024 dated
2018-09-18.

When I tried building the glabels package it quit when it didn't find a
make target for a required file:

lgl-db.c:134:1: note: in expansion of macro 'G_DEFINE_TYPE'
G_DEFINE_TYPE (lglDbModel, lgl_db_model, G_TYPE_OBJECT);
^
Makefile:583: recipe for target 'lgl-db.lo' failed
make[2]: *** [lgl-db.lo] Error 1
make[2]: Leaving directory '/tmp/SBo/glabels-3.4.0/libglabels'
Makefile:509: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/glabels-3.4.0'
Makefile:439: recipe for target 'all' failed
make: *** [all] Error 2

There are no specific dependencies for glabels, and this does look like a
resolveable hurdle and not a firmware issue. Of course, I may well be wrong
about this.

Regards,

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

[Rich Shepard]

Post by Rich Shepard
There are no specific dependencies for glabels, and this does look like a
resolveable hurdle and not a firmware issue. Of course, I may well be
wrong about this.

Well, the BIOS firmware is the latest release and still packages won't
build (e.g., wxPython-3.0.2.0; the same type of issues both before and after
installation of multilibs.)

I now know not to upgrade to -current. A kernel upgrade should not break
anything as far as I know.

Any other steps I should take?

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

[David Woodfall]

On Thursday 4 October 2018 05:50,

Post by Rich Shepard

Post by 414N
I've got no problems too building glabels on a Slackware64 14.2 system
with Eric's multilib packages installed.
If it is gcc, what version are you using? Is it 
"gcc-5.5.0_multilib-x86_64-1alien"?

Rich,

Sorry to reiterate this point, and I apologise if it seems obvious to
you, but just to be clear, I'm wondering how long ago you installed
the multilib packages and if you check for updates?

It's a good idea to do an rysnc of the multilib server from
time-to-time to check if there have been any updates.

Dave

Post by Rich Shepard
Alan,
The issue seems to be the newness of the hardware, most likely the CPU;
perhaps also the motherboard. Packages that have built with no issues on the
three 64-bit portables here that are older will not build on this new
system.
A couple of examples. OpenBLAS (which I need for GRASS, the spatial
analysis tool) would not build until I added a line to the build script
specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of
high-performance CPUs that were first released last year. Adding that target
allowed OpenBLAS to build.
AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced
some failure issues just running. He fixed that by uupgrading the 14.2's
kernel to one in the 4.14 series.
In order to build GnuCash I need goffice/goffice8, and neither will build
on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and
quickly.) All this seems to point to support for a CPU released well after
the basic (and fully patched) 14.2 was released.
Unless Those Who Know tell me not to upgrade to -current, just upgrade the
kernel (and it's been more than 15 years since I built a custom kernel from
kernel.org source; not since 2003 when I switched from Red Hat 7.4 to
Slackware-8.0) I'll do the upgrade this coming weekend. After learning how
best to do this.
Thanks,
Rich

--
Dave

Boston State House is the hub of the Solar System. You couldn't pry
that out of a Boston man if you had the tire of all creation
straightened out for a crowbar.
-- O. W. Holmes

.--. oo
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[Rich Shepard]

Sorry to reiterate this point, and I apologise if it seems obvious to you,
but just to be clear, I'm wondering how long ago you installed the
multilib packages and if you check for updates?

Dave,

Yesterday morning, Oct. 3rd, about 10:00 am PDT, using the lftp command
for the 14.2 builds.

I installed them to run adobe-reader, taking a break from trying to build
libraries and other packages for the past week-and-a-half and encountering
build errors.

Regards,

Rich

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

[Rich Shepard]

Post by Rich Shepard
I would really like to understand why I'm having difficulties building SBo
packages on my new desktop. It's running 14-2/x86_64, has an
8-core/16-thread CPU, 32G memory, and AlienBOB's multilibs for 14.2.

Fixed. Either the BIOS firmware of kernel upgrade cleared the blockage.

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