Re: RFD: cygwin + *native* MinGW compiler

At: http://www.cygwin.com/ml/cygwin/2009-01/msg00848.html Charles Wilson said: Greg said >> >>I use '--build=i686-pc-mingw32 --host=i686-pc-mingw32'. Here: >> http://lists.gnu.org/archive/html/libtool-patches/2009-01/msg00193.html >>you say that's lying to 'configure', but you also observe that >

RE: Cygwin - linker errors - __assert, __itob and __ftol

Dave Korn wrote (archived at http://www.cygwin.com/ml/cygwin/2008-05/msg00643.html) >Tim Prince wrote on 30 May 2008 23:48: >> C S wrote: >>> gcj -D__int64="long long" -shared -I C:\Apps\Java\jdk1.6.0_05\include > >>> the error i get is: gcj: cannot specify -D without --main > >> might be handle

RE: [ mingw-Patches-1789093 ] Modernize mingw10.dll build procedure

> From: Charles Wilson > Sent: Saturday, 26 April 2008 2:05 p.m. > > SourceForge.net wrote: > > Patches item #1789093, was opened at 2007-09-06 14:33 > > > > Comment By: Danny Smith (dannysmith) > > Date: 2008-04-25 17:42 > > > > Ping! > &

Re: About linker otions an rebasing

quoting Brian Dessent in message archived at http://www.cygwin.com/ml/cygwin/2008-01/msg00571.html > auto-import has nothing to do with rebasing and is the default anyway. > The only thing that specifying --enable-auto-import does is disable some > informational messages that are printed during l

Re: cygwin, g++ and boost? Do I need dll.a?

At http://www.cygwin.com/ml/cygwin/2008-01/msg00158.html Charles Wilson said: > With -static, -lxxx only looks for: > > libxxx.a > xxx > > > Note that, oddly, in -static mode a MS-style library name "xxx.lib" > will be ignored, while in (normal) mode it will be used if found (and

RE: gcc-dw2? or fast sjlj-exceptions EH

At http://www.cygwin.com/ml/cygwin/2007-09/msg00194.html Tatsuro Matsuoka wrote: > The best solution, I think, the speed of sjlj-exceptions EH on the > cygwin is as fast as that of other platforms. > In the case of octave, I believe that the main cause of slowdown is the sjlj EH code generated

RE: Decimal float and the Cygwin build of GFortran.

Angelo Graziosi Wednesday, 4 July 2007 7:19 p.m. > > > > I have build GFortran under Cygwin configuring with: > > ./configure --prefix=${prefix_dir} \ > --enable-languages=c,fortran \ >--enable-bootstrap \ >-

dllimport and __asm__("_alias" )

Hello, I would appreciate help with While working on some dllimport problems with aliased symbols, I ran across this inconsistency with gcc (all versions) The use of a literal asmspec to rename a static lib symbol (say "bar"), extern void foo (void) __asm__("_bar"); void call_bar(void) { fo

RE: Eliminating -mno-cygwin from gcc?

cgf wrote > > How about if we eliminate -mno-cygwin from future releases and either > provide our own mingw cross-tools or wrap the offerings from > mingw.org? I would miss -mno-cygwin. Gcc -mno-cygwin suppports symlinks, mingw doesn't. --host=i686-pc-cygwin --target=i686-pc-cygwin would be

RE: cygwin -mno-cygwin AC_CHECK_SIZEOF

> > Or have autoconf use some other tool that does not do binary > processing > (e.g., awk or tr) instead of cat, which would enable the text mount > solution. > Igor Or make cygwin-pc-i686-gcc -mno-cygwin foo.c mean something subtly but significantly different from mingw32-pc-i686-gcc f

[OT] RE: mno-cygwin dll woes

> > Looking at the specs file, -mno-cygwin always links with > -lmsvcrt, so > short of editting the specs file, how is it possible to link > only with > msvcr80? > If you had posted this to the mingw list someone might have suggested: cp -f /lib/mingw/libmsvcr80.a /tmp/libmsvcrt.a gcc -mno

RE: Problems with GCC-3.4.4-2 (exp) ? (Gold S.)

>> D. Korn wrote: >> >> Can I have an experimental gold star for having uploaded an experimental >> version of gcc and get it upgraded to a real gold star when I upload the >> new Curr: version? > > >I think he should have a Gold Star in any case! > Sheesh. I'm in the wrong project. I've been [

RE: GMP-4.2, MPFR-2.2, was Re: Problems with GMP in latest Cygwin

> > Angelo Graziosi wrote: > > Thanks for the links. Unfortunately, the package files that David > Billinghurst references therein seem to have disappeared; does anyone > know where they can currently be found? > ftp://ftp.gnu.org/gnu/gmp/gmp-4.2.1.tar.bz2 http://www.mpfr.org/mpfr-current/mp

Re: Behavior of ifstream::read() in g++

Alex Vinokur Sunday, 15 October 2006 5:10 p.m. > This program has different behavior in > * g++ 3.4.4 (Cygwin) > * gpp 4.0.1 *Djgpp) > * Microsoft C++ 13.00.9466 > > --- foo.cpp -- > #include > #include > #include > using namespace std; > > #define BUFFER_SIZE 1500 > #define INPUT_FI

RE: -fno-inline -O1 breaks ntohs()

> > > >! #if defined __OPTIMIZE__ && !defined __NO_NOINLINE__ #if defined __OPTIMIZE__ && !defined __NO_INLINE__ Rule No 1: The obvious is not always not what it appears to be. Danny -- Unsubscribe info: http://cygwin.co

RE: -fno-inline -O1 breaks ntohs()

> Testcase: > -- > #include > > int main() > { > volatile short s = 33, t; > > t = ntohs(s); > return 0; > } > -- > > > i686-pc-cygwin-gcc -fno-inline -o test test.c > i686-pc-cygwin-gcc -O1 > > -fno-inline -o test test.c > /tm

RE: no message or dialog when a DLL is missing

Dave Korn > > On 30 August 2006 16:19, Pierre Baillargeon wrote: > > > I've identified the reason why DLL don't show up: in the > startup code > > (winsup/cygwin/dcrt0.cc), in dll_crt0_0(), Win32's > SetErrorMode() is > > called to suppress all OS error dialogs. It's there since 1998 > > ac

Re:Can't link TclMagick anymore

Sorry about breaking thread. I suppose I should give in and re-subscribe here. Dave Bodenstab wrote at http://cygwin.com/ml/cygwin/2006-08/msg00264.html > Warning: .drectve `-defaultlib:MSVCRT ' unrecognized > Warning: .drectve `-defaultlib:OLDNAMES ' unrecognized These are harmless > Cannot e

Re:Can't link TclMagick anymore

Dave Bodenstab wrote: > Warning: .drectve `-defaultlib:MSVCRT ' unrecognized > Warning: .drectve `-defaultlib:OLDNAMES ' unrecognized > Cannot export [EMAIL PROTECTED]@Tcl?$AA@: symbol not found > Cannot export [EMAIL PROTECTED]@[EMAIL PROTECTED]@: > symbol not found > Cannot export ^?CORE_RL_ma

Change to Dwarf-2 debug info.

Hello I thought it was about time to change the default debug info for cygwin and mingw from stabs to dwarf2. Currently the default of stabs can be overriden by '-ggdb' (==use the best format for gdb) Apple has done just such a change in gcc 4.2. GCC 4.3 stage 1 seems like a good time to change

[OT] RE: g++ 3.4.4, mingw32, exceptions and threads

Karl wrote: > I am having problems getting exceptions to work properly in > the latest release of g++ distributed from cygwin. I have a multithreaded > code which is built using the no-cygwin option. The code uses > exceptions in a few places. Oddly the code is either crashing out right, > o

RE: Increasing Available Memory for Cygwin Run Programs in XP

> I am trying to run a numerical simulation that requires a large amount > of RAM in the cygwin environment running on a Pentium 4 with Windows > XP and 3GB RAM. I have so far learned that Windows XP (and other > Windows versions) allot only 2GB RAM for user program space. I have > verified this wi

Re: fstream and sstream error with gcc 3.4.4

> After upgrading from gcc 3.3.3 to gcc 3.4.4, I now get the following errors when I compile some code: When using GCC's libstdc++ -DNOMINMAX or #define NOMINMAX before including Danny -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygw

Re: Building libstdc++.dll the easy way

- Original Message - From: "John W. Eaton" Sent: Thursday, 6 October 2005 09:13 > On 6-Oct-2005, Danny Smith wrote: > > | Building libstdc++.dll may be a "hard problem" for a mathematician or > | for libtool, but this is how an ordinary person coud

Building libstdc++.dll the easy way

Building libstdc++.dll may be a "hard problem" for a mathematician or for libtool, but this is how an ordinary person coud do it. dlltool --output-def libstdc++.def --export-all libstdc++.a gcc -shared -olibstdc++.dll -Wl,--out-implib,libstdc++.dll.a \ libstdc++.def libstdc++.a The main

Re; Visibility of compiler symbols between executables and DLLs

Nick Glencross wrote: > On many platforms compilation symbols in an executable are not made > visible to its Shared Library/DLLs by default, but this can often be > overridden with a compiler flag to change the policy. My question in a > nutshell then is whether cygwin has the ability to have a DL

Re: Bug in gcc and/or binutils?

References: Charles Wilson wrote: > > Using .def files turns off the auto-EXport logic (which it should, > because if you specify a specific set of exports you don't want bin

Re: g++ defines for win32

On Sun, 14 Aug 2005, Angel Tsankov wrote: > It seems I've come upon an interesting issue, probably a bug. Here it > is: > I have a header file that defines __stdcall, __fastdecl and __cdecl. > If the preprocessor uses the CPLUS_INCLUDE_PATH to find that header > file, then it does not issue a warn

Re: Serious performance problems (Gerrit/Danny please comment)

Re: Serious performance problems (Gerrit/Danny please comment) From: Christopher Faylor To: cygwin at cygwin dot com Date: Sat, 28 May 2005 14:57:20 -0400 Subject: Re: Serious performance problems (Gerrit/Danny please comment) References:

Re: Problem including float.h with gcc -mno-cygwin (Danny can you comment?)

cgf wrote: >On Sun, Mar 20, 2005 at 09:21:42AM +1200, Danny Smith wrote: >>On native mingw build I get this: >> >>#include "..." search starts here: >>#include <...> search starts here: >> D:/MINGW/BIN/../lib/gcc/mingw32/3.4.3/../../../../include

Re: Problem including float.h with gcc -mno-cygwin (Danny can you comment?)

cgf wrote: >On Sat, Mar 19, 2005 at 11:14:04AM -0500, Paul Stodghill wrote: >> >>[The fact that the cygwin compiler path appears on the search path] is a >>different and unrelated problem, I think. >> >>barney-xp$ md5sum /usr/lib/gcc-lib/*/3.3.3/include/float.h >>248cb979b88c788e88100b913eea6ce9 >>

Re: Possible bug in gas/ld when using .linkonce

Pavel Tsekov wrote: > Hello, > > I found this one while playing with Cygwin's code which takes care of > seamless loading of dll functions (autoload.cc). It seems that when a > symbol in a section marked .linkonce is referenced, wrong relocation info > is generated for that symbol. > > For example

Re: loading of wsock32 disturbs FPU

cgf wrote: >On Wed, Mar 02, 2005 at 03:37:42PM +0100, Corinna Vinschen wrote: >>On Mar 2 15:31, Corinna Vinschen wrote: >>>On Mar 2 13:33, Dave Korn wrote: Hm. We probably need to put a finit instruction into the autoload code somewhere. wsock_init () looks like just the place.. now

Re; Problem running xgettext after compiling gettext 0.14.1 with gcc 3.3.3

From: Peter Rehley > Hi, > > I am working on a project where I had to recompile gettext using gcc > 3.3.3. I'm using cygwin 1.5.12. It compiled without issues but when I > went to run some of the programs, a windows dialog box pops up showing > the following message: > > "The application failed

RE: c++ exceptions in shared library results in crash

From: "Rainer Hochreiter" > throwing an exception in the shared library results in a core dump of the > binary executable - but only for the cross-compiled version! cygwin and mingw gcc sources contain a local patch

Re: c++ code executes very slowly - sjlj EH to blame?

e abort() EH, >>which is equivalent to having _no_ EH in practical >>terms. >> >>Maybe Danny Smith has some thoughts about this, since >>he has apparently been at least partially successful >>in getting DWARF2 EH to work on cygwin. > > >Yes, I expect

Re: Segmentation faults with g++ 4.0

James W. McKelvey wrote: > I installed CYGWIN_NT-5.1 a few days ago and then built g++ from the latest > CVS. Simple programs like the one below will compile and link, but then get > segmentation faults in pthread_specific on execution: > > #include > #include > > static const std::locale l; > /

Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH

Richard Henderson wrote: > On Wed, Nov 24, 2004 at 11:27:11AM +1300, Danny Smith wrote: >> Before I pull any more hair out trying, does any one have any hints >> on how to use an MD_FALLBACK_FRAME_STATE_FOR to workaround ... > > That would be wrong. > > I think the most

Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH

Richard Henderson wrote: > On Wed, Nov 24, 2004 at 11:27:11AM +1300, Danny Smith wrote: >> Before I pull any more hair out trying, does any one have any hints >> on how to use an MD_FALLBACK_FRAME_STATE_FOR to workaround ... > > That would be wrong. > > I think the most

stdcall lib functions with exception throwing callbacks vs Dwarf2 EH

Hi, I've been trying to get DW2 EH exception handling working on windows targets with general success, but have hit a snag. If a C library function that takes a callback arg is compiled using stdcall convention, C++ exception thrown by the callback result in abort. If the C libarary function use

Re: Need an older gcc version on my cygwin due to poor performance on gcc-3.x series.

Gerrit P. Haase wrote: > Danny Smith wrote: > >> Gerrit wrote: >> >> >>> Ole Jacob Hagen wrote: >> >> >>>> Hi, >>>> >>>> I've compiled Octave-2.1.60 with gcc-3.3.3 successfully, but the >>>> pe

: Re: Need an older gcc version on my cygwin due to poor performance on gcc-3.x series.

Gerrit wrote: > Ole Jacob Hagen wrote: >> Hi, >> >> I've compiled Octave-2.1.60 with gcc-3.3.3 successfully, but the >> performance is pretty bad with gcc-3.3.3. >> The performance should of Octave is much better, when compiling it >> with gcc-3.2.x instead. > It would make more sense to ident

Re: [gcc-3.4.1 / binutils] where are my symbols?

Gerrit wrote: > Hello, > > I see the following: > > I link four objects togehter in a DLL: > gcc -shared -o .libs/cyggconfbackend-oldxml.dll \ > -Wl,--out-implib,.libs/libgconfbackend-oldxml.dll.a \ > .libs/xml-cache.o .libs/xml-dir.o .libs/xml-entry.o \ > .libs/xml-backend.o ${LIBS} > >

Re: Building DLL

Maarten wrote > Sorry, searched for that, but couldn't come up with any references of > using dlltool in combination with an executable. Try this: == /* dll.c */ #include extern __attribute__ ((__dllimport__)) void exe_hello(void); vo

profiling vs mingw package [Was: G++ for CygWin]

Tim Prince wrote: < snip> > I go through the list and > turn off mingw every time, because it breaks profiling, so there's > another optional package which I'm happy to avoid. > Tim, are you referring to this profiling bug? http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7940 [3.3 regression] [Cyg

Re: DLL and external symbols

From: Jani Tiainen > > > Hi, > > I'm sure that this has been answered several times, but I'll ask again because couldn't find any solution by myself. > > I would like to build DLL (or any other sort of library) th

#pragma interface [Was: cygwin mysql 4.0.16 compilation]

Gerrit P. Haase wrote: > In short, it seems that > #pragma interface > doesn't work and commenting it let you compile the code. I always > comment also > #pragma implementation > but it seems the it is enough to comment out #pragma interface. > > Though, I'm seeking for someone to shed light on

RE: Possible bug with __attribute__((alias)) in gcc-3.3

Nicholas wrote: > Hi All, > > Gerrit and I were discussing this off-list, but I thought it appropriate > that I move it to the main list since he has confirmed the problem. > > Here's the problem, programs are segfaulting when the are linked to a > symbol which was aliased using __attribute__((a

RE[2]: Exporting const variables from DLLs (GCC bug?)

--- Danny Smith <[EMAIL PROTECTED]> wrote: > Jon Foster wrote: > > > Given this source code: > > extern const int meaning_of_life __declspec(dllexport); > > const int meaning_of_life __declspec(dllexport) = 42; > > > > > > GCC complains: >

RE: Exporting const variables from DLLs (GCC bug?)

Jon Foster wrote: > Given this source code: > extern const int meaning_of_life __declspec(dllexport); > const int meaning_of_life __declspec(dllexport) = 42; > > > GCC complains: > $ c++ -g -O2 -c test.cxx -o test.o > test.cxx:2: error: external linkage required for symbol 'const int >mean

Re: merging mingw and cygwin

Ed said: > Like I said, try: > > mingw > gcc -dM -e -xc /dev/null > cygwin > gcc -mno-cygwin -dM -E -xc /dev/null > > cygwin makes 73 defines, mingw makes 38. If a large project uses any of the > cygwin defines, it will behave differently than if compiled with native mingw. > That's because yo

Anon structs in gcc-3.3.1 [Was: Re: Available for testing: gcc-3.3.1-1 ...]

Serge wrote > Hallo Christopher, > >The support for unnamed structure/union is brocken! > >The warning only (-Wall) is generated and corresponding field is ignored! > >The old GCC compiler (before 2.95.3 if I not mistake) reports the error. > >In the previous 2.95.3 .. 3.2 and in the current GCC s

Re: getopt: ugly linker messages

Re: getopt: ugly linker messages From: Corinna Vinschen To: cygwin at cygwin dot com Date: Fri, 19 Sep 2003 17:34:09 +0200 Subject: Re: getopt: ugly linker messages References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED

Re: (link to) gcc-testsuite results for cygming-special 3.3.1

> From: Christopher Faylor > To: cygwin at cygwin dot com > Date: Sun, 14 Sep 2003 11:33:47 -0400 > On Sun, Sep 14, 2003 at 01:09:08AM -0400, Charles Wilson wrote: > >Christopher Faylor wrote: > > > >>On Sat, Sep 13, 2003 at 05:48:11PM -0700, Tim Prince wrote: > >> > >>>http://gcc.gnu.org/ml/gc

Re: Available for testing: gcc-3.3.1-1 and gcc-mingw-20030911-1

--- Charles Wilson <[EMAIL PROTECTED]> wrote: > Danny Smith wrote: > > > gcc 3.2-3 used Dwarf2 exceptions, which worked most of the time. (In fact, > > I don't recall any bug reports at all on cygwin list). But it didn't work > > with w32api callbacks

Re: Available for testing: gcc-3.3.1-1 and gcc-mingw-20030911-1

On Sat, Sep 13, 2003 at 12:43:38PM -0400, Rolf Campbell wrote: >Christopher Faylor wrote: > >>On Sat, Sep 13, 2003 at 12:20:39PM -0400, Rolf Campbell wrote: >> >>>Is this new gcc supposed to be ABI compatible with 3.2.x? Because I >>>can't link in libraries compiled with an older version of cygwi

Re: ld -r errors with C++ objects

From: "Brian R. Gaeke" > > > > When I link two particular .o files together into a new relocatable > > > (using ld -r) I get errors from ld, instead of a new .o file. This > > > happens in many of our C++ projects

Re: Calling gcc built DLL from .NET (Visual Basic)

From: "Thomas X. Hoban" > Does anyone have a good example that shows how to create a DLL using > cygwin/gcc and call it using VB .NET? I am specifically interested in an > example that shows how to pass a String v

RE: gcc -mno-cygwin preprocessing: cygwin headers included.

From: Teun Burgers --- > > consider a file hello.c with the following two lines: > > #include > #include > > The attached cygwin.txt is the output of gcc -E hello.c > The attached no-cygwin.txt is the output of gcc -mno-cygwin -E hello.c > > The cygwin one includes /usr/include/st

Re: Can open() from console app, not from dll

--- Massimiliano Mirra <[EMAIL PROTECTED]> wrote: > Danny Smith <[EMAIL PROTECTED]> writes: > > >> I am able to open a file and write into it from a console application, > >> but the same fails when done from within a function that is stored in >

RE: Can open() from console app, not from dll

From: Massimiliano Mirra > I am able to open a file and write into it from a console application, > but the same fails when done from within a function that is stored in > a DLL and called from a Visual Basic application. VB expects stdcall convention. Try adding WINAPI to OpenSomething You wil

Re: cygwin gcc 3.4 and cygwin

--- Danny Smith <[EMAIL PROTECTED]> wrote: > Brian Ford wrote: > > > Vanilla gcc 3.2.x is NOT ABI compatible with Cygwin's pre 3.2 gcc, fact. > > I wanted to know why this was allowed to persist given the simple patch > > required to fix it, question. I

Re: cygwin gcc 3.4 and cygwin

Brian Ford wrote: > Vanilla gcc 3.2.x is NOT ABI compatible with Cygwin's pre 3.2 gcc, fact. > I wanted to know why this was allowed to persist given the simple patch > required to fix it, question. I had seen Mr. Faylor make statements > before to the effect of: doubles in structures are not tha

Re: cygwin gcc 3.4 and cygwin

lla gcc are ABI incompatible. > > Doesn't this seem bad? If you want pickled eggs with your free beer, you may have to wait. Myself, I can't understand why the barman can't put the foam on the bottom 2003-02-16 Danny Smith <[EMAIL PROTECTED]> * config/i38

Re: [avail for test] libtool-devel-20030216-1

Christopher Faylor wrote: > However, it could easily be standard. I could include a i686-pc-mingw32-gcc > and a i686-pc-mingw-ld in the gcc distribution. And, I could also alias > all of the i686-pc-cygwin-* tools to i686-pc-mingw32-*. That would provide > the equivalent of a cross compilation

RE:size limit for static arrays in cygwin/gcc

Randall R Schulz wrote: > A couple of months ago, someone reported on how local (stack) > allocations larger than a certain threshold were allocated on the heap. > In fact, you, Danny, contributed materially to that thread: Subject > "Strange behaviour of gcc" starting with a posting by > [EMAIL

RE:size limit for static arrays in cygwin/gcc

"Charles D. Russell" wrote: >Meanwhile, I am trying to find an equivalent problem in C so that it will > get more attention. Unfortunately, I don't know much C. The subsequent > program fails with a segmentation violation if one tries to allocate more > than a few Mb of memory on either my

Re: progress on libstdc++.dll

Paul Kienzle wrote > I have been advised from a couple of sources that the dlltool approach to > building libstdc++.dll will not work. So I then tried the following: > > gcc -shared -Wl,-whole-archive,--export-all-symbols,--enable-auto-image- base \ > /usr/lib/libstdc++.a -Wl,-no-whole-archive

Re:anyone have implicit linkage of gcc DLLs working in Visual C?

- Todd West wrote I'm experimenting with using Cygwin and gcc -shared to build Windows DLLs which are called by code compiled by VC6.0 SP5 or the Intel C 7.0 plug-in for VC. I've using some very small stubs of test code and DLLs extracted from Atlas 3.4.1. Implicitly linked calls

Re:Strange behaviour of gcc

Hello Randall Yeah, no documentation to speak of. The only reason I know about it because I've been chasing the _alloca bug that Fish reported. It is still present in GCC trunk (3.4). I have submitted a simple patch that fixes, but ... time for a ping in the New Year. Danny, rrschulz wrote:

Re:Strange behaviour of gcc

> > GCC's __builtin_alloca uses a helper function called _alloca to check the > stack > whenever allocating more that 4000 bytes in one go. > > Danny To disable stack probing, add this switch -mno-stack-arg-probe. Danny http://movies.yahoo.com.au - Yahoo! Movies - What's on at your local ci

Re:Strange behaviour of gcc

[EMAIL PROTECTED] wrote: > Can somebody explain why gcc (version 3.2 20020927) on Cygwin does > this? Type this simple C program > > void func(void){ > struct {unsigned char data[3985];}var; > } > > and compile with > > gcc -c filename.c > > Then type > > nm filename.o > > The output is > > 0

Re: Error: symbol `_D' is already defined

From: "Tim Beuman" To: "Cygwin at Cygwin dot Com" Date: Thu, 5 Dec 2002 15:39:30 -0800 Subject: Error: symbol `_D' is already defined Hi, I am getting the following error when compiling a c++ source: /d/Temp/

Re: gcc 3.2 string link problem

gcc 3.2 string link problem From: Nigel Stewart & Fiona Smith To: cygwin at cygwin dot com Date: Mon, 18 Nov 2002 10:42:45 +1100 Subject: gcc 3.2 string link problem ===snip=== > $ g++ test.cpp > /cygdrive/c/DOCUME~1/nigels/LOCALS~1/Temp/ccHP4AMl.o(.text+0x25):test.cpp: > > undefined referenc

Re:1.3.15-1: small bug in win32/mmsystem.h waveOutOpen prototype

heiko wrote: > It should be > MMRESULT WINAPI waveOutOpen > (LPHWAVEOUT,UINT,LPCWAVEFORMATEX,PDWORD,PDWORD,DWORD); No it shouldn't. DWORD_PTR != PDWORD. This is what I see in documentation: MMRESULT WINAPI waveOutOpen(LPHWAVEOUT,UINT_PTR,LPWAVEFORMATEX,DWORD_PTR,DWORD_PTR,DWORD); the DWORD_PTR

re: binutils 20021107-2

Hello Robert By default symbols in libstdc++.a are excluded when doing --export-all, to protect against this type of error. However, ld/pe-dll.c knows nothing about libstdc++-2.a. So those symbols do get exported ... and cause the usual problems with multiple definitions. Quick solution: Try --

Re: Problem compiling cpp programs with gcc-3.2-1

From: Mark Schoenberg To: cygwin at cygwin dot com Date: Mon, 28 Oct 2002 20:51:59 +1900 > The problems described below appeared after I upgraded to the latest > versions of the cygwin release. It disappeared w

RE: The -a options no longer accessible in gcc 3.2?

>I tried out the new gcc 3.2 from cygwin's website. But when I tried to > generate the basic block information (-a options), cc1plus screams: > unrecognized option `-a'. Why is this? Is it because this profiling is > turned off, somehow? Enable basic program profiling code with: -fprofile Da

RE: [MinGW-dvlpr] Re: gcc 3.1 [-mno-cygwin and __main ]

--- "Billinghurst, David (CRTS)" <[EMAIL PROTECTED]> wrote: > Danny, > > Can you elaborate on this. Now would be a good time to get > dwarf2 EH working on cygwin. It would be painful to release > a cygwin gcc-3.1 with sjlj exceptions, then switch. > My feelings exactly. Give me 12-18 hours

Re: [MinGW-dvlpr] Re: gcc 3.1 [-mno-cygwin and __main ]

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Wed, May 15, 2002 at 11:15:48AM +1000, Danny Smith wrote: > >>Perhaps it's time to drop the -mno-cygwin support and just supply a > >>cygwin hosted mingw32 targeted cross compiler? > > > >That

Re: [MinGW-dvlpr] Re: gcc 3.1 [-mno-cygwin and __main ]

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Wed, May 15, 2002 at 11:15:48AM +1000, Danny Smith wrote: > >>Perhaps it's time to drop the -mno-cygwin support and just supply a > >>cygwin hosted mingw32 targeted cross compiler? > > > >That

RE: c++ char exceptions

Robert wrote: > > I don't know if this is a cygwin issue or if I am doing something > fundamentally wrong... > You threw const char* int main (int argc, char **argv) { try { throw "catch this"; } catch (const char *message) // ^ { return 1; } return

REt: Creating DLLs using c++/g++

> From: Suhanthan Vanniyasingam > I have created DLLs by using the following command > "gcc -Wl,--out-implib,libmydll.import.a -shared -o mydll.dll > mydll.o" > and used with a VC++ application. > But I have tried the same command with c++ and g++. It's creating the DLL. > But the functio

RE: input stream crash with gcc 3.1

> I have recently compiled the latest 3.1 branch (grabbed directly via cvs) > for cygwin (1.3.9) and am having problems when using anything related at > all > to input streams. See this: http://gcc.gnu.org/ml/gcc-patches/2001-06/msg00841.html then try rebuilding libstdc++ with #define _GLIBCPP_A

RE: undefined reference to `__gxx_personality_sj0'

> From: "Dan Kyhl" > To: cygwin at cygwin dot com > Date: Wed, 20 Feb 2002 11:13:47 +0100 > Hi, > I get a lot of these (and some others) and suppose that I'm missing a library. > I'm already using -lc -lstdc++ as is used in Linux. > So what am I missing here? GCC 3.x. It sounds like you

Re: Possible bug in handling of BSS sections?

--- Julian Hall <[EMAIL PROTECTED]> wrote: > > Hi; I don't know whether this has been mentioned before, but I just had > a bug report for NASM, which I am one of the maintainers of, relating to > linking code assembled by NASM with the cygwin or mingw linkers. > > I've done a little investigati

Re: linking C++ code against library from fortran sources

--- Hans Horn <[EMAIL PROTECTED]> wrote: > Hi everybody, > > I have a bunch of old numerical fortran77 sources, which I compiled with > g77 > and archived into, say libMyF77.a. > > I want those f77 functions to be called from w/i a c++ program. > > Here are my two questions: > > 1. to satisfy

Re: -mno-cygwin with newer GCC?

--- David Abrahams <[EMAIL PROTECTED]> wrote: > -- > Request: If you can remember to, please reply to me personally in > addition > to sending your reply to the cygwin list. Thanks! > -- > > Hi, > > I'm trying to use -mno-cygwin with a Cygwin GCC-3.0.2 that I built from > sources. It se

Re: Run time linking a .dll into a .exe

--- Glen Ozymok <[EMAIL PROTECTED]> wrote: > I want to create some plugins for an executable. > The problem is that when I create a plugin > (.dll, shared object, or whatever you want to call it), > it sucks in code that is already in the executable. > In other words, I link the executable with s