Build issues on Ubuntu

[Felipe Gasper]

Hello,

I’m trying to build the latest 389 release on Ubuntu 20.04 using OS packages.

I think I’ve found a couple issues:

1) (trivial) The configure script doesn’t check for liblmdb’s existence.

2) (fatal) The build fails, thus:

-----
make[1]: Entering directory '/home/ubuntu/code/389-ds-base-389-ds-base-2.1.1'
/bin/bash ./libtool  --tag=CC   --mode=link gcc -g -O2       -lcrack          -o dbscan ldap/servers/slapd/tools/dbscan-dbscan.o -lplds4 -lplc4 -lnspr4 libback-ldbm.la
libtool: link: gcc -g -O2 -o .libs/dbscan ldap/servers/slapd/tools/dbscan-dbscan.o  -lcrack -lplds4 -lplc4 -lnspr4 ./.libs/libback-ldbm.so -Wl,-rpath -Wl,/opt/dirsrv/lib/dirsrv/plugins
/usr/bin/ld: ldap/servers/slapd/tools/dbscan-dbscan.o: undefined reference to symbol 'slapi_ch_realloc'
/usr/bin/ld: /home/ubuntu/code/389-ds-base-389-ds-base-2.1.1/.libs/libslapd.so.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
-----

slapi_ch_realloc() comes from 389 itself, so I would _think_ this to be an internal error, rather than a problem caused by system libraries?

Thank you in advance!

cheers,
-Felipe Gasper

[William Brown]

> On 7 May 2022, at 04:59, Felipe Gasper  wrote:
>
> Hello,
>
> I’m trying to build the latest 389 release on Ubuntu 20.04 using OS packages.
>
> I think I’ve found a couple issues:
> (trivial) The configure script doesn’t check for liblmdb’s existence.

I thought it did check?
> (fatal) The build fails, thus:

This appears to be a missing link to libslapd in the dbscan makefile.in :(
> make[1]: Entering directory '/home/ubuntu/code/389-ds-base-389-ds-base-2.1.1'
> /bin/bash ./libtool  --tag=CC   --mode=link gcc -g -O2       -lcrack          -o dbscan ldap/servers/slapd/tools/dbscan-dbscan.o -lplds4 -lplc4 -lnspr4 libback-ldbm.la
> libtool: link: gcc -g -O2 -o .libs/dbscan ldap/servers/slapd/tools/dbscan-dbscan.o  -lcrack -lplds4 -lplc4 -lnspr4 ./.libs/libback-ldbm.so -Wl,-rpath -Wl,/opt/dirsrv/lib/dirsrv/plugins
> /usr/bin/ld: ldap/servers/slapd/tools/dbscan-dbscan.o: undefined reference to symbol 'slapi_ch_realloc'
> /usr/bin/ld: /home/ubuntu/code/389-ds-base-389-ds-base-2.1.1/.libs/libslapd.so.0: error adding symbols: DSO missing from command line
> collect2: error: ld returned 1 exit status
>
> slapi_ch_realloc() comes from 389 itself, so I would _think_ this to be an internal error, rather than a problem caused by system libraries?
>
> Thank you in advance!
>
> cheers,
> -Felipe Gasper
> _______________________________________________
> 389-users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]....
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

--
Sincerely,

William Brown

Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia

[Felipe Gasper]

> On May 8, 2022, at 20:58, William Brown  wrote:
> > On 7 May 2022, at 04:59, Felipe Gasper  wrote:
> >
> > Hello,
> >
> > I’m trying to build the latest 389 release on Ubuntu 20.04 using OS packages.
> >
> > I think I’ve found a couple issues:
> > (trivial) The configure script doesn’t check for liblmdb’s existence.
>
> I thought it did check?

It’s actually neglecting the check for python3, too.

Reported: https://github.com/389ds/389-ds-base/issues/5287
> > (fatal) The build fails, thus:
>
> This appears to be a missing link to libslapd in the dbscan makefile.in :(

Thank you!

Reported with provisional fix (after your note here):

https://github.com/389ds/389-ds-base/issues/5288

-FG

[William Brown]

> On 9 May 2022, at 23:55, Felipe Gasper  wrote:
> > On May 8, 2022, at 20:58, William Brown  wrote:
> > > On 7 May 2022, at 04:59, Felipe Gasper  wrote:
> > >
> > > Hello,
> > >
> > > I’m trying to build the latest 389 release on Ubuntu 20.04 using OS packages.
> > >
> > > I think I’ve found a couple issues:
> > > (trivial) The configure script doesn’t check for liblmdb’s existence.
> >
> > I thought it did check?
>
> It’s actually neglecting the check for python3, too.
>
> Reported: https://github.com/389ds/389-ds-base/issues/5287
> > > (fatal) The build fails, thus:
> >
> > This appears to be a missing link to libslapd in the dbscan makefile.in :(
>
> Thank you!
>
> Reported with provisional fix (after your note here):
>
> https://github.com/389ds/389-ds-base/issues/5288

Thanks for reporting these!
> -FG
> _______________________________________________
> 389-users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]....
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

--
Sincerely,

William Brown

Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia