X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49E2888A.5080906@nc.rr.com> Date: Sun, 12 Apr 2009 20:34:18 -0400 From: Brian and Victoria User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygwin1.7, g++ 4.3.2 (with -std=c++0x) and undefined references to snprintf() References: <49E27B93 DOT 8090601 AT nc DOT rr DOT com> In-Reply-To: <49E27B93.8090601@nc.rr.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Brian and Victoria wrote: > I've exhausted my google-fu and am hoping someone on the list has > superior powers... > > I'm on the bleeding edge, using cygwin 1.7 and g++ 4.3.2 with > -std=c++0x (enables C++0x experimental features, and access to > variadic template parameters in my case). > > Prior to switching on c++0x, there were no problems. Afterwards > though, the linker (via g++) complains about undefined references to > snprintf(). I'm linking with "stdc++", and tried also linking with > "c" (C99 library) as well, but no luck. Anyone else running into this? > > I've got a build in progress with -std=gnu++0x instead (GNU dialect of > the experimental C++0x features), and will see how that goes. This has resolved the problem, so something may be amiss with the standard dialect or there's something forgiving about the GNU dialect. -Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/