From: kunal chavan <kunal@deeproot.co.in>
To: gcc-help@gcc.gnu.org
Subject: Library linking squence
Date: Sun, 21 Sep 2003 19:32:00 -0000 [thread overview]
Message-ID: <3F6DFD8F.3030605@deeproot.co.in> (raw)
Hello list
I have been using gcc for many days, i have created my own C API
libraries for parsing confugration files like squidGuard.conf and
fetchmailrc (using flex and bison) etc. All these work fine when linked
with single executable.
Now when i link these libraries to my Kylix C++ application (Kylix is an
IDE for developing GUI which users all these API's) what happens is the
function parse_squidguardconf in library which is linked first works
fine but another function parse_fetchmailconf which is in library linked
after the first library gives me parse error and when i change the
linking sequence same thing happens vise-versa (i.e parse_fetchmailconf
works fine but parse_squidguardconf gives parse error).
Thanks in advance for any help suggestion.
Kunal.
reply other threads:[~2003-09-21 19:32 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=3F6DFD8F.3030605@deeproot.co.in \
--to=kunal@deeproot.co.in \
--cc=gcc-help@gcc.gnu.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).