Bug#603194: libogg0: libogg is not built with -fPIC

2010-11-12 Thread Ron

Hi Vladimir,

On Fri, Nov 12, 2010 at 10:38:52AM +0300, Vladimir Berezenko wrote:
 Sorry that I've made my bug-report so messy. But I really have a bug.
 I'm running debian on a powermac G5 quad with more than 4Gb of RAM.
 Seems that this error is not affecting my G4 Pegasos2 with 1Gb.
 AFAIK the ogg libs are built without PIC, because there are plenty of
 R_PPC_REL24 in libogg.so. This leads to such an errors:
 R_PPC_REL24 relocation at 0x0fae21d4 for symbol `memset' out of range
 in some heavy applications built myself (e.x. in HandBrake or avidemux).
 After rebuilding all the ogg stuff using the debian diffs and with
 enabled --with-pic all R_PPC_RELNN are changed to R_PPC_RELATIVE and
 everything started to build and work ok.

And this is with the current packages from Debian squeeze?
The build logs I can see show they were built with -fPIC

I've forwarded this to the powerpc porters list, in case they can
shed some light on any real issue with G5 machines.

The only thing that makes any sense to me at all so far would be
that the packages you are using were built with a broken libtool
or toolchain.  But I'm not seeing how they would have got that way
or why nobody else would have run into this already unless it's
some local corruption on your machine.

 Ron





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#603194: libogg0: libogg is not built with -fPIC

2010-11-12 Thread Michel Dänzer
On Fre, 2010-11-12 at 20:06 +1030, Ron wrote: 
 
 On Fri, Nov 12, 2010 at 10:38:52AM +0300, Vladimir Berezenko wrote:
  Sorry that I've made my bug-report so messy. But I really have a bug.
  I'm running debian on a powermac G5 quad with more than 4Gb of RAM.
  Seems that this error is not affecting my G4 Pegasos2 with 1Gb.
  AFAIK the ogg libs are built without PIC, because there are plenty of
  R_PPC_REL24 in libogg.so. This leads to such an errors:
  R_PPC_REL24 relocation at 0x0fae21d4 for symbol `memset' out of range
  in some heavy applications built myself (e.x. in HandBrake or avidemux).
  After rebuilding all the ogg stuff using the debian diffs and with
  enabled --with-pic all R_PPC_RELNN are changed to R_PPC_RELATIVE and
  everything started to build and work ok.
 
 And this is with the current packages from Debian squeeze?
 The build logs I can see show they were built with -fPIC
 
 I've forwarded this to the powerpc porters list, in case they can
 shed some light on any real issue with G5 machines.
 
 The only thing that makes any sense to me at all so far would be
 that the packages you are using were built with a broken libtool
 or toolchain.

I'm not seeing any R_PPC_REL24 in the output of

objdump -R /usr/lib/libogg.so.0

with libogg0 1.2.0~dfsg-1 installed.

 But I'm not seeing how they would have got that way or why nobody else
 would have run into this already unless it's some local corruption on
 your machine.

That seems most likely at this point, otherwise please provide more
information Vladimir.


-- 
Earthling Michel Dänzer   |http://www.vmware.com
Libre software enthusiast |  Debian, X and DRI developer



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#603194: libogg0: libogg is not built with -fPIC

2010-11-11 Thread Vladimir Berezenko
Package: libogg0
Version: 1.2.0~dfsg-1
Severity: important

libogg should be configured with --with-pic arg appended.



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: powerpc (ppc64)

Kernel: Linux 2.6.32-5-powerpc64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libogg0 depends on:
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib

libogg0 recommends no packages.

libogg0 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org