Tim, Darrell,
I have also run into an avahi-tqt build failure. Again, nothing has changed on my end. However, when attempting to build avahi-tqt, it fails. I have included the context leading to the failure, because I'm not entirely sure what crashed. It looks like it is complaining about a sed option. What does it look like to you?
config.status: executing libtool commands
---{ avahi 0.6.30 }---
prefix: /opt/trinity sysconfdir: /etc localstatedir: /var avahi socket: /var/run/avahi-daemon/socket dbus-1 system.d dir: /etc/dbus-1/system.d dbus-1 version: 1.4.20 dbus-1 system socket: unix:path=/var/run/dbus/system_bus_socket C Compiler: gcc -std=gnu99 CFLAGS: -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fstack-protector -std=c99 -Wall -W -Wextra -pedantic -pipe -Wformat -Wold-style-definition -Wdeclaration-after-statement -Wfloat-equal -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wshadow -Wendif-labels -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wwrite-strings -fdiagnostics-show-option -Wno-cast-qual -fno-strict-aliasing Enable GLIB: yes Enable GLIB GObject: yes Enable GObject Introspection: no Enable GTK 2.0: Enable GTK 3.0: Enable D-Bus: yes With XML: expat Enable GDBM: Enable DBM: Enable Python: Enable pygtk: Enable python-dbus: Enable QT3: yes Enable QT4: Enable Mono: Enable Monodoc: Distribution/OS: archlinux User for avahi-daemon: avahi Group for avahi-daemon: avahi Priviliged access group for Avahi clients: netdev User for avahi-autoipd: avahi-autoipd Group for avahi-autoipd: avahi-autoipd Enable chroot(): yes Enable Linux inotify: yes Enable stack-smashing protection: yes systemd unit directory:
Building libavahi-tqt: yes
+ make clean Making clean in avahi-tqt make[1]: Entering directory `/build/src/avahi-tqt/avahi-tqt' test -z "qt-watch.moc3" || rm -f qt-watch.moc3 test -z "libavahi-tqt.la" || rm -f libavahi-tqt.la rm -f ./so_locations rm -rf .libs _libs rm -f *.o rm -f *.lo make[1]: Leaving directory `/build/src/avahi-tqt/avahi-tqt' Making clean in . make[1]: Entering directory `/build/src/avahi-tqt' test -z "avahi-tqt.pc" || rm -f avahi-tqt.pc rm -rf .libs _libs rm -f *.lo make[1]: Leaving directory `/build/src/avahi-tqt' ==> Building - tde-avahi-tqt... make all-recursive make[1]: Entering directory `/build/src/avahi-tqt' Making all in avahi-tqt make[2]: Entering directory `/build/src/avahi-tqt/avahi-tqt' GEN qt-watch.moc3 cp: invalid option -- 'o' Try 'cp --help' for more information. sed: invalid option -- 'o' Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...
-n, --quiet, --silent suppress automatic printing of pattern space -e script, --expression=script add the script to the commands to be executed
Tim, Darrell,
I have also run into an avahi-tqt build failure. Again, nothing has changed on my end. However, when attempting to build avahi-tqt, it fails. I have included the context leading to the failure, because I'm not entirely sure what crashed. It looks like it is complaining about a sed option. What does it look like to you?
The source tree is currently in a state of flux while I attempt to resolve a couple of long-standing, but fundamental, bugs. I'd recommend waiting a week or so while I run through build tests and fix the resultant failures.
Tim
On 06/19/2012 05:02 PM, Timothy Pearson wrote:
The source tree is currently in a state of flux while I attempt to resolve a couple of long-standing, but fundamental, bugs. I'd recommend waiting a week or so while I run through build tests and fix the resultant failures.
Tim
Hmm,
Thanks Tim! That's what I needed to know. I rob Peter to pay Paul to get a new chroot setup to build with gcc 4.7.1 and --- I get to wait :)
Is there any reason this would impact the kwrite/infinite loop/crash testing? I'm currently building tdelibs and I was looking to build tdebase tonight to test. Any reason not to proceed with that?
I have also run into an avahi-tqt build failure. Again, nothing has changed on my end. However, when attempting to build avahi-tqt, it fails. I have included the context leading to the failure, because I'm not entirely sure what crashed. It looks like it is complaining about a sed option. What does it look like to you?
moc has been renamed to tqmoc. :-) Proposed patch (works for me!):
diff -urN avahi-tqt/avahi-tqt/Makefile.am avahi-tqt.new/avahi-tqt/Makefile.am --- avahi-tqt/avahi-tqt/Makefile.am 2012-05-27 17:57:48.000000000 -0500 +++ avahi-tqt.new/avahi-tqt/Makefile.am 2012-06-19 21:04:00.000000000 -0500 @@ -34,7 +34,7 @@ qt-watch.cpp
qt-watch.moc3: qt-watch.cpp - $(AM_V_GEN)$(MOC_QT3) moc $^ $@ + $(AM_V_GEN)$(MOC_QT3) tqmoc $^ $@
libavahi_tqt_la_CPPFLAGS = $(AM_CFLAGS) $(QT3_CFLAGS) $(VISIBILITY_HIDDEN_CFLAGS) libavahi_tqt_la_LIBADD = $(AM_LDADD) $(QT3_LIBS)
Darrell
I have also run into an avahi-tqt build failure. Again, nothing has changed on my end. However, when attempting to build avahi-tqt, it fails. I have included the context leading to the failure, because I'm not entirely sure what crashed. It looks like it is complaining about a sed option. What does it look like to you?
moc has been renamed to tqmoc. :-) Proposed patch (works for me!):
diff -urN avahi-tqt/avahi-tqt/Makefile.am avahi-tqt.new/avahi-tqt/Makefile.am --- avahi-tqt/avahi-tqt/Makefile.am 2012-05-27 17:57:48.000000000 -0500 +++ avahi-tqt.new/avahi-tqt/Makefile.am 2012-06-19 21:04:00.000000000 -0500 @@ -34,7 +34,7 @@ qt-watch.cpp
qt-watch.moc3: qt-watch.cpp
- $(AM_V_GEN)$(MOC_QT3) moc $^ $@
- $(AM_V_GEN)$(MOC_QT3) tqmoc $^ $@
libavahi_tqt_la_CPPFLAGS = $(AM_CFLAGS) $(QT3_CFLAGS) $(VISIBILITY_HIDDEN_CFLAGS) libavahi_tqt_la_LIBADD = $(AM_LDADD) $(QT3_LIBS)
Darrell
Looks good to me! Still compiling base libraries here (tqt3/tqtinterface) so have not had a chance to test anything else.
Tim
Looks good to me! Still compiling base libraries here (tqt3/tqtinterface) so have not had a chance to test anything else.
I'll push to GIT. Refer to my next message for tqca/tqca-tls patches. :-)
Darrell