linking and iostreams

linking and iostreams

[Greg Miller]

This program:

#include <iostream>

int main() {
  cout << "test" << endl;

  return 0;
}

compiles, links, and does what I expect when compiled with B20.1 and
egcs-1.1.1 using this command:

g++ test.c

but generates numerous undefined references during linking when compiled
with:

g++ -mno-cygwin test.c

Notably, it generates a number of references to "__errno" from
libstdc++.a, which, AFAIK, should not include ANY references to
"__errno" in the mingw-libs version.

So what am I doing wrong?
-- 
http://www.classic-games.com/
President Clinton was acquitted; then again, so was O. J. Simpson.
*** NEWBIES: Limit signatures to four lines! No HTML mail or posts! ***

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

Re: linking and iostreams

[Mumit Khan]

Greg Miller <gmiller@classic-games.com> writes:
> 
> This program:
> 
> #include <iostream>
> 
> int main() {
>   cout << "test" << endl;
> 
>   return 0;
> }
> 
> compiles, links, and does what I expect when compiled with B20.1 and
> egcs-1.1.1 using this command:
> 
> g++ test.c
> 
> but generates numerous undefined references during linking when compiled
> with:
> 
> g++ -mno-cygwin test.c

Please see my howto[1] on -mno-cygwin option. This issue has been discussed
in detail in this group, so the search engine is also a good option.

[1] http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
    http://www.delorie.com/howto/

Regards,
Mumit


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

Re: linking and iostreams

[Greg Miller]

Mumit Khan wrote:
> 
> Greg Miller <gmiller@classic-games.com> writes:
> > but generates numerous undefined references during linking when compiled
> > with:
> >
> > g++ -mno-cygwin test.c

Oops.. just noticed an error here... That should have been:

g++ -mno-cygwin test.c -L //d/cygnus/cygwinb20/mingw-libs

In any event, is it linking the wrong libstdc++.a despite the "-L"
switch? or is something else wrong?
-- 
http://www.classic-games.com/
President Clinton was acquitted; then again, so was O. J. Simpson.
*** NEWBIES: Limit signatures to four lines! No HTML mail or posts! ***

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

Re: linking and iostreams

[Mumit Khan]

Greg Miller <gmiller@classic-games.com> writes:
> Mumit Khan wrote:
> > 
> > Greg Miller <gmiller@classic-games.com> writes:
> > > but generates numerous undefined references during linking when compiled
> > > with:
> > >
> > > g++ -mno-cygwin test.c
> 
> Oops.. just noticed an error here... That should have been:
> 
> g++ -mno-cygwin test.c -L //d/cygnus/cygwinb20/mingw-libs
> 
> In any event, is it linking the wrong libstdc++.a despite the "-L"
> switch? or is something else wrong?

I can't tell unless you include some of the undefined symbols. BTW,
I've updated my egcs-1.1.1-mingw-extra package to include both the
required libs and includes (_G_config.h).

The linker has a verbose option that helps. Similarly, the compiler
has a -H option that shows the includes being included.

  
  $ g++ -mno-cygwin -H -c test.c

shows the includes.

  $ g++ -mno-cygwin -Wl,--verbose test.o 

shows the libraries being linked in (prints loads of output!)..

Both of these switches are very useful for debugging a problem like
yours.

Regards,
Mumit


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

Re: linking and iostreams

[Greg Miller]

Mumit Khan wrote:
> > Oops.. just noticed an error here... That should have been:
> >
> > g++ -mno-cygwin test.c -L //d/cygnus/cygwinb20/mingw-libs

Welp, I'm feeling pretty stupid right about now... seeing as how that
should have been //d/cygnus/cygwin-b20/mingw-libs...

> Regards,
> Mumit

Thanks for your time.
-- 
http://www.classic-games.com/
President Clinton was acquitted; then again, so was O. J. Simpson.
*** NEWBIES: Limit signatures to four lines! No HTML mail or posts! ***

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

