x86_64-pc-linux-gnu-g++ '-DNO_HEAPCHECKER' '-DCHROMIUM_BUILD' '-DENABLE_REMOTING=1' '-DUSE_PROPRIETARY_CODECS' '-DENABLE_GPU=1' '-DENABLE_EGLIMAGE=1' '-DGOOGLE_PROTOBUF_NO_RTTI' '-DFEATURE_ENABLE_SSL' '-DFEATURE_ENABLE_VOICEMAIL' '-DEXPAT_RELATIVE_PATH' '-DLINUX' '-DPOSIX' '-D__STDC_FORMAT_MACROS' '-DNDEBUG' '-DNVALGRIND' '-DDYNAMIC_ANNOTATIONS_ENABLED=0' -I. -Igpu -Ithird_party/protobuf -Ithird_party/protobuf/src -Iout/Release/obj/gen/protoc_out -Ithird_party/libjingle/overrides -Ithird_party/libjingle/source -Ithird_party/expat/files -pthread -fno-exceptions -Wall -Wno-unused-parameter -Wno-missing-field-initializers -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -pipe -fPIC -fno-strict-aliasing -O2 -fno-ident -fdata-sections -ffunction-sections -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden -MMD -MF out/Release/.deps/out/Release/obj.target/chromoting_host/remoting/host/user_authenticator_linux.o.d.raw -march=amdfam10 -O2 -pipe -c -o out/Release/obj.target/chromoting_host/remoting/host/user_authenticator_linux.o remoting/host/user_authenticator_linux.cc remoting/host/user_authenticator_pam.cc:11:31: fatal error: security/pam_appl.h: No such file or directory compilation terminated. make: *** [out/Release/obj.target/chromoting_host/remoting/host/user_authenticator_pam.o] Error 1 make: *** Waiting for unfinished jobs.... chromium-11.0.672.2-r2 built successfully.
Please attach the entire build log and paste your `emerge --info' output in a comment.
This is a real thing, no need to post more details this time. Thank you for reporting. There is an upstream discussion at http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/3b7490cf60f56609# One possible solution is just add sys-libs/pam to the dependencies, but I'd like to explore other possible options too (like making chromoting support optional, and so on).
Fixed in >=www-client/chromium-11.0.686.3
Seems that it can be made optional after all: http://www.linuxquestions.org/questions/slackware-14/chromium-began-require-pam-865109/page2.html#post4273188
(In reply to comment #4) > Seems that it can be made optional after all: > > http://www.linuxquestions.org/questions/slackware-14/chromium-began-require-pam-865109/page2.html#post4273188 Doing that will increase maintenance effort. It seems that upstream doesn't really want to explain why PAM is needed inside the browser for remoting, so for now I'd rather avoid changing that.
