LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-30-2016, 05:47 PM   #1
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Really odd problem: texinfo utilities segfault on current


From other thread:

texinfo-6.3 segfaults on -current.

Specifically, the two utilities which segfault are:
usr/bin/pod2texi
usr/bin/texi2any

Also, invoking /usr/bin/makeinfo, with or without any parameters (even /usr/bin/makeinfo --version) segfaults.

The other utilities installed by texinfo appear to run fine.

I run Slackware64-current, stock system, with some SBos and alienbob's Plasma packages.

I cannot even rebuild texinfo because the SlackBuild from the standard slack64 distribution also reports a segfault with texi2any.

I tried reinstalling texinfo, tetex, and even perl, to no avail.

I wouldn't be much concerned with this issue were it not for the fact that I need to use a good LaTeX distribution. Right now, SBo's texlive packages (inspired by franzen's work) are a good option but I cannot compile the new packages because of these segfaults.

I'd be grateful for any info or hints on how to overcome this issue.

Last edited by sombragris; 10-30-2016 at 05:49 PM.
 
Old 10-30-2016, 10:15 PM   #2
xode
Member
 
Registered: Aug 2003
Distribution: Mandrake 9.0; FC4; FC8; SUSE 10.3; SUSE 12.1; SUSE 13.2
Posts: 638
Blog Entries: 1

Rep: Reputation: 52
This is a completely wild guess on my part: are your installed glibc and glibc-devel libraries newer than your installed linux kernel? If not, then that could be causing your problem. I had a problem faintly similar to this with the vmmon kernel module for my VMware virtual machine crashing continuously at random, and updating my glibc libraries got rid of that problem.
 
Old 10-30-2016, 10:59 PM   #3
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Original Poster
Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
@xode:

Thanks. The answer is no; both kernel and glibc are all stock Slackware64-current.
 
Old 10-31-2016, 07:07 AM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Is this a fresh install of Slackware or did you upgrade (from either -current or 14.1)?
 
Old 10-31-2016, 07:48 AM   #5
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Original Poster
Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
@bassmadrigal: This was always a -current box, even from installation. I installed it on August 2015, i.e., in pre-14.2 days. I applied the relevant upgrades and updates as they were released.
 
Old 10-31-2016, 08:07 AM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Have you done an ldd on makeinfo to see if you might be missing (or referencing incorrect) libraries?
 
1 members found this post helpful.
Old 10-31-2016, 11:33 AM   #7
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Original Poster
Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
@bassmadrigal look at this:

Code:
[eduardo:~/bin]$ ldd /usr/bin/makeinfo
        not a dynamic executable
 
Old 10-31-2016, 12:05 PM   #8
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
That's what I get for checking my 14.1 install instead of my 14.2 I then went to my 14.2 install to do further checking. Using file /usr/bin/makeinfo shows that this is now a symlink to /usr/bin/texi2any, and using file on that shows it is a perl script. Since a perl script is causing your problems, it sounds like you have some old incompatible 3rd-party perl modules laying around (you probably started with perl 5.18.x and now 14.2 and -current have perl 5.22.x).

Unfortunately, I am not well-versed in perl and I don't know what you'd need to do to remove those modules if they weren't installed as Slackware packages. If all the modules were installed into /usr/local/lib{64}/perl5, you could simply (re)move that directory. You would also want to go through your Slackware packages to remove any older perl-based packages and/or rebuild them.
 
1 members found this post helpful.
Old 10-31-2016, 12:09 PM   #9
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Original Poster
Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Quote:
Originally Posted by bassmadrigal View Post
That's what I get for checking my 14.1 install instead of my 14.2 I then went to my 14.2 install to do further checking. Using file /usr/bin/makeinfo shows that this is now a symlink to /usr/bin/texi2any, and using file on that shows it is a perl script. Since a perl script is causing your problems, it sounds like you have some old incompatible 3rd-party perl modules laying around (you probably started with perl 5.18.x and now 14.2 and -current have perl 5.22.x).

Unfortunately, I am not well-versed in perl and I don't know what you'd need to do to remove those modules if they weren't installed as Slackware packages. If all the modules were installed into /usr/local/lib{64}/perl5, you could simply (re)move that directory. You would also want to go through your Slackware packages to remove any older perl-based packages and/or rebuild them.
Oh well. That might be what's causing the problem. Typing "ls /var/log/packages | grep perl" shows about 40 packages, of which about 35 are from SBo. Time to hunt that bug...
Thanks for the pointer!
 
Old 10-31-2016, 12:21 PM   #10
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
If you want to rebuild all of those, just output the names of those programs to a file and use it as a queue file for sbopkg (or possibly your favorite SBo package builder). I'd work out a quick one-liner for you, but it isn't easy to do remotely on my phone...
 
Old 10-31-2016, 12:36 PM   #11
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Original Poster
Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Quote:
Originally Posted by bassmadrigal View Post
If you want to rebuild all of those, just output the names of those programs to a file and use it as a queue file for sbopkg (or possibly your favorite SBo package builder). I'd work out a quick one-liner for you, but it isn't easy to do remotely on my phone...
Thanks but I already got into trouble.

For example, I have a perl package known as perl-CPAN-Meta installed. This was a SBo package from 14.1 era:

https://slackbuilds.org/repository/1...erl-CPAN-Meta/

The last time it was mentioned on a ChangeLog was this:

https://lists.slackbuilds.org/piperm...ne/014406.html

If I installed it was because it was a dependency from another package. Now, it's gone from the 14.2 repository. I have no idea of which package replaces it, and I don't know when it got removed; there is no notice at all in the ChangeLog.
 
Old 10-31-2016, 12:38 PM   #12
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Original Poster
Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Anyway, this is my list of perl packages from SBo:

Code:
perl-Audio-FLAC-Header-2.4-x86_64-1_SBo
perl-CPAN-Meta-2.150005-x86_64-1_SBo
perl-CPAN-Meta-YAML-0.018-x86_64-1_SBo
perl-Curses-1.28-x86_64-1_SBo
perl-Curses-UI-0.9609-x86_64-1_SBo
perl-File-Which-1.09-x86_64-1_SBo
perl-IPC-Run-0.94-x86_64-1_SBo
perl-IPC-Run3-0.048-x86_64-1_SBo
perl-IPC-System-Simple-1.25-noarch-1_SBo
perl-MP3-Info-1.24-x86_64-1_SBo
perl-Module-Build-0.4220-x86_64-1_SBo
perl-Ogg-Vorbis-Header-PurePerl-1.0-x86_64-1_SBo
perl-PAR-Dist-0.49-x86_64-1_SBo
perl-Parse-CPAN-Meta-1.4417-x86_64-1_SBo
perl-Probe-Perl-0.03-x86_64-1_SBo
perl-TermReadKey-2.33-x86_64-0_SBo
perl-Test-Script-1.07-x86_64-1_SBo
perl-cairo-1.105-x86_64-1_SBo
perl-extutils-depends-0.404-x86_64-1_SBo
perl-extutils-makemaker-7.24-x86_64-1_SBo
perl-extutils-pkgconfig-1.15-x86_64-1_SBo
perl-file-basedir-0.07-x86_64-1_SBo
perl-file-desktopentry-0.22-x86_64-1_SBo
perl-file-mimeinfo-0.27-x86_64-1_SBo
perl-glib-1.307-x86_64-1_SBo
perl-gtk2-1.2495-x86_64-1_SBo
perl-libintl-1.23-x86_64-1_SBo
perl-pango-1.227-x86_64-1_SBo
 
Old 10-31-2016, 12:57 PM   #13
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Original Poster
Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
@bassmadrigal: SOLVED!

Upon rebuilding perl-libintl-1.23-x86_64-1_SBo, all texlive utilities, including texi2any and makeinfo, worked like a charm.

I'm very grateful for your help.

Marking this thread as solved!!
 
Old 10-31-2016, 01:05 PM   #14
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by sombragris View Post
Thanks but I already got into trouble.

For example, I have a perl package known as perl-CPAN-Meta installed. This was a SBo package from 14.1 era:

https://slackbuilds.org/repository/1...erl-CPAN-Meta/

The last time it was mentioned on a ChangeLog was this:

https://lists.slackbuilds.org/piperm...ne/014406.html

If I installed it was because it was a dependency from another package. Now, it's gone from the 14.2 repository. I have no idea of which package replaces it, and I don't know when it got removed; there is no notice at all in the ChangeLog.
I just did a search on my 14.1 SBo repo, and the only package that requires perl-CPAN-Meta is perl-Module-Build. According to SBo, this no longer has that dependency on 14.2.

As to your list, to create just package names without version numbers, if my old script on my system is semi-accurate, you should be able to create that list using something like this:

Code:
ls -la /var/log/packages/ | grep perl | grep SBo | rev | cut -d '-' -f4- | rev > /var/lib/sbopkg/queues/rebuild-perl.sqf
You'll also want to remove all those packages before you rebuild them, just in case any try and build off the old version.

Code:
while read i; do removepkg $i; done </var/lib/sbopkg/queues/rebuild-perl.sqf
Then you can just run sbopkg -i rebuild-perl and select the queue option. However, this might build them slightly out of order if some depend on another and could cause failures, so it might be better to add the files to a REQUIRES line on a .info file, then use sqg to create a proper queue for them.

EDIT: Guess you beat me to it. Congrats on solving it!
 
Old 10-31-2016, 01:12 PM   #15
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 855

Original Poster
Rep: Reputation: 383Reputation: 383Reputation: 383Reputation: 383
Quote:
Originally Posted by bassmadrigal View Post

Then you can just run sbopkg -i rebuild-perl and select the queue option. However, this might build them slightly out of order if some depend on another and could cause failures, so it might be better to add the files to a REQUIRES line on a .info file, then use sqg to create a proper queue for them.

EDIT: Guess you beat me to it. Congrats on solving it!
Thanks @bassmadrigal. I'll take it into account for a next time. Anyway, it's odd that there was no proper notice of removal for several of those perl modules in the SBo repository.
 
  


Reply

Tags
current, segfault, texinfo, texlive



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Error message with sound utilities in last Slackware current philanc Slackware 5 05-16-2016 05:41 AM
Segfault with E17 on Slackware --Current frankbell Slackware 5 03-26-2013 07:19 PM
Odd wireless problem with Slackware-current on Latitude 110L easuter Slackware 1 12-07-2009 04:44 AM
Odd problem with xorg radeon drivers on Slackware current Eternal_Newbie Slackware 1 11-23-2007 11:17 AM
Xterminal + current GTK = segfault crxssi Linux - Software 3 01-28-2006 06:58 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:42 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration