public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "dale henderson" <dalekh@hotmail.com>
To: cygwin@sourceware.cygnus.com
Subject: Undefined Reference
Date: Mon, 17 May 1999 16:53:00 -0000	[thread overview]
Message-ID: <19990517235241.69667.qmail@hotmail.com> (raw)

Here is my scenario:

I have mingw32/egcs1.1.2

Compiling source file for an executable.
There are two static libraries: one libglcanvas.a makes reference to the 
other libopengl32.a.
The source file  penguin.cpp also makes reference to libopengl32.a and does 
so successfully when make does the linking, but the linking to libopengl32.a 
from libglcanvas.a fails causing undefined references.

The source file uses makeprog.g95. When libglcanvas.a was compiled, it used 
makelib.g95. This is the only discernable difference I see.
There is no linking involved when creating a static library in mingw32, 
correct?

Any suggestions?

dalehend@netscape.net









_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: "dale henderson" <dalekh@hotmail.com>
To: cygwin@sourceware.cygnus.com
Subject: Undefined Reference
Date: Mon, 31 May 1999 21:10:00 -0000	[thread overview]
Message-ID: <19990517235241.69667.qmail@hotmail.com> (raw)
Message-ID: <19990531211000.XQr8tC6I4q_gTheWMkqaw6tetOqJ4o4fG_7wBAHXsp8@z> (raw)

Here is my scenario:

I have mingw32/egcs1.1.2

Compiling source file for an executable.
There are two static libraries: one libglcanvas.a makes reference to the 
other libopengl32.a.
The source file  penguin.cpp also makes reference to libopengl32.a and does 
so successfully when make does the linking, but the linking to libopengl32.a 
from libglcanvas.a fails causing undefined references.

The source file uses makeprog.g95. When libglcanvas.a was compiled, it used 
makelib.g95. This is the only discernable difference I see.
There is no linking involved when creating a static library in mingw32, 
correct?

Any suggestions?

dalehend@netscape.net









_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~1999-05-17 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-17 16:53 dale henderson [this message]
1999-05-31 21:10 ` dale henderson
     [not found] <1dbb5dd90906251156v6fec5ffbx749d7d0ce7914b07@mail.gmail.com>
2009-06-26 14:14 ` Fwd: undefined reference Winderson Martins de Souza
2009-06-27  1:20   ` Sisyphus
2009-07-01 13:54     ` Winderson Martins de Souza
  -- strict thread matches above, loose matches on Subject: below --
1997-10-13 19:00 Tim Newsham
1997-10-14  4:29 ` Gunther Ebert
1997-10-14 19:54   ` Tim Newsham

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=19990517235241.69667.qmail@hotmail.com \
    --to=dalekh@hotmail.com \
    --cc=cygwin@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).