[ZBX-10419] Zabbix 2.4.7 Ubuntu build files calls build options twice for db packages Created: 2016 Feb 19  Updated: 2017 May 30  Resolved: 2016 Feb 22

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Installation (I)
Affects Version/s: 2.4.7
Fix Version/s: 2.0.17rc1, 2.2.12rc1, 2.4.8rc1

Type: Incident report Priority: Trivial
Reporter: Dmitry Verkhoturov Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Hello, guys.

I've got your Debian packaging instructions from following url:
http://repo.zabbix.com/zabbix/2.4/ubuntu/pool/main/z/zabbix/zabbix_2.4.7-1+trusty.debian.tar.gz
In it I found duplication of commands passed to build:

CONFFLAGS_COMMON  = --host=$(DEB_HOST_GNU_TYPE) \
                    --build=$(DEB_BUILD_GNU_TYPE) \
                    --prefix=/usr \
                    --mandir=\$${prefix}/share/man \
                    --infodir=\$${prefix}/share/info \
                    --sysconfdir=/etc/zabbix \
                    --enable-server \
                    --enable-agent \
                    --enable-proxy \
                    --enable-java \
                    --with-jabber \
                    --with-ldap \
                    --enable-ipv6 \
                    --with-net-snmp \
                    --with-openipmi \
                    --with-ssh2 \
                    --with-libcurl \
                    --with-unixodbc \
                    --with-libxml2

<...>
CONFFLAGS_SERVER_MYSQL = $(CONFFLAGS_COMMON) --with-mysql
CONFFLAGS_SERVER_PGSQL = $(CONFFLAGS_COMMON) --with-postgresql
CONFFLAGS_SERVER_SQLITE3 = $(CONFFLAGS_COMMON) --with-sqlite3
<...>
	cd $(BUILDDIR)-$(*) && ./configure $(CONFFLAGS_COMMON) $(CONFFLAGS_SERVER_$(*))

Should be:

	cd $(BUILDDIR)-$(*) && ./configure $(CONFFLAGS_SERVER_$(*))

Otherwise (now) it adds same parameters twice. It's trivial but still worth to fix it I think.



 Comments   
Comment by Kodai Terashima [ 2016 Feb 22 ]

Thanks for the pointed out. Fixed it on 2.0.17rc1, 2.2.12rc1 and 2.4.8rc1.

Generated at Mon Apr 07 11:34:26 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.