LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 05-28-2016, 08:13 AM   #226
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915
current postgresql version 9.5.3


SBo guys --

Postgresql version 9.5.3 is available and builds and runs fine on current.

below are diffs for postgresql.info and postgresql.SlackBuild for postgresql version 9.5 vs version 9.5.3

I've not tested all the programs dependent on postgresql but I'll be building postgis RSN for a local app

# ./.get-SB-REQUIRES -Rv postgresql
Code:
#
# packages that require postgresql
#
  unicornscan
  PyGreSQL
  pgtcl-ng
  libqsqlpsql
  libpqxx
  php-pgsql
  cyphesis
  multicorn
  pgadmin3
  pgsanity
  perl-DBD-Pg
  postgis
  pdal
  pointcloud
  pd-psql
  psycopg2
Thanks again !

-- kjh

# diff -Naur postgresql/postgresql.info postgresql-9.5.3/postgresql.info
Code:
--- postgresql/postgresql.info  2016-05-28 04:46:38.779637543 -0500
+++ postgresql-9.5.3/postgresql.info    2016-05-28 05:40:25.843943577 -0500
@@ -1,8 +1,8 @@
 PRGNAM="postgresql"
-VERSION="9.5.0"
+VERSION="9.5.3"
 HOMEPAGE="http://www.postgresql.org"
-DOWNLOAD="http://ftp.postgresql.org/pub/source/v9.5.0/postgresql-9.5.0.tar.bz2"
-MD5SUM="e58fffe9359e311ead94490a06b7147c"
+DOWNLOAD="https://ftp.postgresql.org/pub/source/v9.5.3/postgresql-9.5.3.tar.bz2"
+MD5SUM="3f0c388566c688c82b01a0edf1e6b7a0"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
# diff -Naur postgresql/postgresql.SlackBuild postgresql-9.5.3/postgresql.SlackBuild
Code:
--- postgresql/postgresql.SlackBuild    2016-05-28 04:46:38.779637543 -0500
+++ postgresql-9.5.3/postgresql.SlackBuild      2016-05-28 05:44:04.694964331 -0500
@@ -28,7 +28,7 @@
 # Modified by the SlackBuilds.org Project
 
 PRGNAM=postgresql
-VERSION=${VERSION:-9.5.0}
+VERSION=${VERSION:-9.5.3}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
Old 05-30-2016, 09:28 AM   #227
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,460

Rep: Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087
Plank builds okay, but it installs net.launchpad.plank.gschema.xml in /usr/share/glib-2.0/schemas and doesn't run unless you do:

Code:
glib-compile-schemas /usr/share/glib-2.0/schemas
Maybe this should go in doinst.sh?

Last edited by montagdude; 05-30-2016 at 09:29 AM.
 
Old 05-30-2016, 10:07 AM   #228
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,963

Rep: Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224
Thanks, fixed in my branch already
 
Old 05-30-2016, 06:35 PM   #229
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,307
Blog Entries: 4

Rep: Reputation: Disabled
Community Challenge! Help fix the last few SlackBuilds for 14.2

For anybody not subscribed to the SBo Mailing List, I posted this yesterday. If you have a solution, you are very welcome to post patches into this thread. Thanks for looking!

--------------------------------------

At this time there are only a few packages that fail to build, and all
the git commiters are getting a bit tired, so we would like to
challenge the community to help fix the last few problems. Your
reward will be a nice Thank You in the git repo

Here are the first four ... if you can fix them, there will be some more later!


1. academic/Xyce
http://pastebin.com/nsMwxhgR

It looks like an underlinking error, but I can't see anything wrong
with the link. There is a new version 6.4 upstream, I have tried it,
but the same linking problem happens. Maybe its dep
libraries/trilinos is involved -- Guilherme (maintainer of both Xyce
and trilinos) downgraded trilinos soon after it was first added. I
can't find any bug reports. Most other distros don't have Xyce.

If you don't want to register to download the source, there is a copy
of Xyce-6.4 on SlackBuilds Direct Links (Xyce is GPL, so
redistributing it is perfectly legal )
https://sourceforge.net/projects/sla...ks/files/Xyce/


2. development/hhvm

Eugen Wissner has already fixed this


3. games/ember
http://pastebin.com/Ny5PChhm

The build was broken by the new version of sigc++. Upstream is quite
active but seems to have stopped tagging proper releases. I tried the
latest git, but it needs its deps also updating to compatible
versions.

https://github.com/worldforge/ember
and deps at https://github.com/worldforge


4. graphics/photivo
http://pastebin.com/v5Yt3SYV

This looks like an underlinking error, but the build fails for me only
on x86_64 ... on i586 it builds ok!
 
Old 05-30-2016, 06:41 PM   #230
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,963

