LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
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 11-15-2011, 03:28 PM   #1
Jeronimo Barros
LQ Newbie
 
Registered: Oct 2010
Location: Brazil
Distribution: Slackware since 1996
Posts: 14

Rep: Reputation: 0
Glibc rpcsvc vanished in l/glibc-2.14.1-i486-2.txz


Today I tried to compile postfix in a slackware-current fresh instllation (changelog Sun Nov 13 16:03:06 UTC 2011) and got this error:

dict_nis.c:42:27: fatal error: rpcsvc/ypclnt.h: No such file or directory

In an older install:

root@ushuaia:~# grep ypclnt.h /var/adm/packages/*
/var/adm/packages/glibc-2.13-x86_64-5:usr/include/rpcsvc/ypclnt.h

But in the new one this directory doesn't appear.

Does anyone know what happened ?

Thanks in advance.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 11-15-2011, 06:40 PM   #2
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
That's not the only error with 2.14.1.
rpc has been removed, and replaced with a different library libtirpc.

About the rpc fiasco
http://sourceware.org/git/?p=glibc.g...iff;h=acee4873
http://sourceware.org/git/?p=glibc.g...iff;h=bdd816a3
^ Those patches will reinstate the missing headers, and fix a couple more bugs in glibc.
 
Old 11-15-2011, 09:34 PM   #3
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,851
Blog Entries: 15

Rep: Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191
I hope those can be added to the existing package like a patch by Patrick soon if it is needed.
 
Old 11-15-2011, 10:09 PM   #4
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by ReaperX7 View Post
I hope those can be added to the existing package like a patch by Patrick soon if it is needed.
It's needed, actually it's pretty much required

There's quite a few packages that will FTBFS -
nfs-utils
Code:
../../support/include/rpcsvc/nfs_prot.h:9:21: fatal error: rpc/rpc.h: No such file or directory
Funny thing is, Drepper says to use TI-RPC, but you can't build TI-RPC against this Glibc.
http://sourceforge.net/tracker/index...75&atid=903784
 
Old 11-15-2011, 10:27 PM   #5
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,851
Blog Entries: 15

Rep: Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191
I'll keep my eye out for glibc-2.14.1-patch*date or patch version number*-i486/x86_64-1.txz fairly soon on the -current tree.
 
Old 11-16-2011, 08:42 AM   #6
Darth Vader
Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 660

Rep: Reputation: 140Reputation: 140
Quote from the NEWS file of GLIBC Version 2.14

Code:
* The RPC implementation in libc is obsoleted.  Old programs keep working
  but new programs cannot be linked with the routines in libc anymore.
  Programs in need of RPC functionality must be linked against TI-RPC.
  The TI-RPC implemtation is IPv6 enabled and there are other benefits.

  Visible changes of this change include (obviously) the inability to link
  programs using RPC functions without referencing the TI-RPC library, the
  removal of the RPC headers from the glibc headers, and the lack of
  symbols defined in <rpc/netdb.h> when <netdb.h> is installed.
  Implemented by Ulrich Drepper.
That's it, folks! Even you love or hate it, you should live with it!
 
Old 11-16-2011, 10:09 AM   #7
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
instead, I personally agreed with the comment on top of the gentoo patch (inside their patches tarball)
Quote:
export the rpc symbols and headers again until we can get libtirpc sorted
out as a proper and full replacement

patch from fedora (if redhat can't get it to work as the maintainers of all
these packages, then what chance do we have!)

Last edited by ponce; 11-16-2011 at 10:11 AM.
 
2 members found this post helpful.
Old 11-16-2011, 10:09 AM   #8
GazL
Senior Member
 
Registered: May 2008
Posts: 3,503

Rep: Reputation: 1027Reputation: 1027Reputation: 1027Reputation: 1027Reputation: 1027Reputation: 1027Reputation: 1027Reputation: 1027
Quote:
Originally Posted by Darth Vader View Post
Quote from the NEWS file of GLIBC Version 2.14

Code:
* The RPC implementation in libc is obsoleted.  Old programs keep working
  but new programs cannot be linked with the routines in libc anymore.
  Programs in need of RPC functionality must be linked against TI-RPC.
  The TI-RPC implemtation is IPv6 enabled and there are other benefits.

  Visible changes of this change include (obviously) the inability to link
  programs using RPC functions without referencing the TI-RPC library, the
  removal of the RPC headers from the glibc headers, and the lack of
  symbols defined in <rpc/netdb.h> when <netdb.h> is installed.
  Implemented by Ulrich Drepper.
That's it, folks! Even you love or hate it, you should live with it!
I think you missed the point that tirpc isn't quite ready to take over yet, and still relies on some of the parts of glibc that they've removed and as disturbed1 pointed out above it won't build against glibc 2.14.

