Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Jul 2013 10:31:49 +0100 (BST)
From:      Anton Shterenlikht <mexas@bris.ac.uk>
To:        freebsd-questions@freebsd.org, Olivier.Nicole@cs.ait.ac.th
Subject:   Re: What compiler is used to build a port
Message-ID:  <201307010931.r619Vnd3078758@mech-cluster241.men.bris.ac.uk>
In-Reply-To: <201307010836.r618akZ2098114@banyan.cs.ait.ac.th>

next in thread | previous in thread | raw e-mail | index | archive | help
	Date: Mon, 1 Jul 2013 15:36:46 +0700 (ICT)
	From: Olivier Nicole <Olivier.Nicole@cs.ait.ac.th>
	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@.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201307010931.r619Vnd3078758>