Re: alberta on powerpc: R_PPC_REL24 relocation out of range

On 05/22/2015 12:07 PM, Ansgar Burchardt wrote: > Maybe there was a bug in the (non-standard) clang toolchain when > alberta_3.0.1-1 was built on powerpc which has since been fixed? I have > requested a binNMU for alberta and hope this will make the issue go away > (#786500). As a follow-up: this

Re: alberta on powerpc: R_PPC_REL24 relocation out of range

[ Please CC me in replies. ] On 05/22/2015 11:05 AM, Michel Dänzer wrote: > On 22.05.2015 16:58, Ansgar Burchardt wrote: >> while looking at a test failure for dune-grid[1] on powerpc I encountered >> this issue: >> >> gmshtest: error while loading shared libraries: >> /usr/lib/powerpc-lin

Re: alberta on powerpc: R_PPC_REL24 relocation out of range

On 22.05.2015 16:58, Ansgar Burchardt wrote: > Hi, > > while looking at a test failure for dune-grid[1] on powerpc I encountered > this issue: > > gmshtest: error while loading shared libraries: > /usr/lib/powerpc-linux-gnu/libalberta_utilities.so.4: > R_PPC_REL24 relocation at 0x0fcd

alberta on powerpc: R_PPC_REL24 relocation out of range

Hi, while looking at a test failure for dune-grid[1] on powerpc I encountered this issue: gmshtest: error while loading shared libraries: /usr/lib/powerpc-linux-gnu/libalberta_utilities.so.4: R_PPC_REL24 relocation at 0x0fcde034 for symbol `time' out of range The internet suggests th

Re: R_PPC_REL24 relocation ... out of range

2010/6/18 Michel Dänzer : > On Fre, 2010-06-18 at 10:25 -0300, Gunther Furtado wrote: >> >> 2010/6/18 Gunther Furtado : >> >> [...] >> >> > >> > Yes, it is the debian package and I will report the bug as soon as I >> > can. >> > >> >> Funny thing: the safe-upgrade I ran today fixed the problem with

Re: R_PPC_REL24 relocation ... out of range

On Fre, 2010-06-18 at 10:25 -0300, Gunther Furtado wrote: > > 2010/6/18 Gunther Furtado : > > [...] > > > > > Yes, it is the debian package and I will report the bug as soon as I > > can. > > > > Funny thing: the safe-upgrade I ran today fixed the problem without > upgrading mplayer. If anyone

Re: R_PPC_REL24 relocation ... out of range

Oi, 2010/6/18 Gunther Furtado : [...] > > Yes, it is the debian package and I will report the bug as soon as I > can. > Funny thing: the safe-upgrade I ran today fixed the problem without upgrading mplayer. If anyone is interested I'll show aptitude's log. Cheers, -- "...agora, só nos sobro

Re: R_PPC_REL24 relocation ... out of range

Sex, 18Jun2010, "brian m. carlson" escreveu:, "brian m. carlson" escreveu: > On Thu, Jun 17, 2010 at 09:44:28PM -0300, Gunther Furtado wrote: > > Hi, > > > > After the latest update mplayer is giving me: > > > > mplayer: error while loading shared libraries: /usr/lib/libvpx.so.0: > > R_PPC_REL2

Re: R_PPC_REL24 relocation ... out of range

On Thu, Jun 17, 2010 at 09:44:28PM -0300, Gunther Furtado wrote: > Hi, > > After the latest update mplayer is giving me: > > mplayer: error while loading shared libraries: /usr/lib/libvpx.so.0: > R_PPC_REL24 relocation at 0x48040a68 for symbol `memset' out of range It appears that some code in a

R_PPC_REL24 relocation ... out of range

Hi, After the latest update mplayer is giving me: mplayer: error while loading shared libraries: /usr/lib/libvpx.so.0: R_PPC_REL24 relocation at 0x48040a68 for symbol `memset' out of range imac ppc 600MHz sid any hints? Cheers, Gunther -- "...agora, só nos sobrou o futuro...", visto em www.

Re: R_PPC_REL24 relocation out of range

hi does anyone know what the equivalent error message looks like on other archs? i am going to write up this problem and wanted to be able to catch web searches for the different forms of the error. -- [EMAIL PROTECTED] Brad Midgley

Re: R_PPC_REL24 relocation out of range

On Thu, Aug 02, 2001 at 11:21:59AM -0700, Daniel Jacobowitz wrote: > On Thu, Aug 02, 2001 at 12:22:38PM -0600, Bradley C. Midgley wrote: > > On some architectures, it will work anyway; also, the shared object > could be used for some other purpose besides dynamic linking (i > think?). You've just

Re: R_PPC_REL24 relocation out of range

On Thu, Aug 02, 2001 at 12:22:38PM -0600, Bradley C. Midgley wrote: > > > if the contents of a libfoo.a were created without -fPIC, then any .so > > > created with -lfoo will have REL24 relocations and fail. but debian policy > > i have another question along these lines. > > why doesn't gcc fail

Re: R_PPC_REL24 relocation out of range

> > if the contents of a libfoo.a were created without -fPIC, then any .so > > created with -lfoo will have REL24 relocations and fail. but debian policy i have another question along these lines. why doesn't gcc fail when it's told to create a .so using objects that are not PIC? is it because it

Re: R_PPC_REL24 relocation out of range

Bastien Nocera wrote: > Bradley C. Midgley wrote: > > > what is the story with this error? i'm seeing it at dynamic-lib-loadtime > > in a project i build for work that has lots of dynamically loaded modules. > > > > in a web search i see mention of the problem popping up for people all > > over t

Re: R_PPC_REL24 relocation out of range

On Fri, Jul 27, 2001 at 05:48:24PM -0600, Bradley C. Midgley wrote: > solved by creating another repository? No. Did it occur to you to look at what's there? -- G. Branden Robinson| Debian GNU/Linux | // // // / / [EMAIL PROTECTED]

Re: R_PPC_REL24 relocation out of range

solved by creating another repository? for now, i will rebuild the packages i need with gcc aliased to gcc -fPIC. fixing this for an entire multiplatform distro is going to be a mess. > I think I have this solved. See > . > > -- [EMAIL PROTECTED

Re: R_PPC_REL24 relocation out of range

On Thu, Jul 26, 2001 at 11:55:35PM -0700, Daniel Jacobowitz wrote: > This may need to be discussed further. If a library is only provided > statically, a PIC version needs to be provided or it can not be used > for shared libraries. X has a similar issue. I think I have this solved. See

Re: R_PPC_REL24 relocation out of range

On Fri, Jul 27, 2001 at 12:51:35AM -0600, Bradley C. Midgley wrote: > daniel, > > > Sure. But if you're using DynaLoader from 5.6.0, see the archives of > > debian-perl for your problem. Use current 5.6.1 packages from > > for those reading along, the thread is here: > http://lists.debian.org/d

Re: R_PPC_REL24 relocation out of range

daniel, > Sure. But if you're using DynaLoader from 5.6.0, see the archives of > debian-perl for your problem. Use current 5.6.1 packages from for those reading along, the thread is here: http://lists.debian.org/debian-perl-0105/msg00012.html > unstable; DynaLoader contained non-PIC code. unl

Re: R_PPC_REL24 relocation out of range

On Thu, Jul 26, 2001 at 07:09:51PM -0600, Bradley C. Midgley wrote: > i've found that the invocation of the shared-object creation line makes a > difference. > > the original invocation, pulling DynaLoader.a explicitly has getenv in a > REL24 relocation: > > [EMAIL PROTECTED]:~/cockpit/build/linu

Re: R_PPC_REL24 relocation out of range

i've found that the invocation of the shared-object creation line makes a difference. the original invocation, pulling DynaLoader.a explicitly has getenv in a REL24 relocation: [EMAIL PROTECTED]:~/cockpit/build/linuxgcc/scripting$ g++ -fpic -shared -o libscripting-1-0.so PerlScriptingDef.o PerlWr

Re: R_PPC_REL24 relocation out of range

On Thu, Jul 26, 2001 at 05:58:28PM -0600, Bradley C. Midgley wrote: > Dan, > > thanks for weighing in. people at work are suggesting that this kind of > problem shows that ppc isn't stable enough for real work but i want to > show them it's not *representative* -- it's *anomalous* :) Actually, it

Re: R_PPC_REL24 relocation out of range

Dan, thanks for weighing in. people at work are suggesting that this kind of problem shows that ppc isn't stable enough for real work but i want to show them it's not *representative* -- it's *anomalous* :) On Wed, 25 Jul 2001, Daniel Jacobowitz wrote: > On Wed, Jul 25, 2001 at 10:02:37PM -0600,

Re: R_PPC_REL24 relocation out of range

On Wed, Jul 25, 2001 at 10:02:37PM -0600, Bradley C. Midgley wrote: > > Use 'readelf -r' to determine the various types of relocations in > > a shared object file. In a properly compiled PPC .so file, you > > it seems that -fPIC doesn't suppress REL24 type relocations: First, I'm not sure it's s

Re: R_PPC_REL24 relocation out of range

David thanks for your reply > What version of gcc are you using? Older 2.95 versions are known > to have issues outputting R_PPC_REL24 relocs in PIC code. 2.95.4 (from -unstable) > Use 'readelf -r' to determine the various types of relocations in > a shared object file. In a properly compiled

Re: R_PPC_REL24 relocation out of range

On Sat, Jul 21, 2001 at 09:15:53AM -0600, Bradley C. Midgley wrote: > this code works on x86 so i believe it's a ppc-specific problem. using > -fPIC everywhere reduced the number of these errors but didn't eliminate > them. (i may try rebuilding libc6 with the recommended patch to see if it > helps

Re: R_PPC_REL24 relocation out of range

> this code works on x86 so i believe it's a ppc-specific problem. using > -fPIC everywhere reduced the number of these errors but didn't eliminate > them. (i may try rebuilding libc6 with the recommended patch to see if it > helps) The symbol wasn't va_arg_type_violation so it's not what I suspec

Re: R_PPC_REL24 relocation out of range

this code works on x86 so i believe it's a ppc-specific problem. using -fPIC everywhere reduced the number of these errors but didn't eliminate them. (i may try rebuilding libc6 with the recommended patch to see if it helps) these are modules that are being loaded "manually" using dlopen: dlopen(

Re: R_PPC_REL24 relocation out of range

> what is the story with this error? i'm seeing it at dynamic-lib-loadtime > in a project i build for work that has lots of dynamically loaded modules. Post the errors. This may be due to undeclared symbols, or it may be because of improper use of varargs (gcc emits a bogus symbol to catch this bu

Re: R_PPC_REL24 relocation out of range

Hi, Bradley C. Midgley wrote: what is the story with this error? i'm seeing it at dynamic-lib-loadtime in a project i build for work that has lots of dynamically loaded modules. in a web search i see mention of the problem popping up for people all over the place -- one of the first is a messa

Re: R_PPC_REL24 relocation out of range

Bradley C. Midgley wrote: > what is the story with this error? i'm seeing it at dynamic-lib-loadtime > in a project i build for work that has lots of dynamically loaded modules. You didn't compile stuff with -fPIC. Gerd -- Gerd Knorr <[EMAIL PROTECTED]>

Re: R_PPC_REL24 relocation out of range

On Wed, Jul 18, 2001 at 04:42:41PM -0600, Bradley C. Midgley wrote: > what is the story with this error? i'm seeing it at dynamic-lib-loadtime > in a project i build for work that has lots of dynamically loaded modules. Is there any chance you could make the project use static linking? I think thi

R_PPC_REL24 relocation out of range

what is the story with this error? i'm seeing it at dynamic-lib-loadtime in a project i build for work that has lots of dynamically loaded modules. in a web search i see mention of the problem popping up for people all over the place -- one of the first is a message from 1998 in which dan jacobowi