Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 04-18-2019, 03:13 AM   #16
Senior Member
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,754

Rep: Reputation: Disabled

it may be that you have a system that you have upgraded to current but you still have some packages either:

- installed from the shitty (IMHO never use that site full of freaking ads! it mixes packages from different repositories and this is the best way to bork installations);

- that you build on it before applying the updates of 19 april 2018, so that they still link to *.la files that aren't on the system anymore: have a look at the relevant part in the ChangeLog, especially the last lines that should hint you on a possible solution
Thu Apr 19 01:04:06 UTC 2018
Hi folks, and welcome to the third ever Slackware Mass Rebuild (and the
longest ChangeLog entry in project history). There were two primary
motivations for rebuilding everything in the main tree. The first was to
switch to the new C++ ABI. The second was to get rid of all the .la files
in the LD_LIBRARY_PATH. Really, having .la files installed has been mostly
obsolete since things began to use pkg-config instead, but it's not easy
to get rid of them unless you do it all at once. If you just take them out
of one package, any other packages containing .la files that refer to the
removed ones will be broken. We've removed a few here and there before
(and then handled any packages that had referred to them with a rebuild),
but it was time to finally remove all the ones in /lib{,64} and
/usr/lib{,64}. One of the reasons that this really needed to happen is that
many projects are starting to migrate to build systems other than autotools,
and those systems do not generate .la files. So if we didn't get rid of them
now, we might end up in a situation later on where they are being removed
by upstream and then we would have to chase down the dependency breakage and
recompile (possibly many) other packages. The .la files that are outside of
the LD_LIBRARY_PATH were not removed (and shouldn't be) - those ones are
often used by the lt_dlopen() function to load plugins and removing those
ones can break things. But those ones don't cause problems... they aren't
likely to try to infect .la files produced by other packages.
IMPORTANT NOTE: If you have any third party or other packages installed on
your system that don't come with Slackware, and those packages have installed
any .la files, it is very likely that they refer to some .la files which we
have just removed, and that trying to compile against these packages will no
longer work. Luckily, the solution is simple: remove them. This command will
remove any stale .la files from the LD_LIBRARY_PATH:
rm /{,usr/}lib{,64}/*.la
1 members found this post helpful.
Old 04-18-2019, 08:10 AM   #17
Senior Member
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,596

Rep: Reputation: Disabled
Originally Posted by slacknedo View Post
Ok, I tried to install octave without slibtool and i get
libtool:   error: cannot find the library '/usr/lib64/' or unhandled argument '/usr/lib64/
If i install the package libxcb-1.11.1-x86_64-1.txz for slackware 14.2 on my window manager crash.
I also without slibtool pass the options QT="4" to sbopkg but the result it's the same.
You probably have some stale .la files somewhere as ponce said and slibtool would not care about this issue, only libtool.

Originally Posted by ponce View Post
build fine for me too on slackware64-current (also with 23 jobs)
I just want to add the reason libtool doesn't have an issue with parallel builds while slibtool does is likely that slibtool is much faster, enough that it can expose race conditions which just happened to work with libtool.

SDL2 used to have an issue like this with their autotools build, but it was fixed upstream somewhat recently.
1 members found this post helpful.
Old 04-20-2019, 04:50 AM   #18
LQ Newbie
Registered: Apr 2019
Distribution: slackware
Posts: 6

Original Poster
Rep: Reputation: Disabled
Ok, i have done "rm /{,usr/}lib{,64}/*.la" and i reinstall all the package with slackpkg and recompile all the package of sbopkg.
But now i have fail on make check.
  CXXLD    src/octave-config
  CXXLD    libgui/qterminal/
  CXXLD    libgui/src/
  GEN      libinterp/dldfcn/__delaunayn__.oct
  GEN      libinterp/dldfcn/__eigs__.oct
  GEN      libinterp/dldfcn/__fltk_uigetfile__.oct
  GEN      libinterp/dldfcn/__glpk__.oct
  GEN      libinterp/dldfcn/__init_fltk__.oct
  GEN      libinterp/dldfcn/__init_gnuplot__.oct
  GEN      libinterp/dldfcn/__ode15__.oct
  GEN      libinterp/dldfcn/__voronoi__.oct
  GEN      libinterp/dldfcn/amd.oct
  GEN      libinterp/dldfcn/audiodevinfo.oct
  GEN      libinterp/dldfcn/audioread.oct
  GEN      libinterp/dldfcn/ccolamd.oct
  GEN      libinterp/dldfcn/chol.oct
  GEN      libinterp/dldfcn/colamd.oct
  GEN      libinterp/dldfcn/convhulln.oct
  GEN      libinterp/dldfcn/dmperm.oct
  GEN      libinterp/dldfcn/fftw.oct
  GEN      libinterp/dldfcn/gzip.oct
  GEN      libinterp/dldfcn/qr.oct
  GEN      libinterp/dldfcn/symbfact.oct
  GEN      libinterp/dldfcn/symrcm.oct
  GEN      libgui/graphics/__init_qt__.oct
  CXXLD    src/mkoctfile
  CXXLD    src/octave
  CXXLD    liboctave/
  CXXLD    libinterp/
  CXXLD    libgui/
  CXXLD    src/octave-cli
  GEN      src/octave-cli-5.1.0
  CXXLD    src/octave-gui
  GEN      src/octave-gui-5.1.0

Octave successfully built.  Now choose from the following:

   ./run-octave    - to run in place to test before installing
   make check      - to run the tests
   make install    - to install (PREFIX=/usr)

   HG ID for this build is "d05d6eebde10"

make[2]: Leaving directory '/tmp/SBo/octave-5.1.0'
make[1]: Leaving directory '/tmp/SBo/octave-5.1.0'
preserving existing HG-ID file
make  check-recursive
make[1]: Entering directory '/tmp/SBo/octave-5.1.0'
preserving existing HG-ID file
Making check in libgnu
make[2]: Entering directory '/tmp/SBo/octave-5.1.0/libgnu'
make  check-recursive
make[3]: Entering directory '/tmp/SBo/octave-5.1.0/libgnu'
make[4]: Entering directory '/tmp/SBo/octave-5.1.0/libgnu'
make[4]: Nothing to be done for 'check-am'.
make[4]: Leaving directory '/tmp/SBo/octave-5.1.0/libgnu'
make[3]: Leaving directory '/tmp/SBo/octave-5.1.0/libgnu'
make[2]: Leaving directory '/tmp/SBo/octave-5.1.0/libgnu'
make[2]: Entering directory '/tmp/SBo/octave-5.1.0'
preserving existing HG-ID file
  GEN      libinterp/DOCSTRINGS
  MAKEINFO doc/liboctave/
  TEXI2DVI doc/liboctave/liboctave.dvi
/usr/bin/texi2dvi: TeX neither supports -recorder nor outputs \openout lines in its log file
make[2]: *** [Makefile:31027: doc/liboctave/liboctave.dvi] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/tmp/SBo/octave-5.1.0'
make[1]: *** [Makefile:27055: check-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/octave-5.1.0'
make: *** [Makefile:27349: check] Error 2

Would you like to continue processing the rest of the
queue or would you like to abort?  If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
I have tex installed

> $ tex --version                                                                                                                                                            
TeX 3.14159265 (TeX Live 2018 on Slackware)
kpathsea version 6.3.0
Copyright 2018 D.E. Knuth.
There is NO warranty.  Redistribution of this software is
covered by the terms of both the TeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the TeX source.
Primary author of TeX: D.E. Knuth.
> $ texi2dvi --version                                                                                                                                                       
texi2dvi (GNU Texinfo 6.6)

Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

This with libtool, with slibtool have the same problem.

Last edited by slacknedo; 04-21-2019 at 08:12 AM.
Old 04-30-2019, 04:40 AM   #19
LQ Newbie
Registered: Apr 2019
Distribution: slackware
Posts: 6

Original Poster
Rep: Reputation: Disabled
I tried all your solution, but i still have this problem.
Sorry but i don't know how resolve.
Thank you in advance.
Old 04-30-2019, 08:45 AM   #20
Senior Member
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,596

Rep: Reputation: Disabled
For what its worth I have shared your issue with this slibtool developer and the F77 issue was fixed in slibtool (Not sure its pushed yet?), but hasn't had time to look at the remaining issues yet. Maybe later this week.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
I can not compile octave on Slackware 14 rasitabay Slackware 14 07-09-2013 12:29 PM
[SOLVED] Octave 3.4.2 gives compilation error on Slackware-current 64 Bindestreck Slackware 1 05-25-2012 11:26 AM
GNU Octave compile error and fix without recompile ivanp84 Slackware 2 02-12-2012 04:54 AM
Slackware 13 and Octave 3.2 slackuser998 Slackware 1 09-18-2009 08:26 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:45 AM.

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