Rep: Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224
Quote:
Originally Posted by kjhambrick View Post
SBo guys --
Postgresql version 9.5.3 is available and builds and runs fine on current.
Thanks for the suggestion
it has been updated in my branch
 
Old 05-30-2016, 08:59 PM   #231
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,963

Rep: Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224
Quote:
Originally Posted by 55020 View Post
4. graphics/photivo
http://pastebin.com/v5Yt3SYV

This looks like an underlinking error, but the build fails for me only
on x86_64 ... on i586 it builds ok!

Fixed by Thomas Morper
 
Old 05-31-2016, 01:55 AM   #232
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915
SBo team --

pgadmin3 has been updated to version 1.22.1 ...

Version 1.20.0 complains about postgresql version > 9.4.x but 1.22.1 is OK with pg version 9.5.3

The MD5SUM is 'fake' ( generated locally ).

I could not find one at the home page but there is a .sig file and the source file verified OK:

Code:
# gpg --verify ./pgadmin3-1.22.1.tar.gz.sig
gpg: assuming signed data in `./pgadmin3-1.22.1.tar.gz'
gpg: Signature made Mon Feb  8 04:36:36 2016 CST using RSA key ID 698F1519
gpg: Can't check signature: public key not found

# gpg --no-default-keyring --keyring vendors.gpg --keyserver pgp.mit.edu --recv-key 698F1519
gpg: keyring `/root/.gnupg/vendors.gpg' created
gpg: requesting key 698F1519 from hkp server pgp.mit.edu
gpg: key 698F1519: public key "Dave Page <[email protected]>" imported
gpg: public key of ultimately trusted key 40102233 not found
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

# gpg --verify --verbose --keyring vendors.gpg pgadmin3-1.22.1.tar.gz.sig
gpg: assuming signed data in `pgadmin3-1.22.1.tar.gz'
gpg: Signature made Mon Feb  8 04:36:36 2016 CST using RSA key ID 698F1519
gpg: using PGP trust model
gpg: Good signature from "Dave Page <[email protected]>"
gpg:                 aka "Dave Page <[email protected]>"
gpg:                 aka "Dave Page <[email protected]>"
gpg:                 aka "Dave Page <[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: E0C4 CEEB 826B 1FDA 4FB4  68E0 24AD FAAF 698F 1519
gpg: binary signature, digest algorithm SHA1
Thanks.

-- kjh


# diff -Naur pgadmin3 pgadmin3-1.22.1
Code:
diff -Naur pgadmin3/pgadmin3.SlackBuild pgadmin3-1.22.1/pgadmin3.SlackBuild
--- pgadmin3/pgadmin3.SlackBuild        2016-05-30 03:14:22.954681480 -0500
+++ pgadmin3-1.22.1/pgadmin3.SlackBuild 2016-05-31 01:04:34.511136478 -0500
@@ -6,7 +6,7 @@
 # Modified by Mario Preksavec <[email protected]>
 
 PRGNAM=pgadmin3
-VERSION=${VERSION:-1.20.0}
+VERSION=${VERSION:-1.22.1}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
diff -Naur pgadmin3/pgadmin3.info pgadmin3-1.22.1/pgadmin3.info
--- pgadmin3/pgadmin3.info      2016-05-30 03:14:22.954681480 -0500
+++ pgadmin3-1.22.1/pgadmin3.info       2016-05-31 01:17:06.482207790 -0500
@@ -1,8 +1,8 @@
 PRGNAM="pgadmin3"
-VERSION="1.20.0"
+VERSION="1.22.1"
 HOMEPAGE="http://www.pgadmin.org/"
-DOWNLOAD="http://ftp.postgresql.org/pub/pgadmin3/release/v1.20.0/src/pgadmin3-1.20.0.tar.gz"
-MD5SUM="3ca39fb598d0866eca90d30b85d5d5c4"
+DOWNLOAD="https://ftp.postgresql.org/pub/pgadmin3/release/v1.22.1/src/pgadmin3-1.22.1.tar.gz
+MD5SUM="fe56418e9efcd291f5c1f81708d005fe"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="postgresql wxPython"
 
Old 06-01-2016, 10:16 PM   #233
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,963

Rep: Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224Reputation: 1224
Updated in my branch, thanks
 
Old 06-02-2016, 05:56 PM   #234
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,882

Rep: Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591
Is there any thoughts for an (unoffical?) plan for python3 versions of programs already available on SBo as python2 versions?

I'm working on generating a SlackBuild for a new python3 based program, and many of the requirements are of programs already available as python2 versions. Some have an if/then statement to catch a python3 install and generate a dual python2/python3 package, but others don't have any such thing.

So far, for the ones that haven't included any catch for python3 within the SlackBuild, I've mirrored everything and changed the package name to python3-$PRGNAM, which seems like the best option (I did it previously with python3-PyYAML). (Once I complete everything, I'll email the maintainers of those python2 packages to see if they want to maintain the python3 versions, if not, I'll maintain them).

However, my question stems from the programs, like python-requests, that have the if/then statement in there to catch whether python3 is installed. If that package was originally built as a python2 only package, and then a person tries to build the dependencies of this program (including python3), the user or some automated tools would skip the already installed python2-only program since it was already installed.

Is there a recommended course of action on how to handle these packages? Should I just mention it in the README that recompilations for those programs that have the checks might be required if they were originally built as python2? Or should I just continue and mirror those programs as python3-$PKGNAM versions?

Last edited by bassmadrigal; 06-02-2016 at 06:00 PM. Reason: Linkified to SBo
 
Old 06-02-2016, 11:59 PM   #235
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,339

Rep: Reputation: 864Reputation: 864Reputation: 864Reputation: 864Reputation: 864Reputation: 864Reputation: 864
I can't help but wonder if we should split the "python" category into "python2" and "python3" - this would necessitate (or least imply the desire for) separate python2-$app and python3-$app builds, which would make many things better but also carries the possibility of making some things worse, I suppose...
 
3 members found this post helpful.
Old 06-03-2016, 12:16 AM   #236
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,460

Rep: Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087Reputation: 1087
This is kind of off-topic, but I made a SlackBuild for acpi_call. (I needed it for TLP to set custom battery charge thresholds on my Thinkpad.) I see on SlackBuilds.org that the submissions page is down currently in anticipation of 14.2. So should I just wait until that page comes up and then submit it, or would anyone like to test or look at it beforehand?
 
Old 06-03-2016, 08:01 AM   #237
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,882

Rep: Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591
Quote:
Originally Posted by rworkman View Post
I can't help but wonder if we should split the "python" category into "python2" and "python3" - this would necessitate (or least imply the desire for) separate python2-$app and python3-$app builds, which would make many things better but also carries the possibility of making some things worse, I suppose...
I really think that separate packages are the best way. It might not even be necessary to put the python2 label on pacakges until Slackware ships python3 as default, but I would think it makes sense to separate the two on SBo. This ensures that when people attempt to build things that require the python3 version, that they'll know for sure that they're good.

I don't think it'll really make things worse except maintainers would need to manage two packages, although, they should be simple to maintain considering there shouldn't be much of a difference between the two (at least that's been the case in my experience with providing python3 packages).

=============================================

On the program I was working on, it ended up with the REQUIRES line containing:

Code:
REQUIRES="python3 python3-SQLAlchemy python3-requests-toolbelt python-requests python3-setuptools python3-dateutil colorama python3-appdirs six"
Due to three of those requires having if/then checks for python3, I ended up with a note in the README that stated the below... just to make sure they were aware that if this is their first time installing python3, they may need to recompile them. The others are either reworkings of the python2 versions or freshly developed if they weren't previously on SBo. As I said earlier, prior to me submitting this to SBo (when submissions are open for 14.2), I'll contact the maintainers of any python2 versions I adapted to see if they want to manage the python3 versions. If not, I'll submit and maintain them.

Quote:
NOTE: colorama, six, and python-requests might require rebuilds if they were built prior to installing python3
I also put a note on the python3 versions of programs stating that they were fine to be installed alongside their python2 versions (in case users were wondering/worrying/curious).

Quote:
This builds the python3 version of SQLAlchemy. It is safe to install
this on a system that has SBo's SQLAlchemy (python2) package installed.
 
1 members found this post helpful.
Old 06-03-2016, 08:48 AM   #238
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,710

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by rworkman View Post
I can't help but wonder if we should split the "python" category into "python2" and "python3" - this would necessitate (or least imply the desire for) separate python2-$app and python3-$app builds, which would make many things better but also carries the possibility of making some things worse, I suppose...
I agree with the split: the way it is now might lead to confusion...

what might happen, I think, is that maintainers might not want to support their scripts for the two different versions of python, but let's hope someone else will step in their place if they won't.
 
3 members found this post helpful.
Old 06-03-2016, 09:18 AM   #239
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,882

Rep: Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591Reputation: 3591
A quick search of my local SBo repo shows that there's 46 SlackBuilds that have an if/then check for python3 (although, some developers may have used a different way to check for python3).

Code:
grep -R "if \$(python3 -c" */*/*.SlackBuild
 
1 members found this post helpful.
Old 06-07-2016, 08:44 AM   #240
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915Reputation: 915
scribus vs nxclient conflict + scribus version 1.4.6 is available

SBo Team --

Needed to add scribus to my Current64 + Multilib Laptop.

I previously installed nxclient which makes a mess for scribus ... ( scribus' cmake tries to link against /usr/NX/lib/{libz.so,libjpeg.so,libfreetype.so} ( oops )) ...

The build errors are appended below my .sig

These are the culprits ( note the references to /usr/NX/lib/ ):

Code:
# sh ./scribus.SlackBuild 2>&1 |tee ../scribus.SlackBuild-1.4.5.out

<<build failed after a few minutes>>

# grep NX ../scribus.SlackBuild-1.4.5.out

-- Found ZLIB: /usr/NX/lib/libz.so  
-- Found JPEG: /usr/NX/lib/libjpeg.so  
-- Found Freetype: /usr/NX/lib/libfreetype.so (found version "2.6.3") 
-- Looking for FT_Get_First_Char in /usr/NX/lib/libfreetype.so
-- Looking for FT_Get_First_Char in /usr/NX/lib/libfreetype.so - found
-- Looking for FT_Get_Next_Char in /usr/NX/lib/libfreetype.so
-- Looking for FT_Get_Next_Char in /usr/NX/lib/libfreetype.so - found

Fixed the build error by adding -DCMAKE_LIBRARY_PATH to the scribus.SlackBuild:

# diff -Naur scribus.SlackBuild.orig scribus.SlackBuild

Code:
-- scribus.SlackBuild.orig     2016-06-07 05:29:26.294075307 -0500
+++ scribus.SlackBuild  2016-06-07 08:22:36.857950496 -0500
@@ -72,8 +72,11 @@
   -o -perm 511 \) -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
-
+#
+# -DCMAKE_LIBRARY_PATH to link proper /usr/lib/{libz.so,libjpeg.so,libfreetype.so}
+#
 cmake \
+  -DCMAKE_LIBRARY_PATH="/usr/lib${LIBDIRSUFFIX}" \
   -DCMAKE_C_FLAGS="$SLKCFLAGS" \
   -DCMAKE_CXX_FLAGS="$SLKCFLAGS" \
   -DCMAKE_INSTALL_PREFIX:PATH=/usr \
Not sure why this is ... there is NO NX in my ldconfig -p listing ...

And, while I am here ...

Scribus 1.4.6 is the most recent stable release now.

Scribus version 1.4.6 also required the CMAKE_LIBRARY_PATH setting.

Otherwise, all I did was bump VERSION=1.4.6 in the scribus.SlackBuild file.

It builds and runs fine on Slackware Current64 + Multilib + Alien's pododo ...

I did not prepare a new .info file ( there is no md5sum on SourceForge ) but I can prep one if you like.

Thanks again guys !

-- kjh
Code:
# tail -200 ../scribus.SlackBuild-1.4.5.out

<<snip>>

[ 75%] Linking CXX executable scribus
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: warning: libjpeg.so.8, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libpodofo.so, may conflict with libjpeg.so.62
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: warning: libtiff.so.3, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libpodofo.so, may conflict with libtiff.so.5
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libcups.so: undefined reference to `[email protected]_1.2.0'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libcairo.so: undefined reference to `FT_Bitmap_New'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libfontconfig.so: undefined reference to `FT_Select_Size'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libcairo.so: undefined reference to `FT_Library_SetLcdFilter'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/libpng16.so.16: undefined reference to `[email protected]_1.2.3.4'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libxml2.so: undefined reference to `[email protected]_1.2.3.3'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libcairo.so: undefined reference to `FT_Bitmap_Convert'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libcairo.so: undefined reference to `FT_Bitmap_Done'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libxml2.so: undefined reference to `[email protected]_1.2.2.3'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libtiff.so: undefined reference to `[email protected]_6.2'
collect2: error: ld returned 1 exit status
scribus/CMakeFiles/scribus.dir/build.make:15718: recipe for target 'scribus/scribus' failed
make[2]: *** [scribus/scribus] Error 1
CMakeFiles/Makefile2:153: recipe for target 'scribus/CMakeFiles/scribus.dir/all' failed
make[1]: *** [scribus/CMakeFiles/scribus.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2
 
  


Reply

Tags
current, sbo, sbopkg, slackrepo


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
[SOLVED] Error building gst1-plugins-good 1.4.1 from SBO l0rddarkf0rce Slackware 4 10-06-2014 05:58 PM
[SOLVED] Failure building nvidia-kernel Slackbuild from SBo sysfce2 Slackware 7 07-02-2011 01:10 AM
problems building fontforge from SBo gtludwig Slackware 7 05-12-2010 01:52 PM
Pls help me take my 1st step! verysoon Fedora - Installation 2 12-12-2005 07:49 AM

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

All times are GMT -5. The time now is 05:00 AM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration