AW: Apache 2.0.50 port is busted

From: Alexander Liebau (beisser_at_lefti.net)
Date: 07/30/04

  • Next message: David Rio Deiros: "Re: correct way to upgrade ssh"
    To: "Jeffrey Wheat" <jeff@cetlink.net>, <freebsd-questions@freebsd.org>
    Date: Fri, 30 Jul 2004 23:45:55 +0200
    
    

    i had the same problem, asked the same questions and noone was able to help
    :/

    -----Ursprungliche Nachricht-----
    Von: owner-freebsd-questions@freebsd.org
    [mailto:owner-freebsd-questions@freebsd.org]Im Auftrag von Jeffrey Wheat
    Gesendet: Freitag, 30. Juli 2004 23:31
    An: freebsd-questions@freebsd.org
    Betreff: Apache 2.0.50 port is busted

    Has anyone else attempted to build the apache-2.0.50 port
    from cvs'd port tree a couple hours ago? I am trying to
    build this on a 5.2.1 (i386) box and it looks like the
    libtool bug is as present as ever:

    grep: /usr/local/libexec/apache2/mod_dir.la: No such file or directory
    grep: /usr/local/libexec/apache2/mod_dir.la: No such file or directory
    Warning! dlname not found in /usr/local/libexec/apache2/mod_dir.la.
    Assuming installing a .so rather than a libtool archive.
    /usr/ports/www/apache2/work/httpd-2.0.50/srclib/apr/libtool --silent
    --mode=install cp mod_imap.la /usr/local/libexec/apache2/
    grep: /usr/local/libexec/apache2/mod_imap.la: No such file or directory
    grep: /usr/local/libexec/apache2/mod_imap.la: No such file or directory
    Warning! dlname not found in /usr/local/libexec/apache2/mod_imap.la.
    Assuming installing a .so rather than a libtool archive.
    /usr/ports/www/apache2/work/httpd-2.0.50/srclib/apr/libtool --silent
    --mode=install cp mod_actions.la /usr/local/libexec/apache2/
    grep: /usr/local/libexec/apache2/mod_actions.la: No such file or
    directory
    grep: /usr/local/libexec/apache2/mod_actions.la: No such file or
    directory
    Warning! dlname not found in /usr/local/libexec/apache2/mod_actions.la.
    Assuming installing a .so rather than a libtool archive.

    This happens for every module during the build. This server is a fresh
    install (today). I tried this yesterday with a fresh install and had
    the same results. The 2.0.48 port will build and install correctly
    though.

    If anyone knows why this is happening, I would appreciate an email as I
    had to unsubscribe from the lists due to too much other email already.

    Thanks!
    Jeffrey
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: David Rio Deiros: "Re: correct way to upgrade ssh"