Thanks, Dave. I ended up having to add a link in /usr/lib to /usr/local/lib/libopts.so.25.
Appreciate your effort in helping me out! Best, Geof ________________________________________ From: Dave Hart [daveh...@gmail.com] Sent: Thursday, March 24, 2011 9:05 PM To: Geof Sawaya Cc: autogen-us...@lists.sf.net Subject: Re: [Autogen-users] FW: problem with auto-opts definition element . . . On Fri, Mar 25, 2011 at 02:35 UTC, Geof Sawaya <geof.saw...@utah.edu> wrote: > However, I can't get autogen to run -- I'm wondering if you might have a > quick fix. (BTW, using Ubuntu 10.10 x64) > > Check this output: > > sawaya@ubuntu:~/installations/autogen/autogen-5.11.6$ which autogen > /usr/local/bin/autogen > sawaya@ubuntu:~/installations/autogen/autogen-5.11.6$ autogen > bash: /usr/bin/autogen: No such file or directory > sawaya@ubuntu:~/installations/autogen/autogen-5.11.6$ echo $PATH > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > sawaya@ubuntu:~/installations/autogen/autogen-5.11.6$ /usr/local/bin/autogen > /usr/local/bin/autogen: symbol lookup error: /usr/local/bin/autogen: > undefined symbol: option_char_category My hunch is your ld or ld.so isn't looking in /usr/local/lib or /usr/local/lib64 or wherever libopts.so.* was installed. Try: $ ldd /usr/local/bin/autogen /usr/local/bin/autogen: libopts.so.33 => /usr/local/lib/libopts.so.33 (0x28099000) [...] You probably have a "not found" or so after =>. I'm not an expert on shared libraries, I'm more familiar with how Windows DLLs are handled. But after flailing around a bit, I can throw some cheap hack ideas out there anyway while we await more informed wisdom. Figure out where autogen installed libopts.so.33 (I'm guessing /usr/local/lib but I'm also x64-naive). Try providing symlinks from places your distro likes better: ln -s /usr/local/lib/libopts.so.33 /usr/local/lib64 ln -s /usr/local/lib/libopts.so.33 /usr/local/lib64/libopts.so then rebuild your autogen binary and reinstall it, and try running it and/or using ldd to examine its shared library dependencies. If that doesn't work, you could try similar but dirtier (and sure to be broken by installing packaged autogen): ln -s /usr/local/lib/libopts.so.33 /usr/lib64 ln -s /usr/local/lib/libopts.so.33 /usr/lib64/libopts.so Note the lib64 instead of lib is a guess on my part, you should be able to determine which to use based on the other libraries you see referenced in ldd output. More generically, this is a question to pose to other users of Ubuntu: how do I configure and install tool overrides in /usr/local/* ? I can tell you I believe you will find you suffer from opposing strong wills :) Your distro may feel strongly that 64-bit libs belong in .../lib64, while autotools believes default-built shared libs go in /usr/local/lib, not /usr/local/lib64. Good luck, Dave Hart ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Autogen-users mailing list Autogen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/autogen-users