Re: linking and iostreams

[Greg Miller]

Mumit Khan wrote:
> > Oops.. just noticed an error here... That should have been:
> >
> > g++ -mno-cygwin test.c -L //d/cygnus/cygwinb20/mingw-libs

Welp, I'm feeling pretty stupid right about now... seeing as how that
should have been //d/cygnus/cygwin-b20/mingw-libs...

> Regards,
> Mumit

Thanks for your time.
-- 
http://www.classic-games.com/
President Clinton was acquitted; then again, so was O. J. Simpson.
*** NEWBIES: Limit signatures to four lines! No HTML mail or posts! ***

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

CFORTRAN for cygwin/egcs?

[Richard Stanton]

There's a rather useful package called CFORTRAN, that makes calling FORTRAN
subroutines from C, and vice versa, very simple, on the machines it knows
about.

Has anyone got this working with egcs gcc/g77 under NT? If so, I'd
appreciate any pointers or examples you may have.

Thanks a lot.

Richard Stanton


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

Re: CFORTRAN for cygwin/egcs?

[Mumit Khan]

On Mon, 15 Mar 1999, Richard Stanton wrote:

> There's a rather useful package called CFORTRAN, that makes calling FORTRAN
> subroutines from C, and vice versa, very simple, on the machines it knows
> about.
> 
> Has anyone got this working with egcs gcc/g77 under NT? If so, I'd
> appreciate any pointers or examples you may have.

Hmmm ... it's been years since I've used, but from what I remember, it
should be pretty trivial to use with gcc/g77 on Windows32. I believe the
magic was to define -Df2cFortran (or something like that) and the rest
just worked.

One potential gotcha, and only applicable if you're using gcc/c++ as the
link driver instead of using g77, is that f77 runtime library bundled with 
g77 has been renamed from libf2c.a to libg2c.a, and so you'll need to link
with -lg2c instead of -lf2c. 

  
  $ gcc -Df2cFortran -c cfile.c
  $ g77 -c ffile.f
  $ gcc -o mixedprog ffile.o cfile.o -lg2c

What problems have you had?

Mumit



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

RE: CFORTRAN for cygwin/egcs?

[Richard Stanton]

It IS trivial to use, I've found, as long as you use version 3.5 rather than
2.8. The latter seems to be more easily found. As you say,
using -Df2cFortran, and linking with -lg2c, gets the sample program to
compile without warnings.

Thanks.

Richard Stanton

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> Sent: Monday, March 15, 1999 2:28 PM
> To: Richard Stanton
> Cc: cygwin@sourceware.cygnus.com
> Subject: Re: CFORTRAN for cygwin/egcs?
>
>
> On Mon, 15 Mar 1999, Richard Stanton wrote:
>
> > There's a rather useful package called CFORTRAN, that makes
> calling FORTRAN
> > subroutines from C, and vice versa, very simple, on the
> machines it knows
> > about.
> >
> > Has anyone got this working with egcs gcc/g77 under NT? If so, I'd
> > appreciate any pointers or examples you may have.
>
> Hmmm ... it's been years since I've used, but from what I remember, it
> should be pretty trivial to use with gcc/g77 on Windows32. I believe the
> magic was to define -Df2cFortran (or something like that) and the rest
> just worked.
>
> One potential gotcha, and only applicable if you're using gcc/c++ as the
> link driver instead of using g77, is that f77 runtime library
> bundled with
> g77 has been renamed from libf2c.a to libg2c.a, and so you'll need to link
> with -lg2c instead of -lf2c.
>
>
>   $ gcc -Df2cFortran -c cfile.c
>   $ g77 -c ffile.f
>   $ gcc -o mixedprog ffile.o cfile.o -lg2c
>
> What problems have you had?
>
> Mumit
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
>


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

Re: CFORTRAN for cygwin/egcs?

[Mumit Khan]

"Richard Stanton" <stanton@haas.berkeley.edu> writes:
> It IS trivial to use, I've found, as long as you use version 3.5 rather than
> 2.8. The latter seems to be more easily found. As you say,
> using -Df2cFortran, and linking with -lg2c, gets the sample program to
> compile without warnings.

Thank you. That's very useful information, especially since it goes into
the mailing list archive.

BTW, can I use your Excel DLL as an example (with proper attribution of
course)?  I'd like to create some examples in C, C++ and F77 to create
DLLs for VB/Excel etc like I've done for Java etc.

Regards,
Mumit


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

Re: CFORTRAN for cygwin/egcs?

[Mumit Khan]

"Richard Stanton" <stanton@haas.berkeley.edu> writes:
> It IS trivial to use, I've found, as long as you use version 3.5 rather than
> 2.8. The latter seems to be more easily found. As you say,
> using -Df2cFortran, and linking with -lg2c, gets the sample program to
> compile without warnings.

Thank you. That's very useful information, especially since it goes into
the mailing list archive.

BTW, can I use your Excel DLL as an example (with proper attribution of
course)?  I'd like to create some examples in C, C++ and F77 to create
DLLs for VB/Excel etc like I've done for Java etc.

Regards,
Mumit


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

RE: CFORTRAN for cygwin/egcs?

[Richard Stanton]

It IS trivial to use, I've found, as long as you use version 3.5 rather than
2.8. The latter seems to be more easily found. As you say,
using -Df2cFortran, and linking with -lg2c, gets the sample program to
compile without warnings.

Thanks.

Richard Stanton

