Date: Wed, 8 Aug 2018 13:04:09 -0500 From: Dmitri Goutnik <dg@syrec.org> To: Julian Elischer <julian@freebsd.org> Cc: Jan Beich <jbeich@freebsd.org>, ports FreeBSD <ports@freebsd.org>, Fernando =?utf-8?Q?Apestegu=C3=ADa?= <fernando.apesteguia@gmail.com> Subject: Re: has a framework change broken sysutils/google-compute-engine-oslogin? Message-ID: <20180808180408.GA67568@xombo.localdomain> In-Reply-To: <df19225d-44eb-51de-28bb-b9bac08c61f8@freebsd.org> References: <46136fa7-c325-d1fb-9592-9533d6263cbd@freebsd.org> <69e253cd-67e5-d3c1-10a1-3c53776e3e48@freebsd.org> <CAGwOe2YP8amVVGOfJy9hXRHJ=T8bbf-qD6sirn7b5_eWvnp8=g@mail.gmail.com> <5df77493-f59f-2666-994a-fce2031c22ee@freebsd.org> <b06208c1-a09d-c1be-44c8-c89053a638e8@freebsd.org> <pnyt-i205-wny@FreeBSD.org> <df19225d-44eb-51de-28bb-b9bac08c61f8@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18-08-09 01:16:51, Julian Elischer wrote: > On 8/8/18 6:30 pm, Jan Beich wrote: > > Julian Elischer <julian@freebsd.org> 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 BTW, it compiles fine on 112a and 104i with base clang, not sure why original Makefile had USE_GCC. -- Dmitri Goutnik dg@syrec.org | https://syrec.org/dg@syrec.org.asc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180808180408.GA67568>