simple-chrome: No package 'nss' found

[Dylan Reid]

I started from a clean chromium checkout and I get the following when
getting ready to build. Has anyone else seen this?

(sdk eve R63-9970.0.0) src$ gn gen out_eve/Release --args="$GN_ARGS"
ERROR at //build/config/linux/pkg_config.gni:103:17: Script returned
non-zero exit code.
pkgresult = exec_script(pkg_config_script, args, "value")
^----------
Current dir: /scratch/chromium/src/out_eve/Release/
Command: python --
/scratch/chromium/src/build/config/linux/pkg-config.py -p pkg-config
nss -v -lssl3
Returned 1.
stderr:

Package nss was not found in the pkg-config search path.
Perhaps you should add the directory containing `nss.pc'
to the PKG_CONFIG_PATH environment variable
No package 'nss' found
Could not run pkg-config.

See //third_party/nss/BUILD.gn:15:3: whence it was called.
pkg_config("system_nss_no_ssl_config") {
^---------------------------------------
See //crypto/BUILD.gn:221:25: which caused the file to be included.
public_configs += [ "//third_party/nss:system_nss_no_ssl_config" ]
^-------------------------------------------
(sdk eve R63-9970.0.0) src$

[Mike Frysinger]

we def have nss & its .pc file in the sysroot for simple chrome.  i'm guessing the pkg-config wrapper isn't looking in the right place though.

$ PKG_CONFIG_LIBDIR=$SYSROOT/usr/lib64/pkgconfig pkg-config --libs nss 

-L/usr/lib64 -lssl3 -lsmime3 -lnss3 -lnssutil3 -lplds4 -lplc4 -lnspr4

-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Dylan Reid]

Thanks, adding the libdir to gn gen fixed it.

PKG_CONFIG_LIBDIR=$SYSROOT/usr/lib64/pkgconfig gn gen out_eve/Release
--args="$GN_ARGS"

[Mike Frysinger]

that really shouldn't have been necessary though :/

i'm wondering if no one is noticing this bug because all the systems where we run Simple Chrome happen to have nss dev files installed in /

-mike

[Puneet Kumar]

+Miao-chen Chou and +Dmitry Grinberg were seeing this yesterday and want to make sure they see this.  But that's a clear case of others hitting it too

---
You received this message because you are subscribed to the Google Groups "Chromium OS dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

--

Puneet

[Dylan Reid]

I spoke too soon. With the path to nss added it configured but
wouldn't build because of missing headers from the nss library.

/scratch/chromium/.cros_cache/common/goma+2/gomacc
/scratch/chromium/src/third_party/llvm-build/Release+Asserts/bin/clang++
-MMD -MF host/obj/crypto/crypto/nss_key_util.o.d
-DCRYPTO_IMPLEMENTATION -DV8_DEPRECATION_WARNINGS -DUSE_UDEV
-DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DFULL_SAFE_BROWSING
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD
-DFIELDTRIAL_TESTING_ENABLED -DCR_CLANG_REVISION=\"313786-1\"
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
-D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Ihost/gen
-I../../third_party/boringssl/src/include -I/usr/include/nss
-I/usr/include/nspr -fno-strict-aliasing --param=ssp-buffer-size=4
-fstack-protector -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__=
-D__TIMESTAMP__= -funwind-tables -fPIC -pipe
-B../../third_party/binutils/Linux_x64/Release/bin -pthread
-fcolor-diagnostics -m64 -march=x86-64 -Wall -Wextra
-Wno-missing-field-initializers -Wno-unused-parameter
-Wno-c++11-narrowing -Wno-covered-switch-default
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override
-Wno-undefined-var-template -Wno-nonportable-include-path
-Wno-address-of-packed-member -Wno-unused-lambda-capture
-Wno-user-defined-warnings -Wno-enum-compare-switch
-Wno-tautological-unsigned-zero-compare -Wno-null-pointer-arithmetic
-Wno-tautological-unsigned-enum-zero-compare -O2 -fno-ident
-fdata-sections -ffunction-sections -fomit-frame-pointer -g2
-gsplit-dwarf -fvisibility=hidden -Wheader-hygiene -Wstring-conversion
-Wtautological-overlap-compare -Wno-header-guard -std=gnu++14
-fno-rtti -nostdinc++
-isystem../../buildtools/third_party/libc++/trunk/include
-isystem../../buildtools/third_party/libc++abi/trunk/include
-fno-exceptions -fvisibility-inlines-hidden
-Wno-unknown-warning-option -c ../../crypto/nss_key_util.cc -o
host/obj/crypto/crypto/nss_key_util.o
In file included from ../../crypto/nss_key_util.cc:5:
In file included from ../../crypto/nss_key_util.h:14:
../../crypto/scoped_nss_types.h:8:10: fatal error: 'keyhi.h' file not found
#include <keyhi.h>
^~~~~~~~~
1 error generated.
[583/28386] CXX host/obj/crypto/crypto/nss_util.o
FAILED: host/obj/crypto/crypto/nss_util.o
/scratch/chromium/.cros_cache/common/goma+2/gomacc
/scratch/chromium/src/third_party/llvm-build/Release+Asserts/bin/clang++
-MMD -MF host/obj/crypto/crypto/nss_util.o.d -DCRYPTO_IMPLEMENTATION
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1
-DUSE_OZONE=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD
-DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED
-DCR_CLANG_REVISION=\"313786-1\" -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Ihost/gen
-I../../third_party/boringssl/src/include -I/usr/include/nss
-I/usr/include/nspr -fno-strict-aliasing --param=ssp-buffer-size=4
-fstack-protector -Wno-builtin-macro-redefined -D__DATE__= -D__TIME__=
-D__TIMESTAMP__= -funwind-tables -fPIC -pipe
-B../../third_party/binutils/Linux_x64/Release/bin -pthread
-fcolor-diagnostics -m64 -march=x86-64 -Wall -Wextra
-Wno-missing-field-initializers -Wno-unused-parameter
-Wno-c++11-narrowing -Wno-covered-switch-default
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override
-Wno-undefined-var-template -Wno-nonportable-include-path
-Wno-address-of-packed-member -Wno-unused-lambda-capture
-Wno-user-defined-warnings -Wno-enum-compare-switch
-Wno-tautological-unsigned-zero-compare -Wno-null-pointer-arithmetic
-Wno-tautological-unsigned-enum-zero-compare -O2 -fno-ident
-fdata-sections -ffunction-sections -fomit-frame-pointer -g2
-gsplit-dwarf -fvisibility=hidden -Wheader-hygiene -Wstring-conversion
-Wtautological-overlap-compare -Wno-header-guard -std=gnu++14
-fno-rtti -nostdinc++
-isystem../../buildtools/third_party/libc++/trunk/include
-isystem../../buildtools/third_party/libc++abi/trunk/include
-fno-exceptions -fvisibility-inlines-hidden
-Wno-unknown-warning-option -c ../../crypto/nss_util.cc -o
host/obj/crypto/crypto/nss_util.o
../../crypto/nss_util.cc:8:10: fatal error: 'pk11pub.h' file not found
#include <pk11pub.h>
^~~~~~~~~~~
1 error generated.
[1059/28383] CXX obj/v8/v8_base/api.o
ninja: build stopped: subcommand failed.

[Mike Frysinger]

i'm confused why it's also using the Chromium compiler instead of the CrOS one:

/scratch/chromium/src/third_party/llvm-build/Release+Asserts/bin/clang++

something is wonky on the gn side.

-mike

>> email to chromium-os-dev+unsubscribe@chromium.org.
>
> --
>
> Puneet

[Dylan Reid]

Has anyone gotten simplechrome to work in the past couple of days?

>> >> email to chromium-os-d...@chromium.org.
>> >
>> > --
>> >
>> > Puneet
>
>

[Puneet Kumar]

This is precisely what the bt team had been complaining about all of yesterday BTW. The answer is no.

--

Puneet

[Dylan Reid]

Maybe we should change the subject to "PSA: simplechrome is broken".
Is there a bug tracking this? I'll try again tomorrow... or Monday:)

[Luigi Semenzato]

By "trying simplechrome in the last couple of days" do you mean after
a source sync? Because I compiled (locally, not with goma) yesterday
at 2 and it was fine. But my last sync was on Tuesday.

[sk...@chromium.org]

My simple chrome has also been broken.  However, mine is complaining that it can't find cups-config.  Thankfully, I have a working chroot for the board I'm using so I'm using:

cros chrome-sdk --board=$board --chroot=$path_to_my_cros_repo/chroot

>> >> >> email to chromium-os-dev+unsubscribe@chromium.org.
>> >> >
>> >> > --
>> >> >
>> >> > Puneet
>> >
>> >
>
> --
>
> Puneet

[Chris Sosa]

+stevenjb

Chris Sosa
Always Be Continually Integrating

[Steven Bennetts]

Has anyone filed a bug for this? That seems like a better way to track the problem than email. I haven't done a recent simple chrome build but it was working for me yesterday for samus. I'll try ToT when I get in tomorrow.

[Mike Frysinger]

i don't think we have a bug.  i think we were hoping to hash out an obvious pebkac and then the thread would die :).  looks like we need to move on to the next step (bug+investigation).

-mike

[Junichi Uekawa (上川純一)]

I just tried mine (sdk kevin R63-9972.0.0) 

Hidehiko was telling me he couldn't build simplechrome yesterday and I tried to reproduce it on my kevin chroot but it didn't fail.

git pull --rebase 

GOMA_TMP_DIR=/tmp/goma_uekawa cros chrome-sdk --board=kevin  --internal

GYP_DEFINES="branding=Chrome buildtype=Official $GYP_DEFINES" gclient sync -j16

gn gen out_$SDK_BOARD/Release --args="$GN_ARGS"

ninja -C out_${SDK_BOARD}/Release -j1000 chrome chrome_sandbox nacl_helper

uekawa@uekawa-4 ~/src/chrome1/src $ ninja -C out_${SDK_BOARD}/Release -j1000 chrome chrome_sandbox nacl_helper

I suspected that eve sdk was stale but maybe not.

[Hidehiko Abe]

Yes, I hit yesterday. Though, at some point, it was fixed mysteriously.

Today, I sync'ed again, and then hit the same issue.

Chrome looks repeatedly crashing. Here is a stackdump, I could obtain.

INFO    : Dumping stack for chrome.20170929.181733.1752.dmp with /build/caroline

/usr/lib/debug/breakpad:

Operating system: Linux

                  0.0.0 Linux 3.18.0-16068-g71066a770e8e #1 SMP PREEMPT Wed Sep 

27 21:56:20 PDT 2017 x86_64

CPU: amd64

     family 6 model 78 stepping 3

     1 CPU

GPU: UNKNOWN

Crash reason:  SIGSEGV

Crash address: 0x0

Process uptime: not available

Thread 0 (crashed)

 0  ld-2.23.so!_dl_relocate_object [dl-reloc.c : 232 + 0x0]

    rax = 0x0000000000000000   rdx = 0x0000000000000001

    rcx = 0x0000000000000000   rbx = 0x0000000000000001

    rsi = 0x0000000000000000   rdi = 0x000071cb47ce9128

    rbp = 0x00007ffe99ec1230   rsp = 0x00007ffe99ec1120

     r8 = 0xffffffffffffffff    r9 = 0x0000000000000001

    r10 = 0x0000000000000022   r11 = 0x0000000000000206

    r12 = 0x0000000000000001   r13 = 0x0000000000000000

    r14 = 0x000071cb47ce8998   r15 = 0x000071cb47ce9128

    rip = 0x000071cb47acec32

    Found by: given as instruction pointer in context

 1  ld-2.23.so!dl_main [rtld.c : 2106 + 0x20]

    rbx = 0x0000000000000000   rbp = 0x00007ffe99ec1320

    rsp = 0x00007ffe99ec1240   r12 = 0x000071cb47ce9128

    r13 = 0x0000000000000000   r14 = 0x000071cb47ce8998

    r15 = 0x000071cb47ce9128   rip = 0x000071cb47ac676d

    Found by: call frame info

 2  ld-2.23.so!_dl_sysdep_start [dl-sysdep.c : 249 + 0x15]

    rbx = 0x00000000029c67af   rbp = 0x00007ffe99ec1360

    rsp = 0x00007ffe99ec1330   r12 = 0x00006151b8660040

    r13 = 0x000000000000000a   r14 = 0x000071cb47ac4b10

    r15 = 0x000071cb47ac34f8   rip = 0x000071cb47adb0ac

    Found by: call frame info

 3  ld-2.23.so!_dl_start [rtld.c : 307 + 0x5]

    rbx = 0x0000000000000000   rbp = 0x00007ffe99ec13d0

    rsp = 0x00007ffe99ec1370   r12 = 0x00007ffe99ec13e0

    r13 = 0x000071cb47ac3a08   r14 = 0x000071cb47ac3000

    r15 = 0x000071cb47ac34f8   rip = 0x000071cb47ac7ef9

    Found by: call frame info

 4  ld-2.23.so + 0xd48

    rbx = 0x0000000000000000   rbp = 0x0000000000000000

    rsp = 0x00007ffe99ec13e0   r12 = 0x0000000000000000

    r13 = 0x0000000000000000   r14 = 0x0000000000000000

    r15 = 0x0000000000000000   rip = 0x000071cb47ac3d48

    Found by: call frame info

Loaded modules:

0x6151b8660000 - 0x6151c2234fff  chrome  ???  (main)

0x71cb47ac3000 - 0x71cb47ae6fff  ld-2.23.so  ???

0x7ffe99f47000 - 0x7ffe99f48fff  linux-gate.so  ???