> -----Original Message-----
> From: cygwin-owner@sourceware.cygnus.com
> [ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Mumit Khan
> Sent: Monday, March 15, 1999 2:28 PM
> To: Richard Stanton
> Cc: cygwin@sourceware.cygnus.com
> Subject: Re: CFORTRAN for cygwin/egcs?
>
>
> On Mon, 15 Mar 1999, Richard Stanton wrote:
>
> > There's a rather useful package called CFORTRAN, that makes
> calling FORTRAN
> > subroutines from C, and vice versa, very simple, on the
> machines it knows
> > about.
> >
> > Has anyone got this working with egcs gcc/g77 under NT? If so, I'd
> > appreciate any pointers or examples you may have.
>
> Hmmm ... it's been years since I've used, but from what I remember, it
> should be pretty trivial to use with gcc/g77 on Windows32. I believe the
> magic was to define -Df2cFortran (or something like that) and the rest
> just worked.
>
> One potential gotcha, and only applicable if you're using gcc/c++ as the
> link driver instead of using g77, is that f77 runtime library
> bundled with
> g77 has been renamed from libf2c.a to libg2c.a, and so you'll need to link
> with -lg2c instead of -lf2c.
>
>
>   $ gcc -Df2cFortran -c cfile.c
>   $ g77 -c ffile.f
>   $ gcc -o mixedprog ffile.o cfile.o -lg2c
>
> What problems have you had?
>
> Mumit
>
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
>


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

Re: CFORTRAN for cygwin/egcs?

[Mumit Khan]

On Mon, 15 Mar 1999, Richard Stanton wrote:

> There's a rather useful package called CFORTRAN, that makes calling FORTRAN
> subroutines from C, and vice versa, very simple, on the machines it knows
> about.
> 
> Has anyone got this working with egcs gcc/g77 under NT? If so, I'd
> appreciate any pointers or examples you may have.

Hmmm ... it's been years since I've used, but from what I remember, it
should be pretty trivial to use with gcc/g77 on Windows32. I believe the
magic was to define -Df2cFortran (or something like that) and the rest
just worked.

One potential gotcha, and only applicable if you're using gcc/c++ as the
link driver instead of using g77, is that f77 runtime library bundled with 
g77 has been renamed from libf2c.a to libg2c.a, and so you'll need to link
with -lg2c instead of -lf2c. 

  
  $ gcc -Df2cFortran -c cfile.c
  $ g77 -c ffile.f
  $ gcc -o mixedprog ffile.o cfile.o -lg2c

What problems have you had?

Mumit



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

CFORTRAN for cygwin/egcs?

[Richard Stanton]

There's a rather useful package called CFORTRAN, that makes calling FORTRAN
subroutines from C, and vice versa, very simple, on the machines it knows
about.

Has anyone got this working with egcs gcc/g77 under NT? If so, I'd
appreciate any pointers or examples you may have.

Thanks a lot.

Richard Stanton


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

Re: linking and iostreams

[Mumit Khan]

Greg Miller <gmiller@classic-games.com> writes:
> Mumit Khan wrote:
> > 
> > Greg Miller <gmiller@classic-games.com> writes:
> > > but generates numerous undefined references during linking when compiled
> > > with:
> > >
> > > g++ -mno-cygwin test.c
> 
> Oops.. just noticed an error here... That should have been:
> 
> g++ -mno-cygwin test.c -L //d/cygnus/cygwinb20/mingw-libs
> 
> In any event, is it linking the wrong libstdc++.a despite the "-L"
> switch? or is something else wrong?

I can't tell unless you include some of the undefined symbols. BTW,
I've updated my egcs-1.1.1-mingw-extra package to include both the
required libs and includes (_G_config.h).

The linker has a verbose option that helps. Similarly, the compiler
has a -H option that shows the includes being included.

  
  $ g++ -mno-cygwin -H -c test.c

shows the includes.

  $ g++ -mno-cygwin -Wl,--verbose test.o 

shows the libraries being linked in (prints loads of output!)..

Both of these switches are very useful for debugging a problem like
yours.

Regards,
Mumit


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

Re: linking and iostreams

[Greg Miller]

Mumit Khan wrote:
> 
> Greg Miller <gmiller@classic-games.com> writes:
> > but generates numerous undefined references during linking when compiled
> > with:
> >
> > g++ -mno-cygwin test.c

Oops.. just noticed an error here... That should have been:

g++ -mno-cygwin test.c -L //d/cygnus/cygwinb20/mingw-libs

In any event, is it linking the wrong libstdc++.a despite the "-L"
switch? or is something else wrong?
-- 
http://www.classic-games.com/
President Clinton was acquitted; then again, so was O. J. Simpson.
*** NEWBIES: Limit signatures to four lines! No HTML mail or posts! ***

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

Re: linking and iostreams

[Mumit Khan]

Greg Miller <gmiller@classic-games.com> writes:
> 
> This program:
> 
> #include <iostream>
> 
> int main() {
>   cout << "test" << endl;
> 
>   return 0;
> }
> 
> compiles, links, and does what I expect when compiled with B20.1 and
> egcs-1.1.1 using this command:
> 
> g++ test.c
> 
> but generates numerous undefined references during linking when compiled
> with:
> 
> g++ -mno-cygwin test.c

Please see my howto[1] on -mno-cygwin option. This issue has been discussed
in detail in this group, so the search engine is also a good option.

[1] http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
    http://www.delorie.com/howto/

Regards,
Mumit


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

linking and iostreams

[Greg Miller]

This program:

#include <iostream>

int main() {
  cout << "test" << endl;

  return 0;
}

compiles, links, and does what I expect when compiled with B20.1 and
egcs-1.1.1 using this command:

g++ test.c

but generates numerous undefined references during linking when compiled
with:

g++ -mno-cygwin test.c

Notably, it generates a number of references to "__errno" from
libstdc++.a, which, AFAIK, should not include ANY references to
"__errno" in the mingw-libs version.

So what am I doing wrong?
-- 
http://www.classic-games.com/
President Clinton was acquitted; then again, so was O. J. Simpson.
*** NEWBIES: Limit signatures to four lines! No HTML mail or posts! ***

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