From: "Ken Yee" <kenkyee@excite.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] PPP auth.c doesn't compile/link?
Date: Wed, 29 Aug 2012 19:51:00 -0000 [thread overview]
Message-ID: <20120829155055.2474@web005.roc2.bluetie.com> (raw)
First thing I hit was that option_error wasn't defined, so I copied the macr=
o from pppd.c/ipcp.c but the macro takes one parameter while the calls in au=
th.c passed in multiple parameters, so I changed it to a straight mapping to=
the db_printf function.
Then I get these link errors:
ecos_install/lib/libtarget.a(net_ppp_auth.o): In function `cyg_ppp_auth_chec=
k_options':
/home/kenyee/ecos/packages/net/ppp/current/src/auth.c:619: undefined =
reference to `auth_req_info'
/home/kenyee/ecos/packages/net/ppp/current/src/auth.c:619: undefined =
reference to `devnam_info'
/home/kenyee/ecos/packages/net/ppp/current/src/auth.c:619: undefined =
reference to `connector_info'
/home/kenyee/ecos/packages/net/ppp/current/src/auth.c:619: undefined =
reference to `disconnector_info'
/home/kenyee/ecos/packages/net/ppp/current/src/auth.c:619: undefined =
reference to `welcomer_info'
collect2: ld returned 1 exit status
Looks like those variables existed in the 1.3 version added in 2004:
http://sourceware.org/ml/ecos-discuss/2004-07/txt00000.txt
But then they were taken out at some point and externs added to include/auth=
.h but grepping through the tree, I don't see where they're defined...
I worked around it by adding the same variable definitions from 1.3.
ken
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2012-08-29 19:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120829155055.2474@web005.roc2.bluetie.com \
--to=kenkyee@excite.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).