15 Jan
2014
15 Jan
'14
12:32 a.m.
On 01/14/2014 05:22 PM, David C. Rankin wrote:
On 01/14/2014 05:06 PM, Calvin Morrison wrote:
Grr, found that problem - yes there really is a trailing space in the hal source
that kills the build. Fix with:
build() {
cd $srcdir
patch -Np1 -d ${srcdir} < hal.patch
cd "${srcdir}/${pkgname}-${pkgver}"
patch -Np1 -i "${srcdir}/hal-libudev-events.patch"
patch -Np1 -i "${srcdir}/hal-glib-2.3-compile-fix.patch"
patch -Np1 -i "${srcdir}/udev-update.patch"
patch -Np1 -i "${srcdir}/badvok-compile-fix.patch"
sed -i 's/failed; [\] /failed; \\/' policy/Makefile.am
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
But then another FTBS:
hald/solaris/probing/Makefile.am:15: but option 'subdir-objects' is disabled
hald/solaris/probing/Makefile.am:19: warning: source file '../../logger.c' is in
a subdirectory,
hald/solaris/probing/Makefile.am:19: but option 'subdir-objects' is disabled
partutil/Makefile.am:7: warning: source file '../hald/logger.c' is in a
subdirectory,
partutil/Makefile.am:7: but option 'subdir-objects' is disabled
==> ERROR: A failure occurred in build().
Aborting...
Where line 7 is:
libpartutil_la_SOURCES = partutil.h partutil.c ../hald/logger.c
So this looks like a true 'subdir-objects' is disabled failure regarding
logger.c. (why this one and not the 100 before?) dunno.. I'm going to try:
AM_INIT_AUTOMAKE([subdir-objects])
--
David C. Rankin, J.D.,P.E.
Those packages should be marked out of date. I
wouldn't trust them. I'm not sure
about specifics about the conflict
I am re-writing the PKGBUILD, so I'm going to figure it out. I think the only
dependencies that no longer exist are 'eject' and 'systemd-tools' and
those seem
to be provided now by 'util-linux' and 'systemd'. (god knows the source
hasn't
changed.....) I'll report back with success or failure.