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
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
> 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
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
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
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
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
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
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
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.
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
> >
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
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,
> >
> >
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
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
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
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 -
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
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
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
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.
>
> >
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
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
___
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:
>
>
> 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
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
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
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
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;
29 matches
Mail list logo
