public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kayvan A. Sylvan" <kayvan@sylvan.com>
To: David Snopek <xevol@execpc.com>
Cc: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>,
	gcc-help@gcc.gnu.org
Subject: Re: Shared Libraries
Date: Sat, 08 Jul 2000 16:26:00 -0000	[thread overview]
Message-ID: <20000708162553.A13337@satyr.sylvan.com> (raw)
In-Reply-To: <3967B5C2.618B3AA1@execpc.com>

On Sat, Jul 08, 2000 at 06:14:10PM -0500, David Snopek wrote:
> I found the solution to the problem (or at least something that makes it
> go away) although I do not really understand it.  In all of my files I
> had "#pragma interface" in the header and "#pragma implementation" in
> the implementation.  I had read in the man pages for g++ that if you
> don't give "#pragma implementation" a header name then it will use the
> files name except with the *.h extension, so I didn't supply one because
> all of my files are named in this fashion.  In the midst of trying
> completely random things, I put the header names in.  And now it works
> perfectly.  I don;t know why, but for now I do not care.  Thanks for
> trying to help!!

I would like to know why this happens too, since I've been bitten by this
behavior as well.

Note also: The problem will go away with use of ``-O'' optimization. If
you use gcc's ``-g'' flag by itself, though, the linking problem
shows up.

-- 
Kayvan A. Sylvan                   | Proud husband of      | Father to my kids:
Sylvan Associates, Inc.            | Laura Isabella Sylvan | Katherine Yelena
http://www.successlinks.com/kayvan | Reach your goals now! | Robin Gregory

  reply	other threads:[~2000-07-08 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-08 11:10 David Snopek
2000-07-08 15:02 ` Martin v. Loewis
2000-07-08 16:16   ` David Snopek
2000-07-08 16:26     ` Kayvan A. Sylvan [this message]
2000-07-09  0:15     ` Martin v. Loewis
  -- strict thread matches above, loose matches on Subject: below --
1999-12-30  6:56 Shared libraries Coleman Baker
1999-12-31 22:24 ` Coleman Baker

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=20000708162553.A13337@satyr.sylvan.com \
    --to=kayvan@sylvan.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=martin@loewis.home.cs.tu-berlin.de \
    --cc=xevol@execpc.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).