Guest xionmark Posted October 13, 2005 Share Posted October 13, 2005 Greetings fellow coders, I'm getting a loader error when trying to compile the Cleave SOP on FC2, hcustom claims it can't find libGLU, yet the lib is installed on the machine. [mstory@troll100 cleave]$ hcustom -L /usr/X11R6/lib/ -i . SOP_Cleave.C Install directory = '.' Making SOP_Cleave.o and ./SOP_Cleave.so from SOP_Cleave.C SOP_Cleave.C: In member function `virtual void OP_CleaveOperator::getOperatorHelp(const char*, UT_String&, int) const': SOP_Cleave.C:79: warning: unused parameter `int level' SOP_Cleave.C: In member function `virtual OP_ERROR SOP_Cleave::cookMySop(OP_Context&)': SOP_Cleave.C:206: warning: unused variable `GEO_Vertex*vtx' SOP_Cleave.C:207: warning: unused variable `GEO_Point*pnt' /usr/bin/ld: cannot find -lGLU collect2: ld returned 1 exit status [mstory@troll100 cleave]$ [mstory@troll100 cleave]$ hcustom -L /usr/lib/ -i . SOP_Cleave.C Install directory = '.' Making SOP_Cleave.o and ./SOP_Cleave.so from SOP_Cleave.C SOP_Cleave.C: In member function `virtual void OP_CleaveOperator::getOperatorHelp(const char*, UT_String&, int) const': SOP_Cleave.C:79: warning: unused parameter `int level' SOP_Cleave.C: In member function `virtual OP_ERROR SOP_Cleave::cookMySop(OP_Context&)': SOP_Cleave.C:206: warning: unused variable `GEO_Vertex*vtx' SOP_Cleave.C:207: warning: unused variable `GEO_Point*pnt' /usr/bin/ld: cannot find -lGLU collect2: ld returned 1 exit status Yet when I search for the lib .. [mstory@troll100 cleave]$ locate libGLU /var/spool/up2date/xorg-x11-Mesa-libGLU-6.7.0-14.i386.rpm /usr/X11R6/lib/libGLU.so.1.3 /usr/X11R6/lib/libGLU.so.1 /usr/lib/libGLU.so.1 Houdini Version 8.0.383 [mstory@troll100 cleave]$ uname -a Linux troll100.charlex.com 2.6.10-1.771_FC2smp #1 SMP Mon Mar 28 Any ideas? TIA! --Mark Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted October 14, 2005 Share Posted October 14, 2005 Forgot to mention that I started by trying to compile in the normal way, without specifying a library path at all, e.g.: [mstory@troll100 cleave]$ hcustom -i . SOP_Cleave.C Install directory = '.' Making SOP_Cleave.o and ./SOP_Cleave.so from SOP_Cleave.C SOP_Cleave.C: In member function `virtual void OP_CleaveOperator::getOperatorHelp(const char*, UT_String&, int) const': SOP_Cleave.C:79: warning: unused parameter `int level' SOP_Cleave.C: In member function `virtual OP_ERROR SOP_Cleave::cookMySop(OP_Context&)': SOP_Cleave.C:206: warning: unused variable `GEO_Vertex*vtx' SOP_Cleave.C:207: warning: unused variable `GEO_Point*pnt' /usr/bin/ld: cannot find -lGLU collect2: ld returned 1 exit status Would anyone have an idea why hcustom can't find the GL library? ---Mark Quote Link to comment Share on other sites More sharing options...
rjpieke Posted October 14, 2005 Share Posted October 14, 2005 [mstory@troll100 cleave]$ locate libGLU /var/spool/up2date/xorg-x11-Mesa-libGLU-6.7.0-14.i386.rpm /usr/X11R6/lib/libGLU.so.1.3 /usr/X11R6/lib/libGLU.so.1 /usr/lib/libGLU.so.1 Hmm ... I think you might also need a /usr/lib/libGLU.so symlink. At least, that's the only difference I see between your printout and what's on my box. Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted October 14, 2005 Share Posted October 14, 2005 Hmm ... I think you might also need a /usr/lib/libGLU.so symlink. At least, that's the only difference I see between your printout and what's on my box. 21870[/snapback] Hi Robert, I checked and this is what's installed: [root@troll100 lib]# ll /usr/X11R6/lib/libGLU.so.1.3 -rwxr-xr-x 1 root root 498756 Mar 24 2005 /usr/X11R6/lib/libGLU.so.1.3 [root@troll100 lib]# ll /usr/X11R6/lib/libGLU.so.1 lrwxrwxrwx 1 root root 13 Sep 20 10:42 /usr/X11R6/lib/libGLU.so.1 -> libGLU.so.1.3 [root@troll100 lib]# ll /usr/lib/libGLU.so.1 lrwxrwxrwx 1 root root 31 Sep 20 10:42 /usr/lib/libGLU.so.1 -> ../../usr/X11R6/lib/libGLU.so.1 So they all point to: /usr/X11R6/lib/libGLU.so.1.3 which I would think is correct. I have an FC2 machine at home and it compiles fine, but it's a 2.6.5-1.358 kernel, can't imagine why this would be happening on a machine with the 2.6.10-1.771 kernel. The libs appears to be the same, same file name, same byte count. I also tried compiling the SOP_Star.C example for a sanity check, no go, same errors. Hmmm ... just tried on an FC2 machine here at the shop that's running the same kernel as I have at home, 2.6.5-1.358, and I get the same error. Now I'm suspecting there's something up with the release, houdini-8.0.360-linux_rh9.tar.gz. Can you compile on a FC2 machine with H8.0.383? Perplexed. --Mark Quote Link to comment Share on other sites More sharing options...
rjpieke Posted October 14, 2005 Share Posted October 14, 2005 Hi Robert,I checked and this is what's installed: [root@troll100 lib]# ll /usr/X11R6/lib/libGLU.so.1.3 -rwxr-xr-x 1 root root 498756 Mar 24 2005 /usr/X11R6/lib/libGLU.so.1.3 [root@troll100 lib]# ll /usr/X11R6/lib/libGLU.so.1 lrwxrwxrwx 1 root root 13 Sep 20 10:42 /usr/X11R6/lib/libGLU.so.1 -> libGLU.so.1.3 [root@troll100 lib]# ll /usr/lib/libGLU.so.1 lrwxrwxrwx 1 root root 31 Sep 20 10:42 /usr/lib/libGLU.so.1 -> ../../usr/X11R6/lib/libGLU.so.1 So they all point to: /usr/X11R6/lib/libGLU.so.1.3 which I would think is correct. I have an FC2 machine at home and it compiles fine, but it's a 2.6.5-1.358 kernel, can't imagine why this would be happening on a machine with the 2.6.10-1.771 kernel. The libs appears to be the same, same file name, same byte count. I also tried compiling the SOP_Star.C example for a sanity check, no go, same errors. Hmmm ... just tried on an FC2 machine here at the shop that's running the same kernel as I have at home, 2.6.5-1.358, and I get the same error. Now I'm suspecting there's something up with the release, houdini-8.0.360-linux_rh9.tar.gz. Can you compile on a FC2 machine with H8.0.383? Perplexed. --Mark 21871[/snapback] Unfortunately, I don't have access to the same machine configuration, but try making a libGLU.so link that points to libGLU.so.1 : cd /usr/lib : ln -s libGLU.so.1 libGLU.so As mentioned, that's the first difference I see between what's on your machine and what's on mine. Quote Link to comment Share on other sites More sharing options...
rjpieke Posted October 14, 2005 Share Posted October 14, 2005 Unfortunately, I don't have access to the same machine configuration, but try making a libGLU.so link that points to libGLU.so.1: cd /usr/lib : ln -s libGLU.so.1 libGLU.so As mentioned, that's the first difference I see between what's on your machine and what's on mine. 21872[/snapback] Yeah, definitely try that. I tried removing my libGLU.so link and started getting the same errors you mentioned. Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted October 14, 2005 Share Posted October 14, 2005 Unfortunately, I don't have access to the same machine configuration, but try making a libGLU.so link that points to libGLU.so.1: cd /usr/lib : ln -s libGLU.so.1 libGLU.so As mentioned, that's the first difference I see between what's on your machine and what's on mine. 21872[/snapback] OK, I tried that and still the same error. My memory may be foggy but I didn't think that kind of linking is needed, as the loader can figure it out for itself. I did an "objdump" on the libGLU.so and it appears healthy on both machines. I'm curious, what kernel and version of Houdini are you using? This was all working as recently as H8.0.360 --Mark Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted October 14, 2005 Share Posted October 14, 2005 Yeah, definitely try that. I tried removing my libGLU.so link and started getting the same errors you mentioned. 21873[/snapback] OK, I'll try again ... It must be right under my nose ... Quote Link to comment Share on other sites More sharing options...
rjpieke Posted October 14, 2005 Share Posted October 14, 2005 OK, I tried that and still the same error. My memory may be foggy but I didn't think that kind of linking is needed, as the loader can figure it out for itself. I did an "objdump" on the libGLU.so and it appears healthy on both machines. I'm curious, what kernel and version of Houdini are you using? This was all working as recently as H8.0.360 --Mark 21874[/snapback] Houdini 8.0.383 Linux 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005 i686 athlon i386 GNU/Linux : ll /usr/lib/libGLU* -rw-r--r-- 1 root root 682194 2005-09-12 19:23 /usr/lib/libGLU.a lrwxrwxrwx 1 root root 13 2005-10-11 14:56 /usr/lib/libGLU.so -> libGLU.so.1.3 lrwxrwxrwx 1 root root 13 2005-10-11 12:43 /usr/lib/libGLU.so.1 -> libGLU.so.1.3 -rwxr-xr-x 1 root root 523632 2005-09-12 19:26 /usr/lib/libGLU.so.1.3 As mentioned, if I get rid ot the libGLU.so -> libGLU.so.1.3 link, I start getting the same errors you mentioned. Quote Link to comment Share on other sites More sharing options...
Guest xionmark Posted October 14, 2005 Share Posted October 14, 2005 Yeah, definitely try that. I tried removing my libGLU.so link and started getting the same errors you mentioned. 21873[/snapback] OK, that *did* seem to help, but now ld can't find X11! This is weird, it's a very recent install of FC2. [mstory@troll100 SOP]$ hcustom -i . SOP_Star.C Install directory = '.' Making SOP_Star.o and ./SOP_Star.so from SOP_Star.C /usr/bin/ld: cannot find -lX11 collect2: ld returned 1 exit status So I had to add the following links: [root@troll100 lib]# ln -s libX11.so.6.2 libX11.so [root@troll100 lib]# ln -s libXext.so.6.4 libXext.so [root@troll100 lib]# ln -s libXi.so.6.0 libXi.so I wonder why those links weren't created then the system was built ... very strange. Thanks for your help! --Mark Quote Link to comment Share on other sites More sharing options...
rjpieke Posted October 14, 2005 Share Posted October 14, 2005 OK, that *did* seem to help. . . Thanks for your help! --Mark 21877[/snapback] You're welcome! The machine I'm currently testing on is a SUSE10 box. I found it was easier to get going than Fedora Core 4 (for starters, it properly identified all the hardware, which certainly saves some configuration time). Cheers! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.