Re: Issues with version numbering and some ports
Trey Sizemore [EMAIL PROTECTED] writes: On Sun, 2004-12-05 at 11:44 -0500, Lowell Gilbert wrote: Trey Sizemore [EMAIL PROTECTED] writes: Let me rephrase this previously posted question with a more desriptive subject, I'm trying to get the CVS version of sylpheed-claws installed on this 5.3 box (so if you've done it successfully, I'd *love* your feedback). However, I'm getting a lot of errors: This is why we have the ports collection... Yes, but here is a case where the application I want, specifically sylpheed-claws-gtk2 is *not available* in ports. The ports should still provide some valuable clues; they're not magic, after all, just an encapsulation of the kind of experience with the program that you were hoping someone would post with. It's for a slightly earlier version, admittedly, but the mail/sylpheed-gtk2 port is pretty short and doesn't involve any unusual magic. The only thing that jumps out at me is that it calls out libtool 1.5... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Issues with version numbering and some ports
Trey Sizemore [EMAIL PROTECTED] writes: Let me rephrase this previously posted question with a more desriptive subject, I'm trying to get the CVS version of sylpheed-claws installed on this 5.3 box (so if you've done it successfully, I'd *love* your feedback). However, I'm getting a lot of errors: This is why we have the ports collection... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Issues with version numbering and some ports
On Sun, 2004-12-05 at 11:44 -0500, Lowell Gilbert wrote: Trey Sizemore [EMAIL PROTECTED] writes: Let me rephrase this previously posted question with a more desriptive subject, I'm trying to get the CVS version of sylpheed-claws installed on this 5.3 box (so if you've done it successfully, I'd *love* your feedback). However, I'm getting a lot of errors: This is why we have the ports collection... Yes, but here is a case where the application I want, specifically sylpheed-claws-gtk2 is *not available* in ports. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Issues with version numbering and some ports
Let me rephrase this previously posted question with a more desriptive subject, I'm trying to get the CVS version of sylpheed-claws installed on this 5.3 box (so if you've done it successfully, I'd *love* your feedback). However, I'm getting a lot of errors: $ ./autogen.sh --enable-gpgme --enable-aspell --enable-spamassassin-plugin --with-config-dir=.sylpheed-gtk2 --program-suffix=-gtk2 --enable-ldap /usr/X11R6/share/aclocal/rep.m4:7: warning: underquoted definition of AM_PATH_REP run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal /usr/X11R6/share/aclocal/imlib.m4:9: warning: underquoted definition of AM_PATH_IMLIB /usr/X11R6/share/aclocal/imlib.m4:167: warning: underquoted definition of AM_PATH_GDK_IMLIB /usr/X11R6/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK /usr/X11R6/share/aclocal/gdk-pixbuf.m4:12: warning: underquoted definition of AM_PATH_GDK_PIXBUF m4/imlib.m4:167: warning: underquoted definition of AM_PATH_GDK_IMLIB aclocal:configure.ac:243: warning: macro `AM_PATH_GLIB_2_0' not found in library configure.ac:88: warning: AC_CANONICAL_HOST invoked multiple times You should update your `aclocal.m4' by running aclocal. Putting files in AC_CONFIG_AUX_DIR, `config'. configure.ac:88: warning: AC_CANONICAL_HOST invoked multiple times configure.ac:88: warning: AC_CANONICAL_HOST invoked multiple times src/common/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined src/common/Makefile.am:1: src/common/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/common/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. src/gtk/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined src/gtk/Makefile.am:3: src/gtk/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/gtk/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/clamav/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined src/plugins/clamav/Makefile.am:3: src/plugins/clamav/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/clamav/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/demo/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined src/plugins/demo/Makefile.am:3: src/plugins/demo/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/demo/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/dillo_viewer/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined src/plugins/dillo_viewer/Makefile.am:3: src/plugins/dillo_viewer/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/dillo_viewer/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/image_viewer/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined src/plugins/image_viewer/Makefile.am:3: src/plugins/image_viewer/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/image_viewer/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/mathml_viewer/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined src/plugins/mathml_viewer/Makefile.am:3: src/plugins/mathml_viewer/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/mathml_viewer/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/pgpmime/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined src/plugins/pgpmime/Makefile.am:3: src/plugins/pgpmime/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/pgpmime/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/spamassassin/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined src/plugins/spamassassin/Makefile.am:3: src/plugins/spamassassin/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/spamassassin/Makefile.am:3: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/trayicon/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined src/plugins/trayicon/Makefile.am:5: src/plugins/trayicon/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/trayicon/Makefile.am:5: to `configure.ac' and run `aclocal' and `autoconf' again. src/plugins/trayicon/libeggtrayicon/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined src/plugins/trayicon/libeggtrayicon/Makefile.am:1: src/plugins/trayicon/libeggtrayicon/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/plugins/trayicon/libeggtrayicon/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. The sylpheed-claws mailing list remarked that the underquoted warnings can be ignored, but that the missing macros were a real problem.
