enterprise-support team mailing list archive

[Rafael David Tinoco <1890790@xxxxxxxxxxxxxxxxxx>]

Alright, you can fix it by doing:

edit src/ssl/certificate_db.h and change

#define Here __FILE__, __LINE__

to

#ifndef Here
#define Here __FILE__, __LINE__
#endif

and that will fix your issue.

But, please, do notice that this bug is unsupported by Ubuntu and this
bug is indeed invalid.

"no modification" is "not changing package configure options" and that
is why we didn't catch this issue after the security fixes were applied:
because we don't build with those options (including crypto) so we never
faced a FTBFS after applying the patches.

I can't move on with a "SRU" (Stable Release Update) for a FTBFS in a
configure option we don't use to generate our binary packages, I hope
you understand. Just wanted to clarify this for further needs. Best
place to discuss those issues could be Ubuntu User mailing list, or even
to query someone at Ubuntu Devel mailing list.

For the record, after the fix:

$ ldd ./debian/squid/usr/sbin/squid3 | grep ssl
	libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f5b37dd0000)

Have a good one ;)

** Changed in: squid3 (Ubuntu)
       Status: New => Invalid

** Changed in: squid3 (Ubuntu Xenial)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to squid3 in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1890790

Title:
  Build Failure with --enable-ssl-crtd flag

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1890790/+subscriptions