From owner-freebsd-ports@freebsd.org Tue Aug 14 02:29:36 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 384A21065C3A for ; Tue, 14 Aug 2018 02:29:36 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B3E1079849 for ; Tue, 14 Aug 2018 02:29:35 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 784F31065C36; Tue, 14 Aug 2018 02:29:35 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5667A1065C34 for ; Tue, 14 Aug 2018 02:29:35 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0222679846; Tue, 14 Aug 2018 02:29:34 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (106-69-226-241.dyn.iinet.net.au [106.69.226.241]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id w7E2TI5N011641 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 13 Aug 2018 19:29:22 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: has a framework change broken sysutils/google-compute-engine-oslogin? To: Helen Koike , Jan Beich , ports FreeBSD , =?UTF-8?Q?Fernando_Apestegu=c3=ada?= References: <46136fa7-c325-d1fb-9592-9533d6263cbd@freebsd.org> <69e253cd-67e5-d3c1-10a1-3c53776e3e48@freebsd.org> <5df77493-f59f-2666-994a-fce2031c22ee@freebsd.org> <20180808180408.GA67568@xombo.localdomain> <11ebf847-4b06-e53c-9ff1-7fcb0e9590c3@collabora.com> From: Julian Elischer Message-ID: Date: Tue, 14 Aug 2018 10:28:06 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <11ebf847-4b06-e53c-9ff1-7fcb0e9590c3@collabora.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 02:29:36 -0000 On 13/8/18 9:16 pm, Helen Koike wrote: > Hi all, > > On 08/08/2018 03:04 PM, Dmitri Goutnik wrote: >> On 18-08-09 01:16:51, Julian Elischer wrote: >>> On 8/8/18 6:30 pm, Jan Beich wrote: >>>> Julian Elischer writes: >>>> >>>>> g++ -O2 -pipe -DPANZURA_DEV -DPZ_LONGNAMES -fstack-protector -isystem >>>>> /usr/local/include -fno-strict-aliasing -isystem /usr/local/include >>>>> -fPIC -c pam_module/pam_oslogin_login.cc -o >>>>> pam_module/pam_oslogin_login.o >>>>> g++ -fstack-protector -I/usr/local/include/json-c -o >>>>> google_authorized_keys authorized_keys/authorized_keys.cc >>>>> utils/oslogin_utils.cc -lcurl -ljson-c >>>>> g++ -fstack-protector -Wall -Wstrict-prototypes -fPIC -shared >>>>> -Wl,-soname,libnss_cache_oslogin.so.2 -o >>>>> libnss_cache_google-compute-engine-oslogin-1.3.0.so >>>>> libnss_cache_oslogin/nss_cache_oslogin.o >>>>> libnss_cache_oslogin/compat/getpwent_r.o >>>>> utils/oslogin_utils.cc:16:23: error: curl/curl.h: No such file or >>>>> directory >>>>> utils/oslogin_utils.cc:16:23: error: curl/curl.h: No such file or >>>>> directory >>>> - GCC 4.2.1 (patched) from base system is not a supported configuration >>>> on i386/amd64/aarch64/armv6/armv7 >>>> - C*FLAGS aren't consistently respected, see >>>> https://wiki.freebsd.org/WarnerLosh/UsrLocal#Include_paths >>>> https://www.freebsd.org/doc/en/books/porters-handbook/dads-cflags.html >>>> >>>> $ g++7 -v -xc++ - >>>> [...] >>>> ignoring nonexistent directory "/usr/local/lib/gcc7/gcc/x86_64-portbld-freebsd12.0/7.3.0/include-fixed" >>>> ignoring nonexistent directory "/usr/local/lib/gcc7/gcc/x86_64-portbld-freebsd12.0/7.3.0/../../../../../x86_64-portbld-freebsd12.0/include" >>>> #include "..." search starts here: >>>> #include <...> search starts here: >>>> /usr/local/lib/gcc7/include/c++/ >>>> /usr/local/lib/gcc7/include/c++//x86_64-portbld-freebsd12.0 >>>> /usr/local/lib/gcc7/include/c++//backward >>>> /usr/local/lib/gcc7/gcc/x86_64-portbld-freebsd12.0/7.3.0/include >>>> /usr/local/include <-- HERE is why pkg-fallout@ is silent >>> Sorry you are out of my area of knowledge.. >>> All I know is that the port no longer compiles under amd64. >>> though It did some months back. >>> How it selects the compiler to use I have no clue.. >>> I got my pkg using make.conf but that is not a sustainable answer. >>> >>>> /usr/include >>>> End of search list. >>>> >>> _______________________________________________ >>> freebsd-ports@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >> Hi Julian, >> >> As Jan said, port's Makefile is broken in a sense that not all of its binary >> targets respect CXXFLAGS. I took a stab at unbreaking the build, see >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230466 > Sorry to take so long to reply. Thanks a lot for the patch. > >> BTW, it compiles fine on 112a and 104i with base clang, not sure why original >> Makefile had USE_GCC. Ok so thanks to everyone.  It's been educational. Will the change in the bug be checked in? Every few months I recompile all the packages we need at $JOB and each time the hope is that we can get all the way through, tough there is nearly always one that falls over in some new way.. (we install a couple of hundred packages. this time it was sysutils/google-compute-engine-oslogin (and a couple of others..) Hopefully the fixes that go in this time will give me (false) hope of a clean run next time  :-) >> > Because of my lack of experience. Ah but you did do the port, for which I thank you!. > > > I couldn't reproduce the error with USE_GCC though https://paste.ee/p/FXNiv > Maybe it is something in my environment (g++6 maybe). > > Thank you all > Helen >