From owner-freebsd-ports@FreeBSD.ORG  Sun Mar  8 12:36:20 2015
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A0462882
 for <freebsd-ports@freebsd.org>; Sun,  8 Mar 2015 12:36:20 +0000 (UTC)
Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com
 [IPv6:2607:f8b0:400d:c01::22f])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 5F21A9CC
 for <freebsd-ports@freebsd.org>; Sun,  8 Mar 2015 12:36:20 +0000 (UTC)
Received: by qcxm20 with SMTP id m20so60805369qcx.0
 for <freebsd-ports@freebsd.org>; Sun, 08 Mar 2015 05:36:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=TmNgDxfUuMnXg04PNNwd+YhbRtZy34Hx2Q7IgRQh1Mk=;
 b=INVhbkcXFRMZQ4z0YdNxKUzXrVc3WCJNiwIQWPdMXbGXWG7KzV/nFUCRd2PWVwd+bw
 xiIoDhRCb2zeqXQHkca2utZ8aMTu0HZTvIW5tKLqpnahen10XnWDbIQ/ImMonQHWciVN
 5uXfoQW8LbG410dvNPs0zw6H/rvmJTO+3UPAiZOyPuVYn3Qhvs3EEl/7oJ3gKNMiYyid
 v8nTNMauq/kzzr/GM3mdyZd4A8r7i+b5pdzCQUTnWy7ZpZHn9CWfyNzAb3A6GdsQZcNn
 PnrICJdWxH5yZz6lV9MdfcyjPfAt18ECq4/vZQoCs/O6XhZv8EU0XI/NuvetIQ361rtU
 M78A==
MIME-Version: 1.0
X-Received: by 10.140.231.151 with SMTP id b145mr29830516qhc.22.1425818179587; 
 Sun, 08 Mar 2015 05:36:19 -0700 (PDT)
Received: by 10.96.158.137 with HTTP; Sun, 8 Mar 2015 05:36:19 -0700 (PDT)
In-Reply-To: <54FBEE00.6060501@rawbw.com>
References: <54FB8656.8060502@rawbw.com> <54FBDDE0.6090806@pinyon.org>
 <54FBEE00.6060501@rawbw.com>
Date: Sun, 8 Mar 2015 14:36:19 +0200
Message-ID: <CA+7WWScr2dv-=ysveV24Pg-RA1xTkf6A0D038RoL36X=NF9LFg@mail.gmail.com>
Subject: Re: Single worst bug for ports: lang/gcc* doesn't support c++11
From: Kimmo Paasiala <kpaasial@gmail.com>
To: Yuri <yuri@rawbw.com>
Content-Type: text/plain; charset=UTF-8
Cc: "Russell L. Carter" <rcarter@pinyon.org>,
 freebsd-ports <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Mar 2015 12:36:20 -0000

On Sun, Mar 8, 2015 at 8:36 AM, Yuri <yuri@rawbw.com> wrote:
> On 03/07/2015 21:28, Russell L. Carter wrote:
>>
>>
>> I would like to understand better the problem here, because I use c++11
>> features heavily with lang/gcc49 on a daily basis with zero problems.
>
>
> No, gcc-4.9.3 fails in the same way. Specific missing feature: std::snprintf
>
> error: 'snprintf' is not a member of 'std'
>
>
> Yuri

Post an example of the offending code. I suspect that the real problem
is that the code is not using an explicit 'using std::snprintf' when
it should, this is a very common problem in C++ code that has been
written at a time when including a header file was enough to bring the
std:: namespace names in that header to the global namespace. This is
no longer the case afaik on standard conformining implementations.

-Kimmo