Dropsafe

by Alec Muffett

Simple Aspell Problem Resolution

Problem:

# aspell
ld.so.1: aspell: fatal: relocation error: file /opt/csw/bin/aspell: symbol _ZTVN7acommon6StringE: referenced symbol not found
Killed

Resolution:

# env LD_LIBRARY_PATH=/opt/csw/lib:$LD_LIBRARY_PATH aspell
Usage: aspell [options] <command>
<command> is one of:
-?|usage display a brief usage message
help display a detailed help message
-c|check <file> to check a file
-a|pipe “ispell -a” compatibility mode
[dump] config dumps the current configuration to stdout
config <key> prints the current value of an option
[dump] dicts | filters | modes
lists available dictionaries / filters / filter modes
[options] is any of the following:
–encoding=<str> encoding to expect data to be in
–mode=<str> filter mode
-l,–lang=<str> language code
-d,–master=<str> base name of the main dictionary to use
–sug-mode=<str> suggestion mode

Summary:

Check your shared library loading path.

⊞

Comments

4 responses to “Simple Aspell Problem Resolution”

  1. Mark J Musante
    re: Simple Aspell Problem Resolution

    I’ve a friend named Bob Aspell. I’ll warn him about this when he gets ready to start forking.

    Reply
  2. Stephen Usher
    re: Simple Aspell Problem Resolution

    You’ve been using Solaris for how long? And you’ve only just discovered this?!

    Reply
  3. alecm
    re: Simple Aspell Problem Resolution

    >You’ve been using Solaris for how long?

    Erm, if you include SunOS4.1, approximately 17 years.

    >And you’ve only just discovered this?!

    Yes. Before now I’ve compiled “ispell” rather than import some beta-test software from a third-party open-source software repository the which causes repeated and annoying library clashes and filename conflicts with core Solaris.

    Reply
  4. Stephen Usher
    re: Simple Aspell Problem Resolution

    You’ve been really-really lucky then.

    I guess that’s you’ve always unsetenv’d LD_LIBRARY_PATH and LD_RUN_PATH before compilation (so that the Solaris linker in takes notice of the -R flags on the command line under certain Solaris versions) and have just compiled your own code rather than try to use the crud from Solaris Freeware site.

    SunOS 4.x.x was far simpler. You’d just edit /etrc/ld.so.config and run ldconfig then the runtime linker would know where to look.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

More posts