Re: Message during linking

Eric Lilja wrote: > Dave Korn wrote: >> It has started to happen now because libstdc++ is a DLL for the first >> time. We've fixed upstream ld to enable the feature by default and these >> warnings will disappear in the next binutils release. Hmm, it occurs to me that for the benefit of users w

Re: Message during linking

Dave Korn wrote: It has started to happen now because libstdc++ is a DLL for the first time. We've fixed upstream ld to enable the feature by default and these warnings will disappear in the next binutils release. Ok, sounds great! And the benefits of a libstdc++ as a DLL is reduced code si

Re: Message during linking

Eric Lilja wrote: > g++ command_line.o grep.o scanner.o -s -o my_grep.exe > Info: resolving typeinfo for std::runtime_error by linking to > __imp___ZTISt13runtime_error (auto-import) > Info: resolving std::cout by linking to __imp___ZSt4cout (auto-import) > Info: resolving std::cerr by linking t

Re: Message during linking

Kai Tietz wrote: Hello Eric, Hello Kai and thanks for your swift reply! Here's the very simple Makefile that was used: CXX = g++ CXXFLAGS = -Wall -Wextra -std=c++98 -pedantic -Werror -c LDFLAGS = -s -o $(EXEC) Add to your LDFLAGS --enable-auto-import --enable-auto-import did nothing, ho

Re: Message during linking

Hello Eric, > Here's the very simple Makefile that was used: > CXX = g++ > CXXFLAGS = -Wall -Wextra -std=c++98 -pedantic -Werror -c > LDFLAGS = -s -o $(EXEC) Add to your LDFLAGS --enable-auto-import That should remove those warnings for you. Cheers, Kai Regards, i.A. Kai Tietz | (\_/) Thi

Message during linking

Hi, I have a small utility written in C++ that I made for cygwin 1.5.x and g++ 3.4.4 a few years ago. I just tried to build it under the latest test release of cygwin 1.7 with the latest test release of g++ 4.3.2. First it didn't compile due to a missing include but I remember that one of the t