Good afternoon,
Have found what seems to be a bug in the generate-release.sh script. When
running the command for example :
sh generate-release.sh releng/10.0 /expert/release-generada
it fails when stats building pkg in the chrooted env. I think this is because
in the chroot env are not
)
libcrypto.so.7 = /lib/libcrypto.so.7 (0x801cb8000)
libthr.so.3 = /lib/libthr.so.3 (0x8020a3000)
Thank you so much Olli,
Regards!
perhaps you're
El 09/04/2014, a las 01:40, olli hauer oha...@gmx.de escribió:
On 2014-04-08 12:03, Egoitz Aurrekoetxea wrote:
Hi,
Have tried building
Hi,
Have tried building Apache on a recently upgraded ports collection for linking
Apache, php and all against openssl new port…. but no way of ending up that
way….
I see always :
ldd /usr/local/libexec/apache22/mod_ssl.so
/usr/local/libexec/apache22/mod_ssl.so:
libssl.so.7 =
/lib/libssl.so.8 (0x800af2000)
libcrypto.so.8 = /usr/local/lib/libcrypto.so.8 (0x800d58000)
libc.so.7 = /lib/libc.so.7 (0x801154000)
libthr.so.3 = /lib/libthr.so.3 (0x8014ed000)
El 08/04/2014, a las 12:03, Egoitz Aurrekoetxea ego...@ramattack.net escribió:
Hi,
Have
Hello all,
One little question. I have package collections of packages made (packages
created by compiling ports and later pkg_create -Rb) for my freebsd provisioned
releases with the servers I need to provision (mail, web, etc)...
now imagine, someone in some of those provisioned servers
