| Summary: | net-misc/shout-0.8.0-r1 fails to compile | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Bjarke Istrup Pedersen (RETIRED) <gurligebis> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | f5d8fd51ed1e804c9e8d0357e8614e0493b06e96 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
shout-0.8.0-r1_ebuild-patch´
shout-0.8.0-r1_ebuild-patch shout-0.8.0-r1_ebuild-patch |
||
|
Description
Bjarke Istrup Pedersen (RETIRED)
2004-08-07 12:45:51 UTC
Using: glibc-2.3.4.20040619 gcc-3.4.1-r1 If that might be at any help. fails at the same point for me, too (no matter if I use gcc 3.4.1 or 3.4.4) from a quick googling I'd say it's a glibc issue <quote>
> > /usr/lib/libdb-4.0.a(env_open.o): In function `__db_parse':
> > env_open.o(.text+0x13cb): undefined reference to `__ctype_b'
> > env_open.o(.text+0x1413): undefined reference to `__ctype_b'
> > /usr/lib/libdb-4.0.a(env_open.o): In function `__db_tmp_open':
> > env_open.o(.text+0x1f58): undefined reference to `__ctype_b'
> > /usr/lib/libdb-4.0.a(env_region.o): In function `__db_e_remfile':
> > env_region.o(.text+0xe17): undefined reference to `__ctype_b'
> > /usr/lib/libdb-4.0.a(hash_auto.o)(.text+0x468): more undefined references
> > to `__ctype_b' follow
OK, I've now verified that the problem was caused by RedHat's upgrade of
glibc last week from 2.2.x to 2.3.x where they lost some backwards
compatability for the older versions of te glibc package. They have a
BETA version of the fixed glibc 2.3.x available on their
bugzilla.redhat.com site. I suspect that very soon they will release
these changes as new glibc errata.
</quote>
this all is about another package, but show's the same behaviour, all other things found while googeling lead into this direction, too
ok, one last post from me about this issue for tonite... I have a quick fix that at least solved the problem for me... I modified shout-0-8-0/sock.c and have taken out the #include <ctype.h> in line 22. I have two remaining questions: a) does this fix the issue also for other ppl using glibc-2.3.4.20040619 ? b) does this break compilation for ppl using an older, stable glibc? Created attachment 37024 [details, diff]
shout-0.8.0-r1_ebuild-patch´
Created attachment 37024 [details, diff]
shout-0.8.0-r1_ebuild-patch´
all suspisions were totally wrong.
the whole issue was caused by a sock.o left in the source release (that was
build against an older glibc version)
attached you find a patch for the ebuild that simply removes this file
Created attachment 37025 [details]
shout-0.8.0-r1_ebuild-patch
all suspisions were totally wrong.
the whole issue was caused by a sock.o left in the source release (that was
build against an older glibc version)
attached you find a patch for the ebuild that simply removes this file
Created attachment 37026 [details, diff]
shout-0.8.0-r1_ebuild-patch
all suspisions were totally wrong.
the whole issue was caused by a sock.o left in the source release (that was
build against an older glibc version)
attached you find a patch for the ebuild that simply removes this file
Fixed in portage - thanks. |