Hi, > > rm -fr tmp and ./build-complete --build-depcache = exact same result. > > Searching for openvpn bin > :/home/tct/openvpn/bsys/windows-nsis# find tmp | grep vpn | grep bin > tmp/image-x86_64/openvpn/bin > tmp/image-x86_64/openvpn/bin/openssl.exe > tmp/image-x86_64/openvpn/bin/liblzo2-2.dll > tmp/image-x86_64/openvpn/bin/ssleay32.dll > tmp/image-x86_64/openvpn/bin/libpkcs11-helper-1.dll > tmp/image-x86_64/openvpn/bin/c_rehash > tmp/image-x86_64/openvpn/bin/libeay32.dll > tmp/image-i686/openvpn/bin > tmp/image-i686/openvpn/bin/openssl.exe > tmp/image-i686/openvpn/bin/liblzo2-2.dll > tmp/image-i686/openvpn/bin/ssleay32.dll > tmp/image-i686/openvpn/bin/libpkcs11-helper-1.dll > tmp/image-i686/openvpn/bin/c_rehash > tmp/image-i686/openvpn/bin/libeay32.dll > > From what I can tell (tho my sh foo is not great) > ./build-complete --build-depcache does not build openvpn > eg: > ./build-complete --help > --build-depcache create depcache only (no program build) > > but then expects openvpn to be there .. ?
Yes, depcache does not build OpenVPN, only the dependencies. I'll have
to do some testing to figure out what it is doing and whether this is a
feature or a bug. I recall having some depcache-related issue a while
back which vaguely resembles this one.
> Another thing I notice which i think must be an error while building
> openssl:
>
> created directory
> `/home/tct/openvpn/bsys/windows-nsis/tmp/build-x86_64/depcache-root//bin'
> created directory
> `/home/tct/openvpn/bsys/windows-nsis/tmp/build-x86_64/depcache-root///lib'
> created directory
> `/home/tct/openvpn/bsys/windows-nsis/tmp/build-x86_64/depcache-root///lib/engines'
>
> created directory
> `/home/tct/openvpn/bsys/windows-nsis/tmp/build-x86_64/depcache-root///lib/pkgconfig'
>
> created directory
> `/home/tct/openvpn/bsys/windows-nsis/tmp/build-x86_64/depcache-root//include'
>
> created directory
> `/home/tct/openvpn/bsys/windows-nsis/tmp/build-x86_64/depcache-root//include/openssl'
>
> created directory
> `/home/tct/openvpn/bsys/windows-nsis/tmp/build-x86_64/depcache-root/etc'
> created directory
> `/home/tct/openvpn/bsys/windows-nsis/tmp/build-x86_64/depcache-root/etc/ssl'
>
>
> //bin, ///lib & //include .. is this intentional and it occurs many
> times throughout the log ?
This is probably due an extra "/"(s) somewhere. Not a problem, but looks
silly and should be fixed if possible.
> Also, windows-nsis/tmp/build-x86_64/depcache-root does not exist once
> the script fails .. (nor i686)
>
> Finally, "FATAL: please specify openvpn binary tarball" AFAICT, the
> tarball is specified by build-complete:
>
> ROOT="${TMPDIR}/installer" \
> ./build \
> --installer-version="${INSTALLER_VERSION}" \
> --special-build="${SPECIAL_BUILD}" \
> --openvpn-bin-tarball-i686=$(ls
> ${TMPDIR}/image-i686/openvpn-i686-*-bin.*) \
> --openvpn-bin-tarball-x86_64=$(ls
> ${TMPDIR}/image-x86_64/openvpn-x86_64-*-bin.*) \
>
> So that error message is a bit misleading, maybe it could read
> "FATAL: cannot find specified openvpn binary tarball
> $(ls ${TMPDIR}/image-i686/openvpn-i686-*-bin.*)"
>
>
>>
>> If this is a bug then we should add a --build-depcache test to Travis so
>> that the depcache does not break again.
>>
>
> I can open a ticket for it, if it is a bug ? let me know
>
Not sure at this point, but I'll investigate.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
0x40864578.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
