Did anybody of you ever try to compile Juced on 64bit platform?

http://code.google.com/p/juced/

The standalone version of the plugins seems to compile fine, but the vst
version does not:

-
Linking nekobeevst
/usr/bin/ld: ../../../../bin/libjuce_debug.a(juce_Time.o): relocation
R_X86_64_32 against `a local symbol' can not be used when making a
shared object; recompile with -fPIC
../../../../bin/libjuce_debug.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
-

Does anybody know what this means, or how to fix that?

Regards,
gizzmo aka Mathias
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Mathias Krause wrote:
> Did anybody of you ever try to compile Juced on 64bit platform?
>
> http://code.google.com/p/juced/
>
> The standalone version of the plugins seems to compile fine, but the vst
> version does not:
>
> -
> Linking nekobeevst
> /usr/bin/ld: ../../../../bin/libjuce_debug.a(juce_Time.o): relocation
> R_X86_64_32 against `a local symbol' can not be used when making a
> shared object; recompile with -fPIC
>

relocation
R_X86_64_32 against `a local symbol'


ls /usr -l | grep lib
drwxr-xr-x 204 root root 106496 2009-11-16 01:38 lib
drwxr-xr-x 33 root root 36864 2009-08-30 10:06 lib32
lrwxrwxrwx 1 root root 3 2009-04-21 15:23 lib64 -> lib

Maybe because lib64 is a link?


"recompile with -fPIC" What does this mean?


> ../../../../bin/libjuce_debug.a: could not read symbols: Bad value
> collect2: ld returned 1 exit status
> -
>
> Does anybody know what this means, or how to fix that?
>
> Regards,
> gizzmo aka Mathias
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Ralf Mardorf wrote:
> Mathias Krause wrote:
>
>> Did anybody of you ever try to compile Juced on 64bit platform?
>>
>> http://code.google.com/p/juced/
>>
>> The standalone version of the plugins seems to compile fine, but the vst
>> version does not:
>>
>> -
>> Linking nekobeevst
>> /usr/bin/ld: ../../../../bin/libjuce_debug.a(juce_Time.o): relocation
>> R_X86_64_32 against `a local symbol' can not be used when making a
>> shared object; recompile with -fPIC
>>
>>
>
> relocation
> R_X86_64_32 against `a local symbol'
>
>
> ls /usr -l | grep lib
> drwxr-xr-x 204 root root 106496 2009-11-16 01:38 lib
> drwxr-xr-x 33 root root 36864 2009-08-30 10:06 lib32
> lrwxrwxrwx 1 root root 3 2009-04-21 15:23 lib64 -> lib
>
> Maybe because lib64 is a link?
>

Pardon, complete nonsense.

>
> "recompile with -fPIC" What does this mean?
>
>
>
>> ../../../../bin/libjuce_debug.a: could not read symbols: Bad value
>> collect2: ld returned 1 exit status
>> -
>>
>> Does anybody know what this means, or how to fix that?
>>
>> Regards,
>> gizzmo aka Mathias
>>
> _______________________________________________
> 64studio-users mailing list
> 64studio-users@lists.64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-users
>
>

--
Secret of Tux: http://images.wallaceandgromit.com/user_uploads/forum_thumbnails/5/75/355.jpg
"Gromit bit me" says HMV dog: http://img.dailymail.co.uk/i/pix/2007/03_03/GomitHMVPA_468x319.jpg

_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

>> Did anybody of you ever try to compile Juced on 64bit platform?
>>
>> http://code.google.com/p/juced/
>>
>> The standalone version of the plugins seems to compile fine, but the vst
>> version does not:
>>
>> -
>> Linking nekobeevst
>> /usr/bin/ld: ../../../../bin/libjuce_debug.a(juce_Time.o): relocation
>> R_X86_64_32 against `a local symbol' can not be used when making a
>> shared object; recompile with -fPIC
>>
>>
>
> relocation
> R_X86_64_32 against `a local symbol'
>
>
> ls /usr -l | grep lib
> drwxr-xr-x 204 root root 106496 2009-11-16 01:38 lib
> drwxr-xr-x 33 root root 36864 2009-08-30 10:06 lib32
> lrwxrwxrwx 1 root root 3 2009-04-21 15:23 lib64 -> lib
>
> Maybe because lib64 is a link?
>
>
> "recompile with -fPIC" What does this mean?
>

That's exactly what i don't understand... maybe here's a hint:
http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=3

@Ralf: Does it compile on your system? Or did you never try it?
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Mathias Krause wrote:
>>
>> "recompile with -fPIC" What does this mean?
>>
>>
>
> That's exactly what i don't understand...
It means that you need to recompile the objects with the -fPIC directive
added to the build directives (i.e. the makefile, probably as an
addition to the GCC directives). When compiling 64-bit software you'll
almost always use -fPIC.

And btw, I've already tried building and using Juced in a 64-bit
environment. Doesn't work. Get in touch with Lucio Asnaghi, he'll tell
you what you need to know.

Best,

dp

_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

>>> "recompile with -fPIC" What does this mean?
>>>
>>>
>>>
>> That's exactly what i don't understand...
>>
> It means that you need to recompile the objects with the -fPIC directive
> added to the build directives (i.e. the makefile, probably as an
> addition to the GCC directives). When compiling 64-bit software you'll
> almost always use -fPIC.
>
ok .. that's clear. But i don't know exactly where to add it *g* ...
it's a too big build process with its makefiles and configration scripts
...

> And btw, I've already tried building and using Juced in a 64-bit
> environment. Doesn't work. Get in touch with Lucio Asnaghi, he'll tell
> you what you need to know.
>
I use some precompiled juced plugins, they work fine. But i wanted to
try to compile them, so that i could try to extend one of them ...

okay ... I'll try to contact him on his forum... no answer since then...
but maybe i'll get one...

thanks,

regards,
gizzmo
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Mathias Krause wrote:
>>>> "recompile with -fPIC" What does this mean?
>>>>
>>>>
>>>>
>>>>
>>> That's exactly what i don't understand...
>>>
>>>
>> It means that you need to recompile the objects with the -fPIC directive
>> added to the build directives (i.e. the makefile, probably as an
>> addition to the GCC directives). When compiling 64-bit software you'll
>> almost always use -fPIC.
>>
>>
> ok .. that's clear. But i don't know exactly where to add it *g* ...
> it's a too big build process with its makefiles and configration scripts
> ...
>

IIRC (I read your link about .a and .so etc. yesterday) also GCC needs
to be recompiled?!

>> And btw, I've already tried building and using Juced in a 64-bit
>> environment. Doesn't work. Get in touch with Lucio Asnaghi, he'll tell
>> you what you need to know.
>>
>>
> I use some precompiled juced plugins, they work fine. But i wanted to
> try to compile them, so that i could try to extend one of them ...
>
> okay ... I'll try to contact him on his forum... no answer since then...
> but maybe i'll get one...
>
> thanks,
>
> regards,
> gizzmo
>

Did you try that "solution" with wine?

Ralf

PS: I never tested Juced.
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users