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

[sborg63]

On Wed, 03 Oct 2018 18:19:57 +0000

Date: Wed, 3 Oct 2018 11:19:54 -0700 (PDT)
Subject: [Slackbuilds-users] Fontforge build error
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-***@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 sborg63
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.

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

Don't see anything applicable.

Post by sborg63
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-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Matteo Bernardini]

Il giorno mer 3 ott 2018 alle ore 21:58 Rich Shepard

Post by Rich Shepard

Post by sborg63
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.

Post by sborg63
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-***@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]

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-***@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]

  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

[Matteo Bernardini]

Il giorno mer 3 ott 2018 alle ore 22:17 Willy Sudiarto Raharjo

Post by Willy Sudiarto Raharjo

Post by Rich Shepard
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-***@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]

<snipped>

Thank you, Matteo,

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 Willy Sudiarto Raharjo
Non Multilibs is a pure 64-bit system

Okay.

Thanks,

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 Wednesday 3 October 2018 13:16,

Post by Rich Shepard

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
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[David Woodfall]

On Wednesday 3 October 2018 12:58,

Post by Rich Shepard

Post by sborg63
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.

Post by sborg63
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

Post by Rich Shepard

Post by sborg63
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
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[Rich Shepard]

Post by David Woodfall
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-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[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

[Rich Shepard]

Post by Daniel Prosser
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.

Post by Daniel Prosser
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-***@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]

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

[David Woodfall]

On Wednesday 3 October 2018 14:03,

Post by Rich Shepard

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
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[David Woodfall]

On Thursday 4 October 2018 23:54,

Post by David Woodfall
On Wednesday 3 October 2018 14:03,

Post by Rich Shepard

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
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.

Post by David Woodfall
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
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[Rich Shepard]

Post by David Woodfall
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
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-***@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 Friday 5 October 2018 07:41,

Post by Rich Shepard

Post by David Woodfall
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
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.

Post by Rich Shepard
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.

Post by Rich Shepard
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.

Post by Rich Shepard
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
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[Rich Shepard]

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-***@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 Friday 5 October 2018 08:24,

Post by Rich Shepard

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.

Post by Rich Shepard

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
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
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[David Woodfall]

On Friday 5 October 2018 08:24,

Post by Rich Shepard

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.

Post by Rich Shepard

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
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
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[Rich Shepard]

Post by David Woodfall

Post by Rich Shepard
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-***@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 Friday 5 October 2018 09:27,

Post by Rich Shepard

Post by David Woodfall

Post by Rich Shepard
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.

Post by Rich Shepard
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
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
(____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'

[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

Post by David Woodfall

  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-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.or

[Arnaud]

Post by 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

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 waaaay 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.

[Rich Shepard]

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

Arnaud,

Yesterday I ordered a hard drive for an unused, 7-year-old desktop system.
I'll install 14.2 on it (including patches) and start installing SBo
packages. If I need to hold this new box until 15.0 comes out, so be it.

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 Didier Spaier
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.

Post by Didier Spaier
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-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Didier Spaier]

  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-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbu

[Rich Shepard]

Post by David Woodfall
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-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/