incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Zhong" <sco...@roguewave.com>
Subject RE: Cygwin 12d build issues
Date Sun, 11 Mar 2007 02:01:37 GMT
I'm getting a different error than you Mark,
 
$ gcc -D_RWSTD_USE_CONFIG -I. -v -pedantic -nostdinc++  -W -Wall -Wcast-qual -Winline -Wshadow
-Wwrite-strings -Wno-long-long -Wcast-align  -c /build/stdcxx/etc/config/src/BAD_ALLOC_ASSIGNMENT.cpp
-o BAD_ALLOC_ASSIGNMENT.o
$ gcc BAD_ALLOC_ASSIGNMENT.o   -lm -lsupc++ -lcatgets -liconv  -o BAD_ALLOC_ASSIGNMENT
BAD_ALLOC_ASSIGNMENT.o:BAD_ALLOC_ASSIGNMENT.cpp:(.text+0x776): undefined reference to `std::bad_alloc::operator=(std::bad_alloc
const&)'
BAD_ALLOC_ASSIGNMENT.o:BAD_ALLOC_ASSIGNMENT.cpp:(.text+0x7c4): undefined reference to `std::bad_alloc::operator=(std::bad_alloc
const&)'
BAD_ALLOC_ASSIGNMENT.o:BAD_ALLOC_ASSIGNMENT.cpp:(.text+0x845): undefined reference to `std::bad_alloc::operator=(std::bad_alloc
const&)'
BAD_ALLOC_ASSIGNMENT.o:BAD_ALLOC_ASSIGNMENT.cpp:(.text+0x89d): undefined reference to `std::bad_alloc::operator=(std::bad_alloc
const&)'
BAD_ALLOC_ASSIGNMENT.o:BAD_ALLOC_ASSIGNMENT.cpp:(.text$_ZNSt9bad_allocassignERK
S_[std::bad_alloc::assign(std::bad_alloc const&)]+0x1f): undefined reference to `std::bad_alloc::operator=(std::bad_alloc
const&)'
collect2: ld returned 1 exit status
 
Yu (Scott) Zhong

________________________________

From: Scott Zhong [mailto:scottz@roguewave.com]
Sent: Sat 3/10/2007 6:52 PM
To: stdcxx-dev@incubator.apache.org
Subject: RE: Cygwin 12d build issues



some verbose output:

gcc -D_RWSTD_USE_CONFIG -I. -pedantic -nostdinc++  -W -Wall -Wcast-qual -Winline -Wshadow
-Wwrite-strings -Wno-long-long -Wcast-align -v -c /build/stdcxx/etc/config/src/BAD_ALLOC_WHAT.cpp
-o BAD_ALLOC_WHAT.o

Using built-in specs.
Target: i686-pc-cygwin
Configured with: ./configure --prefix=/usr/local/gcc411
Thread model: single
gcc version 4.1.1
 /usr/local/gcc411/libexec/gcc/i686-pc-cygwin/4.1.1/cc1plus.exe -quiet -nostdinc++ -v -I.
-D__CYGWIN32__ -D__CYGWIN__ -Dunix -D__unix__ -D__unix -idirafter /usr/lib/../include/w32api
-idirafter ../../include/w32api -D_RWSTD_USE_CONFIG /build/stdcxx/etc/config/src/BAD_ALLOC_WHAT.cpp
-quiet -dumpbase BAD_ALLOC_WHAT.cpp -mtune=pentiumpro -auxbase-strip BAD_ALLOC_WHAT.o -pedantic
-W -Wall -Wcast-qual -Winline -Wshadow -Wwrite-strings -Wno-long-long -Wcast-align -version
-o /cygdrive/c/DOCUME~1/SCOTTZ~1.QUO/LOCALS~1/Temp/cckhl51h.s
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/usr/local/gcc411/lib/gcc/i686-pc-cygwin/4.1.1/../../../../i686-pc-cygwin/include"
ignoring nonexistent directory "../../include/w32api"
#include "..." search starts here:
#include <...> search starts here:
 .
 /usr/local/gcc411/include
 /usr/local/gcc411/lib/gcc/i686-pc-cygwin/4.1.1/include
 /usr/include
 /usr/lib/../include/w32api
End of search list.
GNU C++ version 4.1.1 (i686-pc-cygwin)
 compiled by GNU C version 3.4.4 (cygming special, gdc 0.12, using dmd 0.125).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 12dba522f737a848e1f2a43498841987
/build/stdcxx/etc/config/src/BAD_ALLOC_ASSIGNMENT.cpp:81: warning: 'class std::bad_alloc'
has virtual functions but non-virtual destructor
 as -o BAD_ALLOC_WHAT.o /cygdrive/c/DOCUME~1/SCOTTZ~1.QUO/LOCALS~1/Temp/cckhl51h.s

----------------------------------------------------------------------------------------------

gcc BAD_ALLOC_WHAT.o  -v -lm -lsupc++ -lcatgets -liconv  -o BAD_ALLOC_WHAT

Using built-in specs.
Target: i686-pc-cygwin
Configured with: ./configure --prefix=/usr/local/gcc411
Thread model: single
gcc version 4.1.1
 /usr/local/gcc411/libexec/gcc/i686-pc-cygwin/4.1.1/collect2.exe -Bdynamic --dll-search-prefix=cyg
-o BAD_ALLOC_WHAT.exe /lib/crt0.o -L/usr/local/gcc411/lib/gcc/i686-pc-cygwin/4.1.1 -L/usr/local/gcc411/lib/gcc/i686-pc-cygwin/4.1.1/../../..
BAD_ALLOC_WHAT.o -lm -lsupc++ -lcatgets -liconv -lgcc -lcygwin -luser32 -lkernel32 -ladvapi32
-lshell32 -lgcc
/usr/local/gcc411/lib/gcc/i686-pc-cygwin/4.1.1/../../../libsupc++.a(new_handler.o): In function
`_ZNSt9bad_allocD2Ev':
/build/gcc-4.1.1/i686-pc-cygwin/libstdc++-v3/libsupc++/../../.././libstdc++-v3/libsupc++/new_handler.cc:47:
multiple definition of `std::bad_alloc::~bad_alloc()'
BAD_ALLOC_WHAT.o:BAD_ALLOC_WHAT.cpp:(.text$_ZNSt9bad_allocD2Ev[std::bad_alloc::~bad_alloc()]+0x0):
first defined here
BAD_ALLOC_WHAT.o:BAD_ALLOC_WHAT.cpp:(.text+0xa0b): undefined reference to `std::bad_alloc::what()
const'
BAD_ALLOC_WHAT.o:BAD_ALLOC_WHAT.cpp:(.text+0xa4f): undefined reference to `std::bad_alloc::what()
const'
collect2: ld returned 1 exit status
Yu (Scott) Zhong

________________________________

From: Mark Brown [mailto:mbrown@inbox.com]
Sent: Sat 3/10/2007 4:39 PM
To: stdcxx-dev@incubator.apache.org; stdcxx-dev@incubator.apache.org
Subject: Re: Cygwin 12d build issues



> -----Original Message-----
> From: sebor@roguewave.com
> Sent: Thu, 08 Mar 2007 17:41:22 -0700
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: Cygwin 12d build issues
>
> Mark or Farid, could one of you please open an issue for this?

Issue STDCXX-352 created: https://issues.apache.org/jira/browse/STDCXX-352

-- Mark

>
> Thanks
> Martin
>
> Farid Zaripov wrote:
>>> -----Original Message-----
>>> From: Martin Sebor [mailto:sebor@roguewave.com]
>>> Sent: Sunday, March 04, 2007 2:22 AM
>>> To: stdcxx-dev@incubator.apache.org
>>> Subject: Re: Cygwin 12d build issues
>>>
>>> Mark Brown wrote:
>>>>> -----Original Message-----
>>>>> From: mbrown@inbox.com
>>>>> Sent: Sat, 3 Mar 2007 11:33:26 -0800
>>>>> To: stdcxx-dev@incubator.apache.org
>>>>> Subject: Re: Cygwin 12d build issues
>>>>>
>>>>> Thanks. I opened issue STDCXX-346 for the -fPIC warnings.
>>> I'll post a
>>>>> patch as soon as I'm done testing it.
>>>>>
>>>>> What about the LIBC_EXCEPTIONS.exe problem with the popup window?
>>>> The other test that pops up this window is
>>> EXTERN_INLINE.exe. It says:
>>>> EXTERN_INLINE.exe has stopped working.
>>>> A problem caused the program to stop working  correctly.
>>>> Windows will close the program and notify you if a solution is
>>>> available.
>>> There shouldn't be any windows popping up when configuring,
>>> building, or using stdcxx. We have code that prevents the
>>> annoying Windows popups in tests that are expected to end
>>> abnormally (e.g., via an exception), for example,
>>> DYNAMIC_CAST.cpp, or NEW_THROWS.cpp, but I don't believe the
>>> two you mention are among them.
>>>
>>> I suppose we could introduce a common header with the code
>>> and #include it from every test to prevent these popups even
>>> when they are not anticipated. It's something to think about.
>>>
>>> In any case, please go ahead and open an issue for the problem.
>>>
>>> I don't have a Cygwin environment handy to test it right now
>>> but Farid might. Farid, if you have installed Cygwin, could
>>> you do a build and see if you can reproduce it?
>>
>>   I have just installed Cygwin. The problem is reproduced.
>>
>>   We have the code that prevent theese popups, but only in
>> THREAD_SAFE_EXCEPTIONS.cpp:
>>
>> #if defined (_WIN32)
>>     // disable displaying the critical-error-handler
>>     // and general-protection-fault message boxes
>>     // windows.h included in thread.h
>>     SetErrorMode (SEM_FAILCRITICALERRORS | SEM_NOGPFAULTERRORBOX);
>> #endif   // _WIN32
>>
>> Farid.





Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message