public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Mills <Jmills@TGA.com>
To: 'eCos Discussion' <ecos-discuss@sourceware.cygnus.com>
Cc: John Mills <Jmills@TGA.com>
Subject: [ECOS] Library Circularity Question
Date: Wed, 07 Jul 1999 15:34:00 -0000	[thread overview]
Message-ID: <FD7521AABD30D2118284006008AE0B6E03BFC0@ns1.tga.com> (raw)

I ran into something I don't understand while linking a "toy" C++ example as
a sh-elf executable. I am using sh-hms libraries built out of
'ecosSWtools-990319', and targeting the Hitachi EDK7045F development board.

Originally I provided a dummy 'delete' operator to satisfy linkage of a
pro-forma C++ destructor. The problem came up when I tried to find a linkage
sequence which would actually implement some dynamic storage allocation and
deallocation. Linking with "-lgcc"
[from "<tooldir>/lib/gcc-lib/sh-hms/2.9-ecosSWtools-990310/libgcc.a"] left
unresolved symbols; adding a trailing link command "-lc" didn't resolve all;
but adding a _second_ "-lgcc" after "-lc" resolved all symbols:
    $(XLD) $(LDFLAGS) -o $@ ${OBJS} -lgcc -lc -lgcc

Any suggestions what is happening here?

Thanks -

  John Mills, Sr. Software Engineer
  TGA Technologies, Inc.
  100 Pinnacle Way, Suite 140
  Norcross, GA 30071-3633
  e-mail: jmills@tga.com
  Phone: 770-421-2100 ext.124 (voice)
         770-449-7740 (FAX)

             reply	other threads:[~1999-07-07 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-07 15:34 John Mills [this message]
1999-07-07 15:49 ` Erik Horstkotte
1999-07-07 15:49 Timothy Konkle

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=FD7521AABD30D2118284006008AE0B6E03BFC0@ns1.tga.com \
    --to=jmills@tga.com \
    --cc=ecos-discuss@sourceware.cygnus.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).