I have since figured out how to do this by adding -Wl, --verbose, and it
shows the library that is being found is the right one, under /lib.
I also have checked that this file contains the required symbols:
readelf -Ws libpthread.so | grep atfork 62: 0 FUNC
GLOBAL DEFAULT UND
> The error is not about whether you have definitions in your header
> files; the error is about the linker being unable to find a definition
> for `pthread_atfork` in whatever libraries you're linking against.
> I'd check whether your LDFLAGS specified to `make` are actually
> getting through to y
EDIT: I found it in /lib/libpthread-2.8.so, and it does contain
a reference to that function:
"readelf -Ws libpthread-2.8.so | grep atfork":
62: 0 FUNC GLOBAL DEFAULT UND
__register_atfork@GLIBC_2.4 (4)
218: b46c 24 FUNC GLOBAL DEFAULT 12 pthread_atfork@GLIBC_2
I forgot to say that -lpthread is in the linker arguments, and near the
end as one would expect.
The full linker commandline is:
arm-unknown-linux-gnueabi-gcc --sysroot=/home/wmt/nas-sysroot -shared
-Wl,--gc-sections -Wl,-z,defs -Wl,-soname -Wl,libsoftokn3.so
-Wl,--version-script,Linux2.6_arm_g
On Thu, Sep 5, 2019 at 8:56 AM Hamish MB wrote:
> The build gets a fair way, but eventually fails with:
>
> Linux2.6_arm_glibc_PTH_DBG.OBJ/pkcs11.o: In function `nsc_CommonInitialize':
> /home/wmt/Downloads/nss-3.25.1/nss/lib/softoken/pkcs11.c:3022: undefined
> reference to `pthread_atfork'
> coll
64
host. I haven't been able to find definitive instructions for cross
compiling NSS, so I resorted to editing coreconf/Linux.mk and
coreconf/arch.mk to hard-code the kernel version and architecture - I'm
sure this is not the right way to do it.
The build gets a fair way, but e
FYI,
I solved the CFLAGS mystery:
On 4 February 2016 at 10:59, Andrew Cagney wrote:
> ifdef CROSS_COMPILE
> DEFAULT_GMAKE_FLAGS += \
> NATIVE_CC='$(HOST_CC)' \
> CC='$(CC)' \
> CCC='$(CXX)' \
> LINK='$(LD)' \
> AS='$(AS)' \
> AR='$(AR) $(AR_FLAGS:
Hi,
I'm trying to understand the "correct" way to cross compile NSS.
The first approach I tried is based on firefox's
config/external/nss/Makefile.in where I found:
ifdef CROSS_COMPILE
DEFAULT_GMAKE_FLAGS += \
NATIVE_CC='$(HOST_CC)' \
CC='$(CC)' \
CCC='$(CXX)' \
L
Hi folks,
I have to cross compile NSS 3.15.1 for arm. I am facing certain
difficulties. If there is a web link or document which could guide me through
it, kindly suggest me.
Thanks in anticipation
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/li
George,
Another source of info on cross-compiling NSS is Mozilla's makefile
responsible for compiling NSS:
http://mxr.mozilla.org/mozilla-central/source/security/manager/Makefile.in
Search for "CROSS_COMPILE" in that makefile.
Note that this approach is different from the pre
t;
>
> --
> dev-tech-crypto mailing list
> dev-tech-crypto@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tech-crypto
>
--
View this message in context:
http://old.nabble.com/need-help-cross-compiling-nss-tp25899698p27165460.html
Sent from the Mozilla - Cryptography mailing list archive at Nabble.com.
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
nvm
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
On 10/14/2009 02:46 PM, CB wrote:
> I'm using WindRiver Linux 2.0 to cross compile nss to a PowerPC. The
> 3.11.4 build instructions and troubleshooting don't cover something
> like this. Can someone point me to documentation that would describe
> how to set the compiler, flags, install location,
I'm using WindRiver Linux 2.0 to cross compile nss to a PowerPC. The
3.11.4 build instructions and troubleshooting don't cover something
like this. Can someone point me to documentation that would describe
how to set the compiler, flags, install location, etc...?
--
dev-tech-crypto mailing list
d
14 matches
Mail list logo
