Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
Daniel Jacobowitz wrote: The one in RPM. However, glibc 2.3.1-3 should (temporarily) work around this issue (and a rebuild of static libraries in the RPM package will help, too). Well, I get the error in the middle of a rpm build, so the couple of static libraries in there should have already been rebuilt. I will try -3 when it is available. -- see shy jo msg01402/pgp0.pgp Description: PGP signature
Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
On Mon, Oct 21, 2002 at 12:37:42PM -0400, Joey Hess wrote: Jeff Bailey wrote: It seems that this is caused by pre glibc-2.3 static libraries. I don't yet understand the whole problem, but I do know that a simple recompile of the static library makes it pick up the new symbols correctly. Which static library do you mean, one of the ones in glibc, or one in rpm, or one that rpm might be linked to? The one in RPM. However, glibc 2.3.1-3 should (temporarily) work around this issue (and a rebuild of static libraries in the RPM package will help, too). -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
Jeff Bailey wrote: Is it perhaps using an installed library instead of the newly built one? Either that or it's probably pulling in a static library for something else. I don't have enough information to offer a better suggestion. The failing link is linking a static rpm binary, so yes, it is pulling in other static libraries: -lz -lbz2 -lpopt -ldb --static. I guess that's the cause. -- see shy jo msg01419/pgp0.pgp Description: PGP signature
Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
Jeff Bailey wrote: It seems that this is caused by pre glibc-2.3 static libraries. I don't yet understand the whole problem, but I do know that a simple recompile of the static library makes it pick up the new symbols correctly. Which static library do you mean, one of the ones in glibc, or one in rpm, or one that rpm might be linked to? -- see shy jo pgpD0FYKMKOtO.pgp Description: PGP signature
Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
On Mon, Oct 21, 2002 at 12:37:42PM -0400, Joey Hess wrote: Jeff Bailey wrote: It seems that this is caused by pre glibc-2.3 static libraries. I don't yet understand the whole problem, but I do know that a simple recompile of the static library makes it pick up the new symbols correctly. Which static library do you mean, one of the ones in glibc, or one in rpm, or one that rpm might be linked to? The one in RPM. However, glibc 2.3.1-3 should (temporarily) work around this issue (and a rebuild of static libraries in the RPM package will help, too). -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
Daniel Jacobowitz wrote: The one in RPM. However, glibc 2.3.1-3 should (temporarily) work around this issue (and a rebuild of static libraries in the RPM package will help, too). Well, I get the error in the middle of a rpm build, so the couple of static libraries in there should have already been rebuilt. I will try -3 when it is available. -- see shy jo pgp1Yr6IFpEJx.pgp Description: PGP signature
Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
On Mon, Oct 21, 2002 at 01:41:23PM -0400, Joey Hess wrote: The one in RPM. However, glibc 2.3.1-3 should (temporarily) work around this issue (and a rebuild of static libraries in the RPM package will help, too). Well, I get the error in the middle of a rpm build, so the couple of static libraries in there should have already been rebuilt. I will try -3 when it is available. Is it perhaps using an installed library instead of the newly built one? Either that or it's probably pulling in a static library for something else. I don't have enough information to offer a better suggestion. -- learning from failures is nice in theory... but in practice, it sucks :) - Wolfgang Jaehrling
Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
Jeff Bailey wrote: Is it perhaps using an installed library instead of the newly built one? Either that or it's probably pulling in a static library for something else. I don't have enough information to offer a better suggestion. The failing link is linking a static rpm binary, so yes, it is pulling in other static libraries: -lz -lbz2 -lpopt -ldb --static. I guess that's the cause. -- see shy jo pgp8nJCjYqSgq.pgp Description: PGP signature
Re: FWD: Bug#165617: Problems compiling programs with librpm and the new libc6 2.3.1
(The other Jeff replying...)
It seems that this is caused by pre glibc-2.3 static libraries. I
don't yet understand the whole problem, but I do know that a simple
recompile of the static library makes it pick up the new symbols
correctly.
Daniel has one proposed fixed for glibc. I'm hoping to look at this
more tommorow night.
Tks,
Jeff Bailey
On Sun, Oct 20, 2002 at 06:23:38PM -0400, Joey Hess wrote:
Jeff do you have any fixes for rpm and glibc 2.3.1? I don't know where
this __ctype_b symbol is coming from (ctype.h?) or why the linker wants it,
but I get similar errors merely building rpm on a system with glibc 2.3.1
and it seems libc has stopped exporting the symbol. I tend to think this is
perhaps a glibc bug.
- Forwarded message from Angel Ramos [EMAIL PROTECTED] -
From: Angel Ramos [EMAIL PROTECTED]
Date: 20 Oct 2002 20:40:35 +0200
To: [EMAIL PROTECTED]
Subject: Bug#165617: Problems compiling programs with librpm and the new
libc6 2.3.1
Reply-To: Angel Ramos [EMAIL PROTECTED], [EMAIL PROTECTED]
X-Mailer: Ximian Evolution 1.0.8
X-Spam-Status: No, hits=-6.7 required=5.0
tests=DEBIAN_BTS_BUG,FORGED_RCVD_FOUND,RESENT_TO,
SPAM_PHRASE_00_01,X_LOOP
version=2.41
Package: librpm4
Severity: important
Hi!,
I am the maintainer of rpm2html package and I have problems in order to
compile this package again under the current sid because librpm returns
compiling errors. With the new libc6 I think some variables used for
some programs have been declared as local and this results on a
compiling error. For example look this simple program:
---test.c
char rpmReadConfigFiles();
int main() {
rpmReadConfigFiles();
return 0;
}
-
When I try to compile it I obtain the next errors:
[EMAIL PROTECTED]:~/debian/rpm2html-1.7$ gcc -o test -g -O2 test.c -lrpm
-lrpmio -lrpmdb -lz -lbz2 -ldb -lpopt
/usr/lib/librpmio.a(base64.o)(.text+0x277): In function `b64dec':
: reference to `__ctype_b' undefinied
/usr/lib/librpmio.a(base64.o)(.text+0x373): In function `b64dec':
: referencia to `__ctype_b' undefinied
collect2: ld returned 1 exit status
The same problem happens with other important functions.
I think this is because __ctype_b now is declared as local in the new
libc. With the old libc this compiles well. Probably the solution is to
define that variable in librpm.
Thanks Regards!
--
Angel Ramos
[EMAIL PROTECTED]
- End forwarded message -
--
see shy jo
--
learning from failures is nice in theory...
but in practice, it sucks :)
- Wolfgang Jaehrling
