From: Rocky Bernstein <rocky@gnu.org>
To: cygwin@cygwin.com
Subject: How does one make a bash "builtin" (shared loadable module) on cygwin
Date: Wed, 18 May 2011 22:47:00 -0000 [thread overview]
Message-ID: <BANLkTint0SzMJBOq=gS9kpK6MWktuSKt6w@mail.gmail.com> (raw)
I am trying to build a bash "builtin" (a dynamically loadable bash
module) on cygwin. Here's the error message I get via automake/make:
$ make
gcc -g -O2 -o set0.exe -shared set0-set0.o
set0-set0.o: In function `set0_builtin':
/tmp/bashdb/builtin/set0.c:46: undefined reference to `_builtin_error'
/tmp/bashdb/builtin/set0.c:47: undefined reference to `_builtin_usage'
/tmp/bashdb/builtin/set0.c:51: undefined reference to `_dollar_vars'
/tmp/bashdb/builtin/set0.c:52: undefined reference to `_xmalloc'
/tmp/bashdb/builtin/set0.c:52: undefined reference to `_dollar_vars'
/tmp/bashdb/builtin/set0.c:42: undefined reference to `_builtin_error'
/tmp/bashdb/builtin/set0.c:43: undefined reference to `_builtin_usage'
collect2: ld returned 1 exit status
make: *** [set0.exe] Error 1
The complete Makefile.am and code is listed at
http://bashdb.git.sourceforge.net/git/gitweb.cgi?p=bashdb/bashdb;a=tree;f=builtin;h=428fd8f3598c88eabb10b3ba800fb900da9f858c;hb=HEAD
Perhaps I need to tell cygwin that these symbols are supposed to be
undefined since they are part of bash?
I've tried looking at gcc documentation for linker options but it's
all a mystery to me.
Thanks in advance for help, suggestions or links to documentation.
Regards,
rocky
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2011-05-18 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 22:47 Rocky Bernstein [this message]
2011-05-19 1:24 ` Larry Hall (Cygwin)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTint0SzMJBOq=gS9kpK6MWktuSKt6w@mail.gmail.com' \
--to=rocky@gnu.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).