Re: anyone seeing "dyld: Symbol not found: _program_name"

[Ben Abbott]

On Feb 5, 2010, at 9:31 AM, Ben Abbott wrote:

> On Feb 5, 2010, at 1:53 AM, John W. Eaton wrote:
> 
>> On  4-Feb-2010, Ben Abbott wrote:
>> 
>> | I've built with the current sources. Running in gdb, I see ...
>> | 
>> | dyld: Symbol not found: _program_name
>> |   Referenced from: 
>> /Users/bpabbott/Development/mercurial/local_clone/liboctave/.libs/liboctave-3.3.50+.dylib
>> |   Expected in: flat namespace
>> |  in 
>> /Users/bpabbott/Development/mercurial/local_clone/liboctave/.libs/liboctave-3.3.50+.dylib
>> | 
>> | Program received signal SIGTRAP, Trace/breakpoint trap.
>> | 0x8fe01065 in __dyld_dyld_fatal_error ()
>> | (gdb) bt
>> | #0  0x8fe01065 in __dyld_dyld_fatal_error ()
>> | #1  0x8fe04fa5 in __dyld__ZN4dyld4haltEPKc ()
>> | #2  0x8fe0796b in __dyld__ZN4dyld5_mainEPK12macho_headermiPPKcS5_S5_ ()
>> | #3  0x8fe018b1 in __dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKcl ()
>> | #4  0x8fe01057 in __dyld__dyld_start ()
>> | 
>> | Is anyone else seeing this.
>> 
>> Does adding the progname module to th gnulib_modules list in the
>> bootstrap.conf file solve this problem for you?  If so, it would be
>> good to know which module in gnulib is using this symbol but not
>> listing the progname module as a dependency.
>> 
>> jwe
> 
> Adding progname to the gnulib_modules list resulted in a successful build.
> 
> However, ...
> 
>       octave:1> cd test
>       octave:2> fntests
> 
>       Integrated test scripts:
> 
>       `lstat' undefined near line 100 column 20
> 
> I'll look into which module depends upon progname.
> 
> Ben


Regarding lstat ...

$ nm libgnu/.libs/lstat.o 
         U ___error
         U _lstat$INODE64
000000ab t _orig_lstat
00000000 T _rpl_lstat
         U _rpl_stat
         U _strlen

Regarding progname, I found the thread below ...

        http://osdir.com/ml/lib.gnulib.bugs/2004-08/msg00093.html

... which indicates the error module requires progname. Looking at 
libgnu/.libs/error.o ...

$ nm libgnu/.libs/error.o
         U ___stack_chk_fail
         U ___stack_chk_guard
         U ___stderrp
         U ___stdoutp
00000144 T _error
0000021b T _error_at_line
00001464 S _error_message_count
00001468 S _error_one_per_line
00001460 S _error_print_progname
000000b0 t _error_tail
         U _exit
         U _fflush
         U _fileno
000001c4 t _flush_stdout
         U _fprintf
0000145c b _old_file_name.4690
00001458 b _old_line_number.4691
00000000 t _print_errno_message
         U _program_name
         U _putc
         U _rpl_fcntl
         U _strcmp
         U _strerror_r
         U _vfprintf    

The xgetcwd module apparently depends on the error module.

$ nm xgetcwd.o
         U ___error
         U _rpl_getcwd
         U _xalloc_die
00000000 T _xgetcwd

... and xgetcwd depends upon getpwd

$ nm xgetcwd.o 
         U ___error
         U _rpl_getcwd
         U _xalloc_die
00000000 T _xgetcwd

I wish I could be more helpful with this rpl_ stuff, but I have no insight into 
this.

Ben