I tried to build 3.0.2 binary rpms with the following script, on CentOS 5.3
x86_64
#!/bin/bash
rpmbuild --rebuild \
--define "build_centos5 1" \
--define "build_x86_64 1" \
--define "build_mysql5 1" \
--define "build_python 1" \
--define "nobuild_gconsole 1" \
--define "contrib_packager Timo Neuvonen <t...@tee-en.net>" \
bacula-3.0.2-1.src.rpm
This ends up with the following:
RPM build errors:
InstallSourcePackage: Header V3 DSA signature: NOKEY, key ID b90d278f
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
user sbarn does not exist - using root
File not found: /var/tmp/bacula-root/etc/bacula/bacula-dir.conf
File not found: /var/tmp/bacula-root/etc/bacula/bacula-fd.conf
File not found: /var/tmp/bacula-root/usr/lib64/bacula/query.sql
File not found: /var/tmp/bacula-root/usr/sbin/bacula-dir
File not found: /var/tmp/bacula-root/usr/sbin/bacula-fd
File not found: /var/tmp/bacula-root/etc/bacula/bacula-fd.conf
File not found: /var/tmp/bacula-root/usr/sbin/bacula-fd
[t...@garfield rpm-build]$
The OS is up-to-date, and has been able to build previous versions
(including 3.0.1) of Bacula. On my another CentOS 5.3 system which is x86,
the build goes nicely, and the resulting binaries also seem to work. So,
maybe this is something x86_64 related?
Regards,
Timo
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