Deprecating/Obsoleting old stuff is all well and good, but one should really make sure that the new replacement is in place and ready to go before you take the old one away. Just another example of disjointed development in the linux ecosystem. No wonder the BSD guys laugh at us.
 
2 members found this post helpful.
Old 11-16-2011, 10:33 AM   #9
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by GazL View Post
I think you missed the point that tirpc isn't quite ready to take over yet, and still relies on some of the parts of glibc that they've removed and as disturbed1 pointed out above it won't build against glibc 2.14.

Deprecating/Obsoleting old stuff is all well and good, but one should really make sure that the new replacement is in place and ready to go before you take the old one away. Just another example of disjointed development in the linux ecosystem. No wonder the BSD guys laugh at us.
You can build libtirpc, but it needs patches. LFS is using patches from Debain.
http://linuxfromscratch.org/pipermai...er/003835.html

I've been running FreeBSD 8.2 and 9.0rc on a few VMs and spare Laptops. Once 9.0 is released, I'm going to see how it fairs on a modern PC with the Nvidia binary driver.
 
2 members found this post helpful.
Old 11-16-2011, 10:46 AM   #10
Darth Vader
Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 660

Rep: Reputation: 140Reputation: 140
Then, the one billion russian dollars question:

Why we need this frakking pre-alpha quality GLIBC, on release 2.14? Because?
 
2 members found this post helpful.
Old 11-16-2011, 11:27 AM   #11
Jeronimo Barros
LQ Newbie
 
Registered: Oct 2010
Location: Brazil
Distribution: Slackware since 1996
Posts: 14

Original Poster
Rep: Reputation: 0
So, falling back to the glibc-solibs-2.13-i486-4.txz...

Thank you very much for the explanations.
 
Old 11-16-2011, 01:47 PM   #12
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
I think the error, Darth, has been to deprecate the rpc stuff after the 2.14.x branch was already declared stable.
I also cannot agree with Ulrich, but maybe "pre-alpha quality" is unfair.
 
Old 11-26-2011, 05:31 AM   #13
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
I was trying to build the newest libvirt on -current and got stuck too without a working XDR implementation

so I tried to use libtirpc, discovering that DES and NIS were broken ( ), but seems to builds fine if patched.
the only thing is that (following LFS's advices) you have to install some headers just to let libtirpc build (you can remove them after building, but they will be needed to build postfix - or either I think you have to patch out its nis support).

if you want to have a look or test with apps that need rpc (they must use the libtirpc headers in /usr/include/tirpc) or with libvirt, sources are here:

http://ponce.cc/slackware/testing/rpcnis-headers/

(EDIT: postfix seems to build with these installed, and it runs also after)

http://ponce.cc/slackware/testing/libtirpc/

http://ponce.cc/slackware/testing/libvirt/

but I really don't know which way Pat is gonna take with this issue, so take this just as testing stuff...
comments/suggestions/fixes are obviously welcomed

Last edited by ponce; 11-26-2011 at 01:45 PM. Reason: added postfix no_nis.patch
 
3 members found this post helpful.
Old 12-15-2011, 02:56 AM   #14
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,504

Rep: Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912Reputation: 912
if someone is interested, I've started moving these things in git branches on github

https://github.com/Ponce/current-sou...rpc/l/libtirpc

already updated (the no-des.patch got prettier )

Last edited by ponce; 12-17-2011 at 05:36 AM. Reason: renamed the repository
 
Old 12-15-2011, 05:59 AM   #15
Jeronimo Barros
LQ Newbie
 
Registered: Oct 2010
Location: Brazil
Distribution: Slackware since 1996
Posts: 14

Original Poster
Rep: Reputation: 0
Ponce, thank you for the informations and scripts.

I'll try your scripts as soon as possible.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
kdebase-workspace-4.3.4-i486-1.txz anyone? antitu Slackware 2 06-09-2010 03:21 PM
[SOLVED] Glibc 1st pass wont compile (possibly i486 related) gsmedia Linux From Scratch 2 06-20-2009 07:32 AM
problem installing glibc-2.3.2-4.80.i686, glibc-common-2.3.2-4.80.8.i386.rpm martianpackets Red Hat 8 05-01-2009 04:22 PM
glibc-compiling loves to make errors? ok, let me post mine here: glibc 2.9 me-$-on Linux From Scratch 7 04-11-2009 07:22 PM
Replacing glibc using linuxthreads for glibc using nptl (native positx thread library CestusGW Linux From Scratch 4 01-20-2005 08:26 AM


All times are GMT -5. The time now is 01:07 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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration