[lvs-users] Question on installing lvs snmp module on centos 5

[lists-95]

Hi,

Just on the slim chance that anyone has done this... :-).

I've installed kernel-devel, net-snmp-devel etc on centos 5
downloaded ipvsadm src code, run make, copied libipvs across to the
net-snmp-lvs-module-0.0.4 directory
then gone into that directory and run make....
and I get:

gcc: -lcrypto: linker input file unused because linking not done
ld -fPIC -shared  `net-snmp-config --netsnmp-libs` -o lvs.so lvs.o
libipvs/libipvs.a
ld: lvs.o: relocation R_X86_64_32 against `a local symbol' can not be
used when making a shared object; recompile with -fPIC
lvs.o: could not read symbols: Bad value
make: *** [lvs.so] Error 1
rm lvs.o

As far as I can see the -fPIC option is enabled on these files? Or is it
related to the compilation of net-snmp (which was from RPM)?

Any help really, really appreciated!
Thanks,
Malcolm.






_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@...
Send requests to lvs-users-request@...
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

[Joseph Mack]

On Mon, 11 Feb 2008, lists wrote:

> Hi,

I may be talking through my hat here...

Is anyone maintaining the lvs snmp module? How old is it?
Do you know about Salvatore's rrdtool scripts for monitoring
LVS (if you want monitoring, rather than snmp)?

> ld: lvs.o: relocation R_X86_64_32 against `a local symbol' can not be
> used when making a shared object; recompile with -fPIC
> lvs.o: could not read symbols: Bad value
> make: *** [lvs.so] Error 1
> rm lvs.o
>
> As far as I can see the -fPIC option is enabled on these files? Or is it
> related to the compilation of net-snmp (which was from RPM)?

I take it that this is a 64 bit machine. Are you mixing 32
and 64 bit object files? (I expect you know enough not to
have done this).

Joe

--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!

_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@...
Send requests to lvs-users-request@...
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

[lists-95]

Joe,

Hi, hope you are well.



> I may be talking through my hat here...
>
>  
Don't we all.
> Is anyone maintaining the lvs snmp module? How old is it?
>  
Pretty old, but last time I compiled it on 32bit it worked fine.
> Do you know about Salvatore's rrdtool scripts for monitoring
> LVS (if you want monitoring, rather than snmp)?
>
>  
Yes, I'm using Salvatore's scripts as well which are great, but wanted
snmp as well.

>> ld: lvs.o: relocation R_X86_64_32 against `a local symbol' can not be
>> used when making a shared object; recompile with -fPIC
>> lvs.o: could not read symbols: Bad value
>> make: *** [lvs.so] Error 1
>> rm lvs.o
>>
>> As far as I can see the -fPIC option is enabled on these files? Or is it
>> related to the compilation of net-snmp (which was from RPM)?
>>    
>
> I take it that this is a 64 bit machine. Are you mixing 32
> and 64 bit object files? (I expect you know enough not to
> have done this).
>
>  

Err... probably, I'm not exactly a guru on this kind of thing, I think
the make files are picking up uname -m which should work.

This is really bugging me so I'm happy to pay someone to help (but
everyone seems to be reluctant to take money on this list ! strange folk.)

Regards,
Malcolm.







_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@...
Send requests to lvs-users-request@...
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

[Michael Moody-2]

Hi, and haha, I'd take money.

Anyways, yes, I've gotten this to work, centos/something else is
irrelevant. Had the same problem.

My solution was, for the ipvsadm source, in the libipvs directory,
change the makefile.

This line:

CFLAGS          = -Wall -Wunused -Wstrict-prototypes -g -O2

To this:

CFLAGS          = -Wall -Wunused -Wstrict-prototypes -g -O2 -fPIC

Then remake, and copy the libipvs directory over, and it should work
correctly.

Thanks,
Michael

lists wrote:

> <div class="moz-text-flowed" style="font-family: -moz-fixed">Joe,
>
> Hi, hope you are well.
>
>
>
>> I may be talking through my hat here...
>>
>>  
> Don't we all.
>> Is anyone maintaining the lvs snmp module? How old is it?
>>  
> Pretty old, but last time I compiled it on 32bit it worked fine.
>> Do you know about Salvatore's rrdtool scripts for monitoring
>> LVS (if you want monitoring, rather than snmp)?
>>
>>  
> Yes, I'm using Salvatore's scripts as well which are great, but wanted
> snmp as well.
>>> ld: lvs.o: relocation R_X86_64_32 against `a local symbol' can not be
>>> used when making a shared object; recompile with -fPIC
>>> lvs.o: could not read symbols: Bad value
>>> make: *** [lvs.so] Error 1
>>> rm lvs.o
>>>
>>> As far as I can see the -fPIC option is enabled on these files? Or
>>> is it
>>> related to the compilation of net-snmp (which was from RPM)?
>>>    
>>
>> I take it that this is a 64 bit machine. Are you mixing 32 and 64 bit
>> object files? (I expect you know enough not to have done this).
>>
>>  
> Err... probably, I'm not exactly a guru on this kind of thing, I think
> the make files are picking up uname -m which should work.
>
> This is really bugging me so I'm happy to pay someone to help (but
> everyone seems to be reluctant to take money on this list ! strange
> folk.)
>
> Regards,
> Malcolm.
>
>
>
>
>
>
>
>
> </div>

--

Michael S. Moody
Sr. Systems Engineer
Global Systems Consulting
Direct: [phone]
Web: http://www.GlobalSystemsConsulting.com

Engineering Support: support@...
Billing Support: billing@...
Customer Support Portal:  http://my.gsc.cc


NOTICE - This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message, you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error, please immediately notify Global Systems Consulting, its subsidiaries or associates. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the view of Global Systems Consulting, its subsidiaries and associates.


_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@...
Send requests to lvs-users-request@...
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

[lists-95]

Michael,

You star! thanks... (will double check tomorrow but I'm sure thats it.)
True to my word, we can negotiate a pay packet offlist.

For info on the list - I've just installed a full Centos5/i686 32bit
environment and the snmp/lvs compile worked first time...
So I assume that it must just be any 64bit platform that has this issue?




Michael Moody wrote:

> Hi, and haha, I'd take money.
>
> Anyways, yes, I've gotten this to work, centos/something else is
> irrelevant. Had the same problem.
>
> My solution was, for the ipvsadm source, in the libipvs directory,
> change the makefile.
>
> This line:
>
> CFLAGS          = -Wall -Wunused -Wstrict-prototypes -g -O2
>
> To this:
>
> CFLAGS          = -Wall -Wunused -Wstrict-prototypes -g -O2 -fPIC
>
> Then remake, and copy the libipvs directory over, and it should work
> correctly.
>
> Thanks,
> Michael
>
>  
>
>  

_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@...
Send requests to lvs-users-request@...
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

[Joseph Mack]

On Mon, 11 Feb 2008, lists wrote:

> For info on the list - I've just installed a full Centos5/i686 32bit
> environment and the snmp/lvs compile worked first time...
> So I assume that it must just be any 64bit platform that has this issue?

AFAIK

-fPIC is a flag neccessary to build a shared library (I
don't know all the details, I just follow recipes). If the
32 bit build is without the -fPIC then it's building a
static library, and the other parts of the build will be
making object files for a static library. That it didn't
work on the 64bit machine must mean that some other part of
the build is working towards a shared library (why static
for 32 bit and shared for 64 bit I don't know - you'll have
to spelunk the build scripts). The failure has nothing to do
with 64/32 bit.

Joe

--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!

_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@...
Send requests to lvs-users-request@...
or go to http://lists.graemef.net/mailman/listinfo/lvs-users