[gccsdk] Building libssh2 fails while building nettle with the autobuilder. Any clues?

Alan Williams ajw at bigblue.net.au
Mon Aug 31 23:03:01 PDT 2015


I would like to be able to build !Nettle as I would like to see if I can add
public/private key authentication to it.

I have never used the auto builder before and I am at a bit of a loss to
know where to start with the error that it presented while building libssh2.

 

Along the way:

 

Autobuilder: source directory is /home/alan/build/libssh2/libssh2-1.5.0

Autobuilder: Debian patch:
0001-Add-lgpg-error-to-.pc-to-facilitate-static-linking.patch

  ...trying level 0

  ...trying level 1

patching file libssh2.pc.in

  ...success !

Autobuilder: Debian patch:
0001-Do-not-expose-private-libraries-nor-link-flags-to-us.patch

  ...trying level 0

  ...trying level 1

patching file libssh2.pc.in

  ...success !

Autobuilder: Calling setvars

Autobuilder: Calling configure command:  /home/alan/env/ro-config

RISC OS: Adding E1F filetype for ./configure

RISC OS: Adding filetype for binary tests for ./configure

RISC OS: Setting libtool library paths for ./configure

RISC OS: Adding X Paths

RISC OS: Adding SSL Path

RISC OS: Enabling shared libraries

RISC OS: Enabling static libraries

checking whether to enable maintainer-specific portions of Makefiles... no

checking for sed... /bin/sed

checking for a BSD-compatible install... /home/alan/env/ro-install

checking whether build environment is sane... yes

/home/alan/build/libssh2/libssh2-1.5.0/missing: Unknown `--is-lightweight'
option

Try `/home/alan/build/libssh2/libssh2-1.5.0/missing --help' for more
information

configure: WARNING: 'missing' script is too old or missing

checking for arm-unknown-riscos-strip...
/home/alan/cross/bin/arm-unknown-riscos-strip

checking for a thread-safe mkdir -p... /home/alan/env/mkdir -p

checking for gawk... gawk

 

 

 

Here is how it ends

 

Making all in tests

make[1]: Entering directory `/home/alan/build/libssh2/libssh2-1.5.0/tests'

/home/alan/env/arm-unknown-riscos-gcc -DHAVE_CONFIG_H -I. -I../src
-I../example  -I../src -I../include -I../src -I/home/alan/env/include  -O3
-MT ssh2.o -MD -MP -MF .deps/ssh2.Tpo -c -o ssh2.o ssh2.c

mv -f .deps/ssh2.Tpo .deps/ssh2.Po

/bin/bash ../libtool  --tag=CC   --mode=link
/home/alan/env/arm-unknown-riscos-gcc  -O3   -o ssh2,e1f ssh2.o
../src/libssh2.la

libtool: link: /home/alan/env/arm-unknown-riscos-gcc -O3 -o ssh2,e1f ssh2.o
../src/.libs/libssh2.a -L/home/alan/env/lib -lssl -lcrypto

/home/alan/env/lib/libcrypto.a(dso_dlfcn.o): In function
`dlfcn_globallookup':

dso_dlfcn.c:(.text+0x7c): undefined reference to `dlopen'

dso_dlfcn.c:(.text+0x90): undefined reference to `dlsym'

dso_dlfcn.c:(.text+0x9c): undefined reference to `dlclose'

/home/alan/env/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_func':

dso_dlfcn.c:(.text+0x454): undefined reference to `dlsym'

dso_dlfcn.c:(.text+0x4c0): undefined reference to `dlerror'

/home/alan/env/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_var':

dso_dlfcn.c:(.text+0x5a0): undefined reference to `dlsym'

dso_dlfcn.c:(.text+0x60c): undefined reference to `dlerror'

/home/alan/env/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_unload':

dso_dlfcn.c:(.text+0x6ac): undefined reference to `dlclose'

/home/alan/env/lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load':

dso_dlfcn.c:(.text+0x750): undefined reference to `dlopen'

dso_dlfcn.c:(.text+0x7b4): undefined reference to `dlclose'

dso_dlfcn.c:(.text+0x7cc): undefined reference to `dlerror'

collect2: ld returned 1 exit status

make[1]: *** [ssh2,e1f] Error 1

make[1]: Leaving directory `/home/alan/build/libssh2/libssh2-1.5.0/tests'

make: *** [all-recursive] Error 1

Package libssh2: ***Failure***

Dependency "libssh2" failed for nettle

Build for package "nettle" failed

 

That looks to me like a disparity in expectations between static and dynamic
builds for 'tests' but I couldn't see how or where to influence that.  I
presume that even if it can build them it can't run them anyway.

 

Thanks in advance to anybody to suggest how to deal with this.

Alan

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.riscos.info/pipermail/gcc/attachments/20150901/ec97eca6/attachment.html>


More information about the gcc mailing list