LinuxQuestions.org
Help answer threads with 0 replies.
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 08-05-2021, 08:46 AM   #1
asarangan
Member
 
Registered: Jul 2009
Posts: 89

Rep: Reputation: 18
compiler says stubs-64.h missing from slackware64-current


As the subject says, stdio.h from gcc is complaining that important header files are missing. I looked in /usr/include/gnu/, and I can see stubs-32.h but not stubs-64.h. My /etc/slackpkg/mirror file is pointing to slackware64-current, not the 32-bit version. Any ideas?
 
Old 08-05-2021, 08:52 AM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,081

Rep: Reputation: Disabled
This file is shipped in glibc-2.33-x86_64-2. Is this package installed?

PS Are you sure you installed Slackware64-current? To check type:
Code:
uname -m
The output should be:
x86_64

Last edited by Didier Spaier; 08-05-2021 at 08:58 AM.
 
Old 08-05-2021, 04:07 PM   #3
asarangan
Member
 
Registered: Jul 2009
Posts: 89

Original Poster
Rep: Reputation: 18
Quote:
Originally Posted by Didier Spaier View Post
This file is shipped in glibc-2.33-x86_64-2. Is this package installed?

PS Are you sure you installed Slackware64-current? To check type:
Code:
uname -m
The output should be:
x86_64
Yes, uname -m gives x86_64. I have no idea how glibc got missed. WHen I did the original installation, I selected "everything".

'slackpkg search glibc' gives me the following:

[ installed ] - aaa_glibc-solibs-2.33-x86_64-2
[uninstalled] - glibc-2.33-x86_64-2
[uninstalled] - glibc-i18n-2.33-x86_64-2
[uninstalled] - glibc-profile-2.33-x86_64-2
[ installed ] - glibc-zoneinfo-2021a-noarch-1


I don't know why glibc-2.33-x86_64-2 shows up as uninstalled. I tried 'slackpkg install glibc-2.33-x86_64-2' and I get "No packages match the pattern for install". I checked /etc/slackpkg/blacklist and that does not have anything listed.

Any ideas would be appreciated.
 
Old 08-05-2021, 04:19 PM   #4
drumz
Member
 
Registered: Apr 2005
Location: Oklahoma, USA
Distribution: Slackware
Posts: 907

Rep: Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697
Quote:
Originally Posted by asarangan View Post
I don't know why glibc-2.33-x86_64-2 shows up as uninstalled. I tried 'slackpkg install glibc-2.33-x86_64-2' and I get "No packages match the pattern for install". I checked /etc/slackpkg/blacklist and that does not have anything listed.

Any ideas would be appreciated.
I don't use slackpkg. Instead I keep a local mirror updated and directly use installpkg/upgradepkg/removepkg. Why not just directly use installpkg to install the missing glibc-* packages?

After installing the packages using installpkg I imagine slackpkg will see that they're installed.

Another way to check installed packages:

Code:
$ ls /var/lib/pkgtools/packages/ | grep glibc
aaa_glibc-solibs-2.33-x86_64-2
glibc-2.33-x86_64-2
glibc-i18n-2.33-x86_64-2
glibc-profile-2.33-x86_64-2
glibc-zoneinfo-2021a-noarch-1
 
Old 08-05-2021, 04:41 PM   #5
asarangan
Member
 
Registered: Jul 2009
Posts: 89

Original Poster
Rep: Reputation: 18
Quote:
Originally Posted by drumz View Post
I don't use slackpkg. Instead I keep a local mirror updated and directly use installpkg/upgradepkg/removepkg. Why not just directly use installpkg to install the missing glibc-* packages?

After installing the packages using installpkg I imagine slackpkg will see that they're installed.

Another way to check installed packages:

Code:
$ ls /var/lib/pkgtools/packages/ | grep glibc
aaa_glibc-solibs-2.33-x86_64-2
glibc-2.33-x86_64-2
glibc-i18n-2.33-x86_64-2
glibc-profile-2.33-x86_64-2
glibc-zoneinfo-2021a-noarch-1

So, is slackpkg broken, or am I doing something wrong?
 
Old 08-05-2021, 04:43 PM   #6
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,357

Rep: Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962
IM not sure , but some times its only a mismatch directory.

The file you mentioned is on

Quote:
/usr/include/gnu/FILE
and the project you go to compile probably search on

Quote:
/usr/include/FILE
If you have file 32 , ina 64 bit system , you broken something.

YOu install multilib , or uncomment 32 bits sources from slackpkg config.

Im my system i have only file 64.h no 32 here.

Last edited by USUARIONUEVO; 08-05-2021 at 04:45 PM.
 
Old 08-06-2021, 09:11 AM   #7
drumz
Member
 
Registered: Apr 2005
Location: Oklahoma, USA
Distribution: Slackware
Posts: 907

Rep: Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697Reputation: 697
Quote:
Originally Posted by asarangan View Post
So, is slackpkg broken, or am I doing something wrong?
I don't know. You didn't run

Code:
ls /var/lib/pkgtools/packages/ | grep glibc
so it's impossible to see what is actually installed on your system.
 
Old 08-06-2021, 10:17 AM   #8
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado, USA
Distribution: Slackware
Posts: 930

Rep: Reputation: 480Reputation: 480Reputation: 480Reputation: 480Reputation: 480
Just a thought... Did you recently upgrade from 14.2 to -current, maybe late January according to your earlier posts?

When you upgraded did you do a new install or upgrade the existing 14.2 install?

Do you run 'slackpkg install-new' regularly? It's a good idea to run that command when using -current.

Take care!
 
Old 08-06-2021, 10:59 AM   #9
lovemeslk
Member
 
Registered: Feb 2020
Location: Rantoul IL
Distribution: Slackware
Posts: 350

Rep: Reputation: 72
Quote:
I don't use slackpkg. Instead I keep a local mirror updated and directly use installpkg/upgradepkg/removepkg
upgradepkg --install-new slackware64/*/*.t?z is what your missing.
as per Pat.
#!/bin/sh
for dir in a ap d e f k kde l n t tcl x xap xfce y ; do
( cd $dir ; upgradepkg --install-new *.t?z )
done
This is how you keep slackware current updated.
As for stable you upgrade from patches. upgradepkg slackware64-14.2/patches/packages/*.t?z
as for missing file without install-new you may be missing something.
I keep a local mirror synced also but use slackpkg to handle it.
Code:
# Local Directory
#----------------------------------------------------------------
# file://path/to/some/directory/
file://home/ftp/pub/Linux/Slackware/slackware64-current/
#----------------------------------------------------------------
# Slackware64-15.0
then use this script
Create the directory
Code:
mkdir -p /home/ftp/pub/Linux/Slackware
cd /home/ftp/pub/Linux/Slackware/
Then put this there name it slacksync
Code:
#!/bin/sh
#MIRROR=rsync://slackware.absolutehosting.net/slackware
#MIRROR=rsync://ftp.slackware.com/slackware
#MIRROR=rsync://dfw.mirror.rackspace.com/slackware 
#MIRROR=rsync://slackware.mirrors.tds.net/slackware
MIRROR=rsync://mirrors.kernel.org/slackware/ 
rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware-14.1 /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware64-14.1 /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware-14.2 /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware64-14.2 /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware-current /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware64-current /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware64-15.0 /home/ftp/pub/Linux/Slackware/
or you could
Code:
cat > /home/ftp/pub/Linux/Slackware/slacksync.sh <<EOF
#!/bin/sh
#MIRROR=rsync://slackware.absolutehosting.net/slackware
#MIRROR=rsync://ftp.slackware.com/slackware
#MIRROR=rsync://dfw.mirror.rackspace.com/slackware 
#MIRROR=rsync://slackware.mirrors.tds.net/slackware
MIRROR=rsync://mirrors.kernel.org/slackware/ 
rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware-14.1 /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware64-14.1 /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware-14.2 /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware64-14.2 /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware-current /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware64-current /home/ftp/pub/Linux/Slackware/

rsync -r -a -v     --delete --progress --stats    $MIRROR/slackware64-15.0 /home/ftp/pub/Linux/Slackware/
EOF
anyway you do it install-new has to be done.

Last edited by lovemeslk; 08-06-2021 at 11:01 AM.
 
  


Reply



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
libpthread-stubs.so and pulseaudio eithrial Linux - Software 1 08-21-2013 07:11 PM
pthread-stubs for CentOS Rodnower Linux - Software 3 04-02-2010 10:50 AM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
Stubs-32.h file missing error during compilation on Windows using Colinux + FC4 rkaur Linux - Software 0 03-21-2007 06:11 AM
Problems writing GDB exception handler stubs Dent Programming 0 10-28-2002 01:10 PM

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

All times are GMT -5. The time now is 02:48 PM.

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