LinuxQuestions.org
Visit Jeremy's Blog.
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-02-2021, 02:24 PM   #4321
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,125

Original Poster
Rep: Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200

Quote:
Originally Posted by Hangaber View Post
log4cpp

Same error from original SBo and https://github.com/Ponce/slackbuilds...raries/log4cpp

Code:
Making all in config
make[1]: Entering directory '/tmp/SBo/log4cpp-1.0/config'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/tmp/SBo/log4cpp-1.0/config'
Making all in src
make[1]: Entering directory '/tmp/SBo/log4cpp-1.0/src'
/bin/sh ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -I../include    -pthread -O2 -fPIC -O2 -DNDEBUG -Wall -Wno-unused -pedantic -MT Appender.lo -MD -MP -MF .deps/Appender.Tpo -c -o Appender.lo Appender.cpp
mkdir .libs
 g++ -DHAVE_CONFIG_H -I. -I../include -I../include -pthread -O2 -fPIC -O2 -DNDEBUG -Wall -Wno-unused -pedantic -MT Appender.lo -MD -MP -MF .deps/Appender.Tpo -c Appender.cpp  -fPIC -DPIC -o .libs/Appender.o
In file included from ../include/log4cpp/Appender.hh:21,
                 from Appender.cpp:11:
../include/log4cpp/Priority.hh:107:9: error: 
  107 |         throw(std::invalid_argument);
      |         ^~~~~
make[1]: *** [Makefile:424: Appender.lo] Error 1
make[1]: Leaving directory '/tmp/SBo/log4cpp-1.0/src'
make: *** [Makefile:356: all-recursive] Error 1
I don't know enough about C++ to correct the 'throw' lines. Some search result suggestions say to wrap it in a try/catch, and others say to just delete the throw() line [107] altogether.
IMHO an update to version 1.1.3 should be advised

https://git.slackbuilds.org/slackbui...it/?id=4204e23

thanks for the report!
 
1 members found this post helpful.
Old 10-02-2021, 02:35 PM   #4322
Roman Dyaba
Member
 
Registered: Sep 2020
Location: Russia, 690016 Vladivostok city, street Osipenko home 66, tel: +79247350007
Distribution: Slackware, UbuntuStudio, FreeBSD, GhostBSD
Posts: 317

Rep: Reputation: 40
because GCC 10.3 is diff to 11.2 ...
 
Old 10-02-2021, 03:04 PM   #4323
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,344

Rep: Reputation: 942Reputation: 942Reputation: 942Reputation: 942Reputation: 942Reputation: 942Reputation: 942Reputation: 942
Hi , today cffi and pycparser was added to -current , y suggest rename the existing 2 in SBo , like python2-cffi and python2-pycparser , and remove python3 support from script.

And then need check REQUIRES , in other slackbuilds to point to python2 - news
 
3 members found this post helpful.
Old 10-03-2021, 12:33 PM   #4324
metageek
Member
 
Registered: Jun 2007
Location: Farmington, CT
Distribution: Slackware64
Posts: 204

Rep: Reputation: 44
Quote:
Originally Posted by ponce View Post
IMHO an update to version 1.1.3 should be advised
I'm the maintainer of this slackbuild and I have already been able to update to version 1.1.3. Given submissions to SBo are currently closed, do I wait until they open again, or is there a way to contribute to Ponce's github repository to see it appear in SBo later on? (I have been updating other packages I maintain too).

Pedro
 
Old 10-03-2021, 01:24 PM   #4325
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,125

Original Poster
Rep: Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200
Quote:
Originally Posted by metageek View Post
I'm the maintainer of this slackbuild and I have already been able to update to version 1.1.3. Given submissions to SBo are currently closed, do I wait until they open again, or is there a way to contribute to Ponce's github repository to see it appear in SBo later on? (I have been updating other packages I maintain too).

Pedro
just send me patches based on what is already on SBo's git master branch: for log4cpp, if it's ok for you, I already pushed the update on SBo (the link in the post above is the commit on SBo's git -it shows also my address).
clone locally SBo's master branch ("git clone git://git.slackbuilds.org/slackbuilds.git"), apply your desired modifications over what's already there and send me the relative patches for every interested SlackBuild.
 
1 members found this post helpful.
Old 10-03-2021, 01:47 PM   #4326
metageek
Member
 
Registered: Jun 2007
Location: Farmington, CT
Distribution: Slackware64
Posts: 204

Rep: Reputation: 44
Quote:
Originally Posted by ponce View Post
just send me patches based on what is already on SBo's git master branch: for log4cpp, if it's ok for you, I already pushed the update on SBo (the link in the post above is the commit on SBo's git -it shows also my address).
clone locally SBo's master branch ("git clone git://git.slackbuilds.org/slackbuilds.git"), apply your desired modifications over what's already there and send me the relative patches for every interested SlackBuild.
Your patches for log4cpp are perfect and so it seems I don't have to do anything for that one. I'll go over the other ones and do as you said. Thanks!

Pedro
 
1 members found this post helpful.
Old 10-03-2021, 04:26 PM   #4327
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 977

Rep: Reputation: 239Reputation: 239Reputation: 239
Hi, recompiling gdal after the latest current-updates incl. the poppler-upgrade gave this :
Quote:
cc1plus: warning: /usr/lib64/include: No such file or directory [-Wmissing-include-dirs]
cc1plus: warning: /usr/lib64/include: No such file or directory [-Wmissing-include-dirs]
pdfdataset.cpp: In static member function ‘static PDFDataset* PDFDataset::Open(GDALOpenInfo*)’:
pdfdataset.cpp:4966:59: error: cannot convert ‘std::unique_ptr<GooString>’ to ‘GooString*’ in initialization
4966 | GooString* poMetadata = poCatalogPoppler->readMetadata();
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
| |
| std::unique_ptr<GooString>
make[2]: *** [../../GDALmake.opt:648: ../o/pdfdataset.lo] Error 1
make[2]: Leaving directory '/tmp/SBo/gdal-3.3.0/frmts/pdf'
make[1]: *** [GNUmakefile:15: pdf-install-obj] Error 2
make[1]: Leaving directory '/tmp/SBo/gdal-3.3.0/frmts'
make: *** [GNUmakefile:114: frmts-target] Error 2

gdal:
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.

(Y)es to continue, (N)o to abort, (R)etry the build?:
Any ideas what needs correcting? (the dependencies had been recompiled beforehand)

EDIT:
same fault when using latest gdal-3.3.2
patch described at https://bugs.freebsd.org/bugzilla/ has already been applied to gdal-3.3.[0,2]
Without configuration option --with-poppler, compilation finishes ok.

Last edited by brobr; 10-05-2021 at 03:35 PM.
 
Old 10-04-2021, 07:50 PM   #4328
metageek
Member
 
Registered: Jun 2007
Location: Farmington, CT
Distribution: Slackware64
Posts: 204

Rep: Reputation: 44
fsarchiver

fsarchiver fails to build, it seems to need a library called libattr (http://savannah.nongnu.org/projects/attr) which is not in SBo

Code:
checking attr/xattr.h usability... no
checking attr/xattr.h presence... no
checking for attr/xattr.h... no
configure: error: attr/xattr.h not found. you may have to install a package called attr, libattr, libattr-devel
 
Old 10-04-2021, 10:24 PM   #4329
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,981

Rep: Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556
Quote:
Originally Posted by metageek View Post
fsarchiver fails to build
I don't use the SBo build but my configure setup is the same as SBo's.

FSArchiver (0.8.6) builds fine here. (ChangeLog.txt Sun Oct 3 23:05:29 UTC 2021)

I don't see those lines in my configure log. I do see this:
Code:
checking for sys/xattr.h... yes
 
1 members found this post helpful.
Old 10-05-2021, 06:39 AM   #4330
metageek
Member
 
Registered: Jun 2007
Location: Farmington, CT
Distribution: Slackware64
Posts: 204

Rep: Reputation: 44
Quote:
Originally Posted by chrisretusn View Post
FSArchiver (0.8.6) builds fine here. (ChangeLog.txt Sun Oct 3 23:05:29 UTC 2021)
The version in SBo was still 0.8.0. I just tried building with version 0.8.6 and it works by simply changing the version number. Thanks.
 
1 members found this post helpful.
Old 10-05-2021, 09:21 AM   #4331
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,125

Original Poster
Rep: Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200
Quote:
Originally Posted by brobr View Post
Hi, recompiling gdal after the latest current-updates incl. the poppler-upgrade gave this :


Any ideas what needs correcting? (the dependencies had been recompiled beforehand)

EDIT:
same fault when using latest gdal-3.3.2
patch described at https://bugs.freebsd.org/bugzilla/ has already been applied to gdal-3.3.[0,2]
it needs a recent upstream patch for the newer poppler

https://git.slackbuilds.org/slackbui...it/?id=6c49eb8

thanks for reporting it!
 
1 members found this post helpful.
Old 10-05-2021, 09:25 AM   #4332
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,125

Original Poster
Rep: Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200
Quote:
Originally Posted by chrisretusn View Post
I don't use the SBo build but my configure setup is the same as SBo's.

FSArchiver (0.8.6) builds fine here. (ChangeLog.txt Sun Oct 3 23:05:29 UTC 2021)

I don't see those lines in my configure log. I do see this:
Code:
checking for sys/xattr.h... yes
Quote:
Originally Posted by metageek View Post
The version in SBo was still 0.8.0. I just tried building with version 0.8.6 and it works by simply changing the version number. Thanks.
thanks to you both for the report!
 
1 members found this post helpful.
Old 10-05-2021, 10:26 AM   #4333
Hangaber
Member
 
Registered: Sep 2004
Location: USA
Distribution: Slackware
Posts: 163

Rep: Reputation: 51
Quote:
Originally Posted by metageek View Post
fsarchiver fails to build, it seems to need a library called libattr (http://savannah.nongnu.org/projects/attr) which is not in SBo

Code:
checking attr/xattr.h usability... no
checking attr/xattr.h presence... no
checking for attr/xattr.h... no
configure: error: attr/xattr.h not found. you may have to install a package called attr, libattr, libattr-devel
I didn't install "attr, libattr, libattr-devel" either, v0.8.6 installed with VERSION=0.8.6 ./fsarchiver.SlackBuild

Do you have the stock "kernel-source" installed?

Edit: NM. I see you tried 0.8.6 and it also worked.

Last edited by Hangaber; 10-05-2021 at 10:28 AM. Reason: Submitted before reading the next post.
 
Old 10-05-2021, 02:59 PM   #4334
camerabambai
Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 408

Rep: Reputation: 54
The latest transcode

Code:
In file included from aud_aux.c:41:
/usr/include/lame/lame.h:877:30: note: expected ‘unsigned char *’ but argument is of type ‘char *’
  877 |         unsigned char*       mp3buf, /* pointer to encoded MP3 stream         */
      |         ~~~~~~~~~~~~~~~~~~~~~^~~~~~
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
libtool: link: ( cd ".libs" && rm -f "export_jpg.la" && ln -s "../export_jpg.la" "export_jpg.la" )
libtool: link: ( cd ".libs" && rm -f "export_im.la" && ln -s "../export_im.la" "export_im.la" )
mv -f .deps/export_xvid4_la-export_xvid4.Tpo .deps/export_xvid4_la-export_xvid4.Plo
mv -f .deps/export_xvid4_la-aud_aux.Tpo .deps/export_xvid4_la-aud_aux.Plo
make[2]: uscita dalla directory «/tmp/SBo/transcode-1.1.7/export»
make[1]: *** [Makefile:586: all-recursive] Errore 1
make[1]: uscita dalla directory «/tmp/SBo/transcode-1.1.7»
make: *** [Makefile:495: all] Errore 2
 
Old 10-05-2021, 03:18 PM   #4335
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,125

Original Poster
Rep: Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200Reputation: 4200
Quote:
Originally Posted by camerabambai View Post
The latest transcode

Code:
In file included from aud_aux.c:41:
/usr/include/lame/lame.h:877:30: note: expected ‘unsigned char *’ but argument is of type ‘char *’
  877 |         unsigned char*       mp3buf, /* pointer to encoded MP3 stream         */
      |         ~~~~~~~~~~~~~~~~~~~~~^~~~~~
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
libtool: link: ( cd ".libs" && rm -f "export_jpg.la" && ln -s "../export_jpg.la" "export_jpg.la" )
libtool: link: ( cd ".libs" && rm -f "export_im.la" && ln -s "../export_im.la" "export_im.la" )
mv -f .deps/export_xvid4_la-export_xvid4.Tpo .deps/export_xvid4_la-export_xvid4.Plo
mv -f .deps/export_xvid4_la-aud_aux.Tpo .deps/export_xvid4_la-aud_aux.Plo
make[2]: uscita dalla directory «/tmp/SBo/transcode-1.1.7/export»
make[1]: *** [Makefile:586: all-recursive] Errore 1
make[1]: uscita dalla directory «/tmp/SBo/transcode-1.1.7»
make: *** [Makefile:495: all] Errore 2
Hi Meska ( )! I cannot see no error in that log: maybe it's above in the output?
FWIW transcode builds fine here...

Last edited by ponce; 10-05-2021 at 03:31 PM.
 
  


Reply

Tags
current, sbo, sbopkg, slackrepo



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 08:16 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
Open Source Consulting | Domain Registration