SBo scripts not building on current (read 1st post, pls)

BW-userx · 10-26-2018, 06:33 PM

Does this have anything to do with you Ponce?
just thought I'd ask.

maybe you can get a royalty check.

ponce · 10-26-2018, 11:34 PM

Quote:

Originally Posted by BW-userx

Does this have anything to do with you Ponce?
just thought I'd ask.

maybe you can get a royalty check.

actually not: the authors of that was inspired for the name of their software by Ponce De Leon, I took my nickname from a local beverage (recipe with english subs).

Regnad Kcin · 10-27-2018, 03:20 AM

android-tools is not building

Quote:

[35/143]
clang++ -std=gnu++14 -D_GNU_SOURCE -DADB_HOST=1 -Icore/include -Icore/base/include -Icore/adb -c core/adb/client/usb_linux.cpp -o core/adb/client/usb_linux.cpp.o
FAILED: core/adb/client/usb_linux.cpp.o
clang++ -std=gnu++14 -D_GNU_SOURCE -DADB_HOST=1 -Icore/include -Icore/base/include -Icore/adb -c core/adb/client/usb_linux.cpp -o core/adb/client/usb_linux.cpp.o
core/adb/client/usb_linux.cpp:274:38: error: use of undeclared identifier 'major'
major(st.st_rdev), minor(st.st_rdev));
^
core/adb/client/usb_linux.cpp:274:57: error: use of undeclared identifier 'minor'
major(st.st_rdev), minor(st.st_rdev));

nobodino · 10-27-2018, 03:21 AM

problem solved for med with "--disable-python".
Thanks for all, once more.

ponce · 10-27-2018, 04:20 AM

Quote:

Originally Posted by Regnad Kcin

android-tools is not building

apply this patch to the SlackBuild (you have to use "patch -p3 < /path/to/the_patch" from the SlackBuild directory) to update it to version 9.0.0_r3

BW-userx · 10-27-2018, 08:35 AM

GTK=2 GTK=3

Code:

  CC       gtk/libfm_gtk3_la-fm-thumbnail.lo
  CCLD     libfm-gtk3.la
/usr/bin/sed: can't read /usr/lib64/libcairo.la: No such file or directory
libtool:   error: '/usr/lib64/libcairo.la' is not a valid libtool archive
make[4]: *** [Makefile:1402: libfm-gtk3.la] Error 1
make[4]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[3]: *** [Makefile:2767: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[2]: *** [Makefile:1133: all] Error 2
make[2]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[1]: *** [Makefile:567: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/libfm-1.3.0.2'
make: *** [Makefile:469: all] Error 2
Failures:
  libfm: libfm.SlackBuild return non-zero

what lib would you suggest I ln (soft link ) against to make libcairo.la, or is it just missing?

Code:

bash-4.4$ ls /usr/lib64/libcairo*
/usr/lib64/libcairo-gobject.so			     /usr/lib64/libcairo.so
/usr/lib64/libcairo-gobject.so.2		     /usr/lib64/libcairo.so.2
/usr/lib64/libcairo-gobject.so.2.11600.0	     /usr/lib64/libcairo.so.2.11600.0
/usr/lib64/libcairo-script-interpreter.so	     /usr/lib64/libcairomm-1.0.so
/usr/lib64/libcairo-script-interpreter.so.2	     /usr/lib64/libcairomm-1.0.so.1
/usr/lib64/libcairo-script-interpreter.so.2.11600.0  /usr/lib64/libcairomm-1.0.so.1.4.0

BTW when I do not link against GTK=0 I get this instead

Code:

find: ‘/tmp/SBo/package-libfm/usr/man’: No such file or directory
Failures:
  libfm: libfm.SlackBuild return non-zero

and on slackbuilds for reference the email is ponce@slackbuilds.org

ponce · 10-27-2018, 08:52 AM

Quote:

Originally Posted by BW-userx

Code:

  CC       gtk/libfm_gtk3_la-fm-thumbnail.lo
  CCLD     libfm-gtk3.la
/usr/bin/sed: can't read /usr/lib64/libcairo.la: No such file or directory
libtool:   error: '/usr/lib64/libcairo.la' is not a valid libtool archive
make[4]: *** [Makefile:1402: libfm-gtk3.la] Error 1
make[4]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[3]: *** [Makefile:2767: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[2]: *** [Makefile:1133: all] Error 2
make[2]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[1]: *** [Makefile:567: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/libfm-1.3.0.2'
make: *** [Makefile:469: all] Error 2
Failures:
  libfm: libfm.SlackBuild return non-zero

what lib would you suggest I ln (soft link ) against to make libcairo.la, or is it just missing?

Code:

bash-4.4$ ls /usr/lib64/libcairo*
/usr/lib64/libcairo-gobject.so			     /usr/lib64/libcairo.so
/usr/lib64/libcairo-gobject.so.2		     /usr/lib64/libcairo.so.2
/usr/lib64/libcairo-gobject.so.2.11600.0	     /usr/lib64/libcairo.so.2.11600.0
/usr/lib64/libcairo-script-interpreter.so	     /usr/lib64/libcairomm-1.0.so
/usr/lib64/libcairo-script-interpreter.so.2	     /usr/lib64/libcairomm-1.0.so.1
/usr/lib64/libcairo-script-interpreter.so.2.11600.0  /usr/lib64/libcairomm-1.0.so.1.4.0

you still have some dependency of libfm looking for libcairo.la: rebuild also all of the optional (like vala, if you have them installed) and mandatory dependencies (libfm-extra, menu-cache, lxmenu-data).

BW-userx · 10-27-2018, 10:01 AM

Quote:

Originally Posted by ponce

you still have some dependency of libfm looking for libcairo.la: rebuild also all of the optional (like vala, if you have them installed) and mandatory dependencies (libfm-extra, menu-cache, lxmenu-data).

order of install
1. libfm-extra
2. menu-cache
3. lxmenu-data
4. libfm
GTK=3
fail

Code:

  CCLD     libfm-gtk3.la
/usr/bin/sed: can't read /usr/lib64/libcairo.la: No such file or directory
libtool:   error: '/usr/lib64/libcairo.la' is not a valid libtool archive
make[4]: *** [Makefile:1402: libfm-gtk3.la] Error 1
make[4]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[3]: *** [Makefile:2767: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[2]: *** [Makefile:1133: all] Error 2
make[2]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[1]: *** [Makefile:567: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/libfm-1.3.0.2'
make: *** [Makefile:469: all] Error 2
Failures:
  libfm: libfm.SlackBuild return non-zero

this is me using sbotools attached to your repo. so now I just instlled sbopkg and in the process of configiring it and all of that stuff.

using it's menu, I set the config to this

Code:

root@slackcurrent:~# cat .sbopkg.conf
REPO_NAME=SBo-git
REPO_BRANCH=current

whereas your page here says to have it this

Code:

REPO_BRANCH=${REPO_BRANCH:-current}

REPO_NAME=${REPO_NAME:-SBo-git}

with that hyphen, and brackets and such, so is that a something I need to change in the conf file?
from
REPO_BRANCH=current to REPO_BRANCH=${REPO_BRANCH:-current} or REPO_BRANCH=-current

wait that was in this file, ( i just read that part, as I was just skimming, looking for pertinent information.)
you can use it on -current setting these two variables in /etc/sbopkg/sbopkg.conf

so you the one in sbopkg dir and get rid of the one in roots home?

MOD:

I figure it out using it like the home config is set putting the order like above, with pcmanfm being last to compile and install, and get this,

Code:

  CC       gtk/libfm_gtk_la-fm-thumbnail.lo
  CCLD     libfm-gtk.la
/bin/sed: can't read /usr/lib64/libcairo.la: No such file or directory
libtool:   error: '/usr/lib64/libcairo.la' is not a valid libtool archive
make[4]: *** [Makefile:1331: libfm-gtk.la] Error 1
make[4]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[3]: *** [Makefile:2767: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[2]: *** [Makefile:1133: all] Error 2
make[2]: Leaving directory '/tmp/SBo/libfm-1.3.0.2/src'
make[1]: *** [Makefile:567: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/libfm-1.3.0.2'
make: *** [Makefile:469: all] Error 2

libfm:
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?:

Code:

 Updating the active repository
 ──────────────────────────────────────────────────────────────────────────────
    ┌────────────────────────────────────────────────────────────────────┐
    │ From git://github.com/Ponce/slackbuilds                            │  
    │  * branch                  current    -> FETCH_HEAD                │  
    │ Already up to date.                                                │  
    │ HEAD is now at 0b34ee30d4 20181027.1 global branch merge.          │  
    │                                                                    │  
    │ Repository update complete.                                        │  
    │                                                                    │  
    │                                                                    │  
    │                                                                    │  
    │                                                                    │  
    │                                                                    │  
    │                                                                    │  
    │                                                                    │  
    │                                                                    │  
    ├────────────────────────────────────────────────────────────────────┤  
    │                             < EXIT >                               │  
    └────────────────────────────────────────────────────────────────────┘

just so you know I am using yours

orbea · 10-27-2018, 10:31 AM

You did read the changelog where it instructs users to remove all .la files in the LD_LIBRARY_PATH?

ponce · 10-27-2018, 10:34 AM

beside what orbea just wrote, have you read also the first post of this thread?
are you trying to build this on a clean and full installation of slackware64-current?

BW-userx · 10-27-2018, 11:54 AM

Quote:

Originally Posted by ponce

beside what orbea just wrote, have you read also the first post of this thread?
are you trying to build this on a clean and full installation of slackware64-current?

yes this is a fresh install and changed to current, so yes, it is a full install running current, (current update, can't get no more current then it is current), I am trying to put my standard what, I use stuff back into it. and yes I still have to figure out how to edit the slackbuilds using sbopkg, if i remember correctly it said one can do that using this program, and no, I didn't read the You did read the changelog where it instructs users to remove all .la files in the LD_LIBRARY_PATH? , I never really have issues to have to deal with changelogs and such.so that is not a habitual thing with me.

my last install of current, just a few days ago I had pcmanfm installed no issues.

how current can a current get if it is already current?

so how am I to do this?
seems to me that would be in the sackbuild or source to look of this item that needs to be removed form telling it to look for it.

here is states put this line in the slackbuild?

[SOLVED] Libtool's .la files

orbea · 10-27-2018, 12:28 PM

So this is a fresh install of 14.2 where you immediately updated to current? I'm not sure I understood that correctly.

If so, please do read the changelog, I think doing so and following the instructions contained should solve this.

BW-userx · 10-27-2018, 12:31 PM

Quote:

Originally Posted by orbea

You did read the changelog where it instructs users to remove all .la files in the LD_LIBRARY_PATH?

Code:

  GNU nano 3.1                    /etc/ld.so.conf                               

include /etc/ld.so.conf.d/*.conf
/lib64
/usr/lib64
/usr/local/lib64
/usr/x86_64-slackware-linux/lib64
include /etc/ld.so.conf.d/*.conf
/usr/lib64/seamonkey

so how do I go about doing something that is a system wide change because the update didn't?

ponce · 10-27-2018, 12:32 PM

Quote:

Originally Posted by BW-userx

my last install of current, just a few days ago I had pcmanfm installed no issues.

so there must be something wrong in this new installation, but as explained in the first post this is not the place to discuss these kind of problems...
please open a dedicated topic.

BW-userx · 10-27-2018, 12:40 PM

Quote:

Originally Posted by ponce

so there must be something wrong in this new installation, but as explained in the first post this is not the place to discuss these kind of problems...
please open a dedicated topic.

is this not for ponce slackbuilds on current? I have never really had to every ask about issues with current, because Ive never really had them. title says
" SBo scripts not building on current (read 1st post, pls)"

if you need a repository that has patches to build them on current, please use this project (not supported or endorsed by SBo)

https://github.com/Ponce/slackbuilds

so slackbuild no matter who is maintaning them their is no real support for them?

which leads me back to la files if that is a system wide issue then should not the system had made corrections to remove this, and not leave it up to the user?

volkerdi
Slackware Maintainer
post#7
https://www.linuxquestions.org/quest...es-4175429931/