SBo scripts not building on current (read 1st post, pls)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi J.W. that's a lot of work you have done. What buildscript did you use? Did you not use as starting point the wps.Slackbuild script at Slackbuilds.org (present in this archive)?
That only uses a doinstall.sh for common stuff (icons, mime, desktop databases) and creates a working package as described above (at least at my end).
Basically, yes. I used SBo's SlackBuild.
There was a little progress in my investigation on my environmental issues.
I'm using fcitx IM on my desktop (Xfce4) as a Japanese input method.
Under my investigation, I found below.
In case of using "fcitx" as IM on X :
- wps-office which use it's own libdbus-1 (3.14.6) didn't start.
- wps-office which re-linked to slackware's system libdbus-1 (3.19.13)works
In case of "fcitx" disabled environment:
- wps-office which use it's own libdbus-1 (3.14.6)works
As it is shown on above result, the underlying solution is not yet known for me, but it is possible that fcitx might be one of the causes.
Since, prior to wps-office-11.1.0.10702, libdbus-1.so.x did not exist in [PATH-TO]/office6/,
I think that the problem did not manifest even in my environment with fcitx enabled.
I think the issue I reported first is not a problem with SBo's wps-office.SlackBuild, but a problem specific to my environment that fcitx is enabled.
I will continue to investigate whether fcitx can take fundamental measures.
I'm sorry for making a noise on my specific issue.
I think the issue I reported first is not a problem with SBo's wps-office.SlackBuild, but a problem specific to my environment that fcitx is enabled.
I will continue to investigate whether fcitx can take fundamental measures.
This makes sense; at this end only English was tested. But if it is fcitx-related/-dependent maybe a separate thread for this would be more suitable?
This makes sense; at this end only English was tested. But if it is fcitx-related/-dependent maybe a separate thread for this would be more suitable?
Yes, if I think I need to do further discussion on this issue, I will create a new thread, not here.
This is my personal opinion. For many slackware users who don't need fcitx, I suspect that the problem I've reported doesn't occur and the number of wps-office users is relatively small.
Therefore, I don't think it is necessary to fix this issue to wps-office.SlackBuild on SBo upstream.
BTW, in my environment with fcitx enabled, I haven't had any problems with applications other than wps-office.
I also reported my investigation result to the package maintainer of wps-office.SlackBuild.
Reference information about fcitx)
I checked fcitx process info on X.
nbd not building correctly it seems.
Once package been made and installed, there's nothing under /etc (should be /etc/nbd-server/ )
Re-compiled the package again, I see no errors related to this. But I don't see anything rel to /etc/nbd-server either...
Additionally, nbd-client as command is not found. nbd-server and nbd-trdump are both found
Any ideas?
No config file is provided by the build itself, so none included in the final package. Running 'man 5 nbd-server' gives all the possible options for a config file. Also, the package's /usr/doc/nbd-3.21/README.md
gives an example. I could add that as an /etc/nbd-server/config.example file if it was considered to be useful.
As already mentioned, nbd-client is found in /usr/sbin
Today, I was trying to install fzf from your repo in the usual way.
I got these error messages:
Code:
fzf-0.27.2/test/test_go.rb
fzf-0.27.2/uninstall
fatal: not a git repository (or any of the parent directories): .git
GOARCH=amd64 go build -a -ldflags "-s -w -X main.version=0.27.2 -X main.revision=0.27.2" -tags "" -mod=vendor -o target/fzf-gccgo_amd64
vendor/github.com/saracen/walker/walker.go:10:2: cannot find package
vendor/github.com/mattn/go-isatty/isatty_tcgets.go:6:8: cannot find package
make: *** [Makefile:126: target/fzf-gccgo_amd64] Error 1
fzf:
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.
No config file is provided by the build itself, so none included in the final package. Running 'man 5 nbd-server' gives all the possible options for a config file. Also, the package's /usr/doc/nbd-3.21/README.md
gives an example. I could add that as an /etc/nbd-server/config.example file if it was considered to be useful.
As already mentioned, nbd-client is found in /usr/sbin
chris
Thanks Chris!
I'll give that a try, see what happens
Today, I was trying to install fzf from your repo in the usual way.
I got these error messages:
Code:
fzf-0.27.2/test/test_go.rb
fzf-0.27.2/uninstall
fatal: not a git repository (or any of the parent directories): .git
GOARCH=amd64 go build -a -ldflags "-s -w -X main.version=0.27.2 -X main.revision=0.27.2" -tags "" -mod=vendor -o target/fzf-gccgo_amd64
vendor/github.com/saracen/walker/walker.go:10:2: cannot find package
vendor/github.com/mattn/go-isatty/isatty_tcgets.go:6:8: cannot find package
make: *** [Makefile:126: target/fzf-gccgo_amd64] Error 1
fzf:
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.
Thanks in advance for your traditional help reviewing this issue.
Best Regards,
Francisco.
hi Francisco,
I think you missed reading the README of google-go-lang
Code:
The tools are added to the path by putting go.sh and go.csh files in
/etc/profile.d and letting the system's /etc/profile or /etc/csh.login
pick it up.
that means after the google-go-lang package installation you have to open a new root shell with "su -" before trying to build fzf or your environment will keep using the go compiler from gcc
Quote:
GOARCH=amd64 go build -a -ldflags "-s -w -X main.version=0.27.2 -X main.revision=0.27.2" -tags "" -mod=vendor -o target/fzf-gccgo_amd64
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
