[SOLVED] some 14.2 packages in SBo fail to build (autoconf)

metageek · 07-03-2016, 05:20 PM

I'm building a series of packages that I depend on from SBo, but a couple failed with the same error that is related to autoconf. I'm building on an upgraded 14.2 (from 14.1) where I followed all instructions of UPGRADE.TXT.

faac fails with:

Code:

aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
/usr/share/aclocal/autotrace.m4:7: warning: underquoted definition of AM_PATH_AUTOTRACE
/usr/share/aclocal/autotrace.m4:7:   run info Automake 'Extending aclocal'
/usr/share/aclocal/autotrace.m4:7:   or see http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
sh: line 1:  1041 Done                    echo 'm4_define([m4_require_silent_probe], [-])'
      1042 Segmentation fault      | autom4te --language Autoconf-without-aclocal-m4 - /usr/share/a

and later:

Code:

aclocal: error: echo failed with exit status: 139

ming also fails in a similar way:

Code:

autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal --force -I macros
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
/usr/share/aclocal/autotrace.m4:7: warning: underquoted definition of AM_PATH_AUTOTRACE
/usr/share/aclocal/autotrace.m4:7:   run info Automake 'Extending aclocal'
/usr/share/aclocal/autotrace.m4:7:   or see http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
sh: line 1:  3192 Done                    echo 'm4_define([m4_require_silent_probe], [-])'
      3193 Segmentation fault      | /usr/bin/autom4te --language Autoconf-without-aclocal-m4 - /usr/share/aclocal-1.15/internal/ac-config-macro-dirs.m4

and later

Code:

aclocal: error: echo failed with exit status: 139
autoreconf: aclocal failed with exit status: 139

these are the versions of the automake tools in my system:
autoconf (GNU Autoconf) 2.69
autoreconf (GNU Autoconf) 2.69
automake (GNU automake) 1.15
m4 (GNU M4) 1.4.17

Any ideas of what could be wrong and how to fix it?

Richard Cranium · 07-03-2016, 05:32 PM

How did you do the upgrade?

metageek · 07-03-2016, 05:56 PM

as I said, I followed UPGRADE.TXT included in 14.2.

55020 · 07-03-2016, 06:14 PM

The segfault is the significant thing here. You can investigate it like any other segfault: type 'ulimit -c unlimited' before you run the SlackBuild, then after autom4te dumps core type 'gdb /usr/bin/autom4te core', then type 'backtrace' and see what was happening when it died.

Wild guess: something may be wrong with perl on your system: maybe cpan modules or SBo perl packages you installed under 14.1 and haven't rebuilt yet. Remove any of that stuff and double-check that Slackware's main perl package is properly installed and up to date.

Richard Cranium · 07-03-2016, 06:24 PM

Quote:

Originally Posted by metageek

as I said, I followed UPGRADE.TXT included in 14.2.

Oh yeah, you did say that. I thought that you might have used slackpkg to do it.

Sorry for the noise.

metageek · 07-03-2016, 06:44 PM

Quote:

Originally Posted by 55020

The segfault is the significant thing here. You can investigate it like any other segfault: type 'ulimit -c unlimited' before you run the SlackBuild, then after autom4te dumps core type 'gdb /usr/bin/autom4te core', then type 'backtrace' and see what was happening when it died.

Wild guess: something may be wrong with perl on your system: maybe cpan modules or SBo perl packages you installed under 14.1 and haven't rebuilt yet. Remove any of that stuff and double-check that Slackware's main perl package is properly installed and up to date.

Ok, will investigate this; several PERL packages had not yet been upgraded, so will try doing them first.

bassmadrigal · 07-03-2016, 06:54 PM

Might be beneficial to set up slackpkg and then run slackpkg clean-system to see what packages you have installed that are not part of Slackware. It might give you a better starting point on what to investigate.

NOTE: Running that won't automatically erase those programs. It will just provide you a prompt listing them all and allowing you to select/deselect them.

metageek · 07-03-2016, 07:09 PM

55020: you were on the right track there. I removed all the perl library packages that were in the system and now the segfault disappeared and the packages build properly. It was easier to remove all packages rather than trying to identify the culprit, so I am not sure which one it was...

Of course, will then rebuild those packages again as they will be needed dependencies of other things. (I am building perl- packages from SBo, but wondering if I shouldn't just be using CPAN instead as that would likely be easier...)

I'm marking this problem as solved.

Richard Cranium · 07-03-2016, 08:14 PM

There's a cpan2tgz package that creates packages for you.