has a framework change broken sysutils/google-compute-engine-oslogin?

[Helen Koike]

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 <julian at 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 at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at 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.
> 

Because of my lack of experience.


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