Re: [Bashdb-help] bashdb-4.2-0.8 make errors under Mac OS X 10.6.8

[Rocky B. <ro...@gn...>]

I seem to recall that OSX uses this dynaloader thing for creating shared
libraries. See the last paragraph of the checked answer in

http://stackoverflow.com/questions/2339679/what-are-the-differences-between-so-and-dylib-on-osx

I don't have access to a computer runnng OSX to use to try to reproduce or
work up a solution. If you do work up a solution, consider sending a patch
or posting the solution here.

Finally, I should note that you don't have to compile with source to get
the large file speedup. That code is now was incorporated into bash 4.1 (and
persists in 4.2).  What compiling with the source will however do is allow
you and bashdb to change $0. In debugging at the outset via bashdb, usually
programmers would prefer $0 to refer to the program getting debugged instead
of bashdb.

On Fri, Sep 30, 2011 at 10:42 PM, John Purnell <joh...@gm...>wrote:

> bash --version
> GNU bash, version 4.2.10(1)-release (i386-apple-darwin10.8.0)
>
> When configuring bashbd with:
>
> ./configure --with-bash=/usr/local/bin/bash \
> --with-dbg-main=/Downloads/src/bashdb-4.2-0.8/dbg-main.sh \
> --with-bashdb-main=/Downloads/src/bashdb-4.2-0.8/bashdb-main.inc \
> && make && make check
>
> all is fine. But as soon as I use:
>
> ./configure --with-bash=/usr/local/bin/bash \
> --with-bash-src=/Downloads/src/bash-4.2.10 \
> --with-dbg-main=/Downloads/src/bashdb-4.2-0.8/dbg-main.sh \
> --with-bashdb-main=/Downloads/src/bashdb-4.2-0.8/bashdb-main.inc
>
> to get large input file support make fails with the following:
>
> Making all in builtin
> gcc -DHAVE_CONFIG_H -I. -I..    -I /Downloads/src/bash-4.2.10 -I
> /Downloads/src/bash-4.2.10/include
> -I/Downloads/src/bash-4.2.10/builtins  -g -O2 -MT set0-set0.o -MD -MP
> -MF .deps/set0-set0.Tpo -c -o set0-set0.o `test -f 'set0.c' || echo
> './'`set0.c
> mv -f .deps/set0-set0.Tpo .deps/set0-set0.Po
> gcc  -g -O2   -o set0 \
>            -shared set0-set0.o
> Undefined symbols:
>  "_dollar_vars", referenced from:
>      _set0_builtin in set0-set0.o
>  "_builtin_usage", referenced from:
>      _set0_builtin in set0-set0.o
>  "_builtin_error", referenced from:
>      _set0_builtin in set0-set0.o
>  "_xmalloc", referenced from:
>      _set0_builtin in set0-set0.o
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[2]: *** [set0] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> I see from a Google search that Rocky reported the same issue on
> 2011-05-18 when building to use the builtin under cygwin. Any ideas
> for a solution.
>
> Thanks
> John
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Bashdb-help mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashdb-help
>