From owner-freebsd-questions@FreeBSD.ORG Mon Jul 1 09:32:25 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E48C1F2F for ; Mon, 1 Jul 2013 09:32:25 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog115.obsmtp.com (eu1sys200aog115.obsmtp.com [207.126.144.139]) by mx1.freebsd.org (Postfix) with ESMTP id 4B6811C92 for ; Mon, 1 Jul 2013 09:32:24 +0000 (UTC) Received: from mail-wg0-f48.google.com ([74.125.82.48]) (using TLSv1) by eu1sys200aob115.postini.com ([207.126.147.11]) with SMTP ID DSNKUdFMiRii8ZiOnCzfW69TICvcZtryKTUm@postini.com; Mon, 01 Jul 2013 09:32:25 UTC Received: by mail-wg0-f48.google.com with SMTP id f11so3497023wgh.15 for ; Mon, 01 Jul 2013 02:31:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:date:from:message-id:to:subject:reply-to:in-reply-to :x-gm-message-state; bh=lFU20Zn44PEjg7B9F+tpGamiA9Y3b969yd7755g2qsw=; b=URz3fqDPPH9NCeYtW7Oi9HSLMKIdgGuFrfk3DUj6Q1yIezYCYS9jR45hsDYg8WShYj sy37klRb2aaIbTudcSZgouiNHCjrRmowJpruX/fSu5lyJfuBwJIsw32qhgYJnRUqUZLJ 2m7+U3WF40KcUpGWV9CUh33zhnUDMK8Fpi7RKkU2qJsi5wrXb8h8nHB0v9Go3oAobNOZ QSVPBddSZZ0Wyvnke5S7cFSngfJCd+8UcUtYMksLcnPZ63qD2UhxGkHlfaWM5Ur9i2Vx 1IDF+TlYl0h5en+ku29zxrfWs1jtTPKbQNAJ92cPhk4UAA3PAfmUHRDAUurK3eQNtKN4 3wTQ== X-Received: by 10.194.20.97 with SMTP id m1mr19229106wje.31.1372671112910; Mon, 01 Jul 2013 02:31:52 -0700 (PDT) X-Received: by 10.194.20.97 with SMTP id m1mr19229103wje.31.1372671112842; Mon, 01 Jul 2013 02:31:52 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id cd11sm14969202wib.10.2013.07.01.02.31.50 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 02:31:51 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r619VnHu078759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 1 Jul 2013 10:31:49 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r619Vnd3078758; Mon, 1 Jul 2013 10:31:49 +0100 (BST) (envelope-from mexas) Date: Mon, 1 Jul 2013 10:31:49 +0100 (BST) From: Anton Shterenlikht Message-Id: <201307010931.r619Vnd3078758@mech-cluster241.men.bris.ac.uk> To: freebsd-questions@freebsd.org, Olivier.Nicole@cs.ait.ac.th Subject: Re: What compiler is used to build a port In-Reply-To: <201307010836.r618akZ2098114@banyan.cs.ait.ac.th> X-Gm-Message-State: ALoCoQkYGXgCtd/HJe9NiXa4hXKRSjvlNz1V6196+h4yn0Gv6AiQj7jmHo4K2w0RdtoZgiUKfQsAif+Jpz2ZB1Pa+hbh5Roc3P3lx6NbEh0ScpBFh5z2T/67IJLyaZaw2kSqaVNMUQcfpD/Utx4cY98BpKmEvTN85rkK43h11Lk9YwxBwZMGvenrWLsV5G9jN6oyxkwlMlEx X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jul 2013 09:32:26 -0000 Date: Mon, 1 Jul 2013 15:36:46 +0700 (ICT) From: Olivier Nicole To: freebsd-questions@freebsd.org Subject: What compiler is used to build a port Hi, I have a strange situation: 2 machines, 9.1 p4, on the first machine, graphicslibfpx build with the stock compiler: $ make ===> Fetching all distfiles required by libfpx-1.3.1.1 for building ===> Extracting for libfpx-1.3.1.1 => SHA256 Checksum OK for libfpx-1.3.1-1.tar.xz. ===> Patching for libfpx-1.3.1.1 ===> Applying FreeBSD patches for libfpx-1.3.1.1 /usr/bin/sed -i '' -e '/^#include "fpxlib-config.h"/d' /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/basics/filename.cpp /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/oless/h/owchar.h /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ole/gen_guid.cpp /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/fpxlib.h ===> Configuring for libfpx-1.3.1.1 ===> Building for libfpx-1.3.1.1 Warning: Object directory not changed from original /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1 g++ -O2 -pipe -DHAVE_WCHAR_H -DHAVE_DLFCN_H -DHAVE_SYS_TIME_H... and on the other machine it insists on using gcc >4.4 (which is actually a mistake, libfpx will *not* compile with gcc 4.4 or gcc 4.6): $ make ===> Fetching all distfiles required by libfpx-1.3.1.1 for building ===> Extracting for libfpx-1.3.1.1 => SHA256 Checksum OK for libfpx-1.3.1-1.tar.xz. ===> Patching for libfpx-1.3.1.1 ===> Applying FreeBSD patches for libfpx-1.3.1.1 /usr/bin/sed -i '' -e '/^#include "fpxlib-config.h"/d' /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/basics/filename.cpp /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/oless/h/owchar.h /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ole/gen_guid.cpp /usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/fpxlib.h ===> libfpx-1.3.1.1 depends on executable: gcc46 - not found ===> Verifying install for gcc46 in /usr/ports/lang/gcc Making GCC 4.6.3 for x86_64-portbld-freebsd9.1 [c,c++,objc,fortran,java] ===> Found saved configuration for gcc-4.6.3 ===> Fetching all distfiles required by gcc-4.6.3 for building ===> Extracting for gcc-4.6.3 => SHA256 Checksum OK for gcc-4.6.3.tar.bz2. ===> gcc-4.6.3 depends on file: /usr/local/bin/perl5.14.4 - found What could cause aport to request for a different compiler version when both machines are very similar? Best regards, Olivier It seems you have different revisions of the ports tree on the two boxes. Do svn info /usr/ports on both boxes, and see what revisions they have. On amd64 with ports at r322188 it builds using the system GCC compiler: http://eis.bris.ac.uk/~mexas/libfpx-amd64-r322188-build.log but looking at the port's svn log (svn log /usr/ports/graphics/libfpx) shows ------------------------------------------------------------------------ r311828 | miwi | 2013-02-07 12:36:20 +0000 (Thu, 07 Feb 2013) | 2 lines - Unbreak build for HEAD Maybe your gcc-46 build is on a box with ports tree prior to that revision? Anton P.S. In cases like these I usually email the maintainer and copy to ports@.