LinuxQuestions.org
Page 4 of 6 « First 23 4 56
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware 14.1 - Release candidate 1! (https://www.linuxquestions.org/questions/slackware-14/slackware-14-1-release-candidate-1-a-4175480780/)

rkfb 10-16-2013 02:56 PM
My elinks stopped working:

$ elinks
elinks: error while loading shared libraries: libguile.so.17: cannot open shared object file: No such file or directory

Didier Spaier 10-16-2013 03:06 PM
Quote:
Originally Posted by rkfb (Post 5047065)
My elinks stopped working:

$ elinks
elinks: error while loading shared libraries: libguile.so.17: cannot open shared object file: No such file or directory
Code:
bash-4.2$ bzgrep libguile MANIFEST.bz2 |grep "so.*0$"
-rwxr-xr-x root/root    119224 2013-10-09 17:37 usr/lib64/libguilereadline-v-18.so.18.0.0
-rwxr-xr-x root/root  1604792 2013-10-09 17:37 usr/lib64/libguile-2.0.so.22.7.0
bash-4.2$
But elinks is not shipped in Slackware. If you got it from slackbuilds.org, bear in mind that slackbuilds there are provided for stable releases only.

PS if you don't need to write scripting plugins, you could just try removing this line:
--with-guile \
from the configure command in the SlackBuild.

rkfb 10-16-2013 03:22 PM
Quote:
Originally Posted by Didier Spaier (Post 5047075)
Code:
bash-4.2$ bzgrep libguile MANIFEST.bz2 |grep "so.*0$"
-rwxr-xr-x root/root    119224 2013-10-09 17:37 usr/lib64/libguilereadline-v-18.so.18.0.0
-rwxr-xr-x root/root  1604792 2013-10-09 17:37 usr/lib64/libguile-2.0.so.22.7.0
bash-4.2$
But elinks is not shipped in Slackware. If you got it from slackbuilds.org, bear in mind that slackbuilds there are provided for stable releases only.
Ah, I didn't realise it wasn't provided, I'll sort it out then. I symlinked the installed libguile to the libguile I need and that seems fine. Just need libgc.so.1 next :-)

Sorry to appear a bit dim but I'm not too sure what that command is you posted, I get:

$ bzgrep libguile MANIFEST.bz2 |grep "so.*0$"
bzip2: Can't open input file MANIFEST.bz2: No such file or directory.

Is this to be run somewhere in particular?

mostlyharmless 10-16-2013 03:25 PM
efibootmgr
 
Gentlemen and Ladies,

I haven't actually tried this yet, as I'm still waiting for my new hardware to show up, but I am planning to use grub not elilo, which probably doesn't make a difference here. However the syntax for efibootmgr seems a bit different from what I've seen elsewhere. Why for example:

Quote:
efibootmgr -q -c -d /dev/sdb -p 1 -l "\EFI\Slackware\elilo.efi" -L slack2
rather than

Code:
efibootmgr -q -c -d /dev/sdb -p 1 -L 'Slackware' -l \\EFI\\slackware\\grubx64.efi
... other than the fact that you've tested the first one :)

Didier Spaier 10-16-2013 03:27 PM
Quote:
Originally Posted by rkfb (Post 5047085)
Sorry to appear a bit dim but I'm not too sure what that command is you posted, I get:

$ bzgrep libguile MANIFEST.bz2 |grep "so.*0$"
bzip2: Can't open input file MANIFEST.bz2: No such file or directory.

Is this to be run somewhere in particular?
Sorry, I should have stated that this command should be run in the /slackware or /slackware64 directory of a Slakware{,64}-current tree (I ran it in a local mirror of Slackware64-current). I assume that file MANIFEST.bz2 records all files that should be installed after a full Slackware installation (kind of a ls -l)

Didier Spaier 10-16-2013 03:32 PM
Quote:
Originally Posted by mostlyharmless (Post 5047086)
Gentlemen,

I haven't actually tried this yet, as I'm still waiting for my new hardware to show up, but I am planning to use grub not elilo, which probably doesn't make a difference here. However the syntax for efibootmgr seems a bit different from what I've seen elsewhere. Why for example:



rather than

Code:
efibootmgr -q -c -d /dev/sdb -p 1 -L 'Slackware' -l \\EFI\\slackware\\grubx64.efi
... other than the fact that you've tested the first one :)
I don't see other differences than doubled first backslash in your case and not using double quotes.

I assume that order of options doesn't matter (but didn't check).

Anyhow there is always a good way to be sure: try ;)

AlleyTrotter 10-16-2013 03:34 PM
Quote:
Originally Posted by mostlyharmless (Post 5047086)
Gentlemen,
I haven't actually tried this yet, ... However the syntax for efibootmgr seems a bit different from what I've seen elsewhere. Why for example:
rather than

Code:
efibootmgr -q -c -d /dev/sdb -p 1 -L 'Slackware' -l \\EFI\\slackware\\grubx64.efi
... other than the fact that you've tested the first one :)
The double backslash is escaping the second backslash. The quotes do the same thing. They keep the shell from seeing \ as a control. I think the double quotes are more self explanatory.

At least that is the way I see it.
John

rkfb 10-16-2013 03:35 PM
Quote:
Originally Posted by Didier Spaier (Post 5047088)
Sorry, I should have stated that this command should be run in the /slackware or /slackware64 directory of a Slakware{,64}-current tree (I ran it in a local mirror of Slackware64-current.
Thanks...I'll fetch myself a tree.

rkfb 10-16-2013 04:22 PM
Solved my elinks problem:

# cd /usr/lib
# ln -s libguile-2.0.so.22.7.0 libguile.so.17

Install gc:
http://slackbuilds.org/repository/14.0/development/gc/

Install libunistring:
http://slackware.org.uk/slacky/slack...istring/0.9.3/

That's it...

hope it helps someone.

saulgoode 10-16-2013 05:45 PM
Quote:
Originally Posted by rkfb (Post 5047120)
Both those packages are included in RC1 and should be part of a full install.

gc-7.2d

libunistring-0.9.3

mostlyharmless 10-16-2013 09:20 PM
Ok, thanks AlleyTrotter, merci Didier

aaazen 10-16-2013 10:58 PM
memtest86+
 
There is a new version of memtest86+ that just came out last month, version 5.01

Could be included in the new release?

I recognizes newer cpu chips and even shows the cpu temperature of my fairly new AMD system.

Didier Spaier 10-16-2013 11:56 PM
It seems that Mr Volkerding chose to please everyone ;)
Code:
efibootmgr -q -c -d $EFI_DEVICE -p $EFI_PARTITION -l "\\EFI\\Slackware\\elilo.efi" -L "Slackware"

marnold 10-17-2013 09:50 AM
Quote:
Originally Posted by comet.berkeley (Post 5047259)
There is a new version of memtest86+ that just came out last month, version 5.01

Could be included in the new release?

I recognizes newer cpu chips and even shows the cpu temperature of my fairly new AMD system.
Ask and ye shall receive:

Quote:
Thu Oct 17 05:21:47 UTC 2013
isolinux/initrd.img: Rebuilt.
kernels/memtest/memtest: Upgraded.
Upgraded to memtest86+-5.01.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Upgraded to memtest86+-5.01.

rkfb 10-17-2013 12:28 PM
Quote:
Originally Posted by rkfb (Post 5047120)
Solved my elinks problem:

# cd /usr/lib
# ln -s libguile-2.0.so.22.7.0 libguile.so.17

Install gc:
http://slackbuilds.org/repository/14.0/development/gc/

Install libunistring:
http://slackware.org.uk/slacky/slack...istring/0.9.3/

That's it...

hope it helps someone.
Sorry, it turns out it didn't work. still getting guile errors so removed and rebuilt with Didier Spaier's suggestion of removing guile from the slackbuild.

Works fine now.


All times are GMT -5. The time now is 11:40 PM.
Page 4 of 6 « First 23 4 56
Show 50 post(s) from this thread on one page