链接时出现ptritclStubsPtr未定义引用问题求助

Your Error Details #

You're encountering undefined reference errors for ptritclStubsPtr during linking:

../build/kl/Release/test/maker/guibase.o: In function `decodeAddrList': tree234.c:(.text+0xc): undefined reference to `ptritclStubsPtr' tree234.c:(.text+0x20): undefined reference to `ptritclStubsPtr' tree234.c:(.text+0x12c): undefined reference to `ptritclStubsPtr' tree234.c:(.text+0x140): undefined reference to `ptritclStubsPtr'

Your build command is:

pkgs/gcc/v4.8.3/bin/gcc -L/usr/X11R6/lib -O2 -DUSE_FLEX -Wall -Wno-char-subscripts -fPIC -DLINUX -DG_DISABLE_CONST_RETURNS -fno-strict-aliasing -o ../build/kl/Release/test/bin/pure.exe -L../build/kl/Release/test/modules ../build/kl/Release/test/maker/constrfunc.TCL.o ../../build/kl/Release/test/maker/pvdbprocs.TCL.o .. ../build/kl/Release/test/maker/maker/memmaker.TCL.o .. ../build/kl/Release/test/maker/modules/libdenbase.a .. ../build/kl/Release/test/maker/guibase.o -lcdnviptcl8.4 -ldenbase -lglib-2.0 -ldenbase -lX11 -ldl -lm -lviputil -lvippli -lcdsCommonMT_sh -lpthread -L/home/dlb/extlibs/arm/lib

And you've confirmed ptritclStubsPtr exists in /home/dlb/extlibs/arm/lib/libcdnviptcl8.4.so:

636: 00000000000d8068 8 OBJECT GLOBAL DEFAULT 24 itclStubsPtr 1240: 00000000000d8068 8 OBJECT GLOBAL DEFAULT 24 ptritclStubsPtr

Let's walk through the most likely fixes for your issue—since the symbol exists in the library, the problem is almost certainly with how the linker processes your command or files.

1. Fix the Linker Order (Most Common Culprit) #

GCC's linker processes object files and libraries in the exact order they appear on the command line. If an object file needs symbols from a library, the library must come after the object file in the command.

Looking at your build command, guibase.o (which contains the decodeAddrList function calling ptritclStubsPtr) is listed before -lcdnviptcl8.4. The linker hasn't seen the library yet when it processes guibase.o, so it can't resolve the symbol.

Adjust your command to move -lcdnviptcl8.4 right after guibase.o (I also cleaned up stray .. entries that looked like typos):

pkgs/gcc/v4.8.3/bin/gcc -L/usr/X11R6/lib -O2 -DUSE_FLEX -Wall -Wno-char-subscripts -fPIC -DLINUX -DG_DISABLE_CONST_RETURNS -fno-strict-aliasing -o ../build/kl/Release/test/bin/pure.exe -L../build/kl/Release/test/modules ../build/kl/Release/test/maker/constrfunc.TCL.o ../../build/kl/Release/test/maker/pvdbprocs.TCL.o ../build/kl/Release/test/maker/maker/memmaker.TCL.o ../build/kl/Release/test/maker/modules/libdenbase.a ../build/kl/Release/test/maker/guibase.o -lcdnviptcl8.4 -ldenbase -lglib-2.0 -ldenbase -lX11 -ldl -lm -lviputil -lvippli -lcdsCommonMT_sh -lpthread -L/home/dlb/extlibs/arm/lib

2. Ensure the Linker Finds the Correct Library #

You added -L/home/dlb/extlibs/arm/lib at the end of your command. GCC searches for libraries in the order of -L flags, so if there's another libcdnviptcl8.4.so or .a in an earlier path (like ../build/kl/Release/test/modules), the linker will pick that one first—and it might not have the ptritclStubsPtr symbol.

Fix this in one of two ways:

• Move -L/home/dlb/extlibs/arm/lib to the front of all -L flags so it's searched first:

  pkgs/gcc/v4.8.3/bin/gcc -L/home/dlb/extlibs/arm/lib -L/usr/X11R6/lib -O2 -DUSE_FLEX -Wall -Wno-char-subscripts -fPIC -DLINUX -DG_DISABLE_CONST_RETURNS -fno-strict-aliasing -o ../build/kl/Release/test/bin/pure.exe -L../build/kl/Release/test/modules ../build/kl/Release/test/maker/constrfunc.TCL.o ../../build/kl/Release/test/maker/pvdbprocs.TCL.o ../build/kl/Release/test/maker/maker/memmaker.TCL.o ../build/kl/Release/test/maker/modules/libdenbase.a ../build/kl/Release/test/maker/guibase.o -lcdnviptcl8.4 -ldenbase -lglib-2.0 -ldenbase -lX11 -ldl -lm -lviputil -lvippli -lcdsCommonMT_sh -lpthread
  

• Or, use the full path to the library instead of -l to eliminate ambiguity:

  pkgs/gcc/v4.8.3/bin/gcc -L/usr/X11R6/lib -O2 -DUSE_FLEX -Wall -Wno-char-subscripts -fPIC -DLINUX -DG_DISABLE_CONST_RETURNS -fno-strict-aliasing -o ../build/kl/Release/test/bin/pure.exe -L../build/kl/Release/test/modules ../build/kl/Release/test/maker/constrfunc.TCL.o ../../build/kl/Release/test/maker/pvdbprocs.TCL.o ../build/kl/Release/test/maker/maker/memmaker.TCL.o ../build/kl/Release/test/maker/modules/libdenbase.a ../build/kl/Release/test/maker/guibase.o /home/dlb/extlibs/arm/lib/libcdnviptcl8.4.so -ldenbase -lglib-2.0 -ldenbase -lX11 -ldl -lm -lviputil -lvippli -lcdsCommonMT_sh -lpthread
  

3. Check for Architecture Mismatches #

Since your library is in an ARM-specific path, make sure your compiled object files (like guibase.o) match the library's architecture. Mismatched 32-bit/64-bit or ARM variants can prevent the linker from resolving symbols, even if they exist.

Run these commands to verify:

# Check architecture of guibase.o
file ../build/kl/Release/test/maker/guibase.o

# Check architecture of the library
file /home/dlb/extlibs/arm/lib/libcdnviptcl8.4.so

The outputs should be identical (e.g., both ARM aarch64 or ARM 32-bit, hard-float). If they don't match, adjust your compiler flags to target the same architecture as the library.

4. Double-Check Symbol Exactness #

While you've already confirmed the symbol exists, double-check that the name matches exactly (case sensitivity matters, though that's unlikely here). Re-run:

readelf -s /home/dlb/extlibs/arm/lib/libcdnviptcl8.4.so | grep ptritclStubsPtr

Ensure the output shows the exact symbol name from your error message.

内容的提问来源于stack exchange，提问作者Harish Tadikamalla