update bacula-server 5.0.2 -> 5.0.3, Undefined symbol "ASN1_INTEGER_it

olli hauer ohauer at gmx.de
Mon Sep 20 21:11:52 UTC 2010

On 2010-09-20 22:58, Per olof Ljungmark wrote:
> On 09/20/10 19:39, olli hauer wrote:
>> On 2010-09-19 08:20, Per olof Ljungmark wrote:
>>> FreeBSD 7.3-STABLE #0: Tue Sep  7 22:46:59 CEST 2010
>>> peo at candyman.i.inter-sonic.com:/usr/obj/usr/src/sys/GENERIC  amd64
>>> Portupgrade of bacula-server 5.0.2 -> 5.0.3
>>> Starting bacula_fd.
>>> /libexec/ld-elf.so.1: /usr/local/lib/libbac.so.5: Undefined symbol
>>> "ASN1_INTEGER_it"
>>> Starting bacula_sd.
>>> Starting bacula_dir.
>>> If one deselects "OPENSSL" and recompile bacula-fd will start without
>>> complaints.
>>> Is this a known issue with 5.0.3?
>> No, can you provide me some more details.
>> First make sure if you have both bacula-server and bacula-client installed
>> on the same machine both are build with(out) ssl support.
>> Both ports install libs with the same name to the same place, but if the
>> client is build/installed first "with SSL support", and then the server
>> without SSL support you can see exact the described issue.
> A-ha. That must be it. I cannot recall why or when but this is what I
> must have done. Sorry for the noise.

No problem,

I was scratching my head about this and tried first to find the issue
in some of the build scripts until this scenario came in my mind.

But I will be happy if you can confirm this with a new build where
all bacula ports are build with SSL (the default with 5.0.3), since
it can be possible I have something overseen during the last update
of the port.


More information about the freebsd-ports mailing list