Menu

#13 configure does not work on Mailsync 5.1.0

None
wont-fix
nobody
None
5
2020-11-10
2004-02-02
Anonymous
No

The configure script fails to find installed libraries:

checking for libssl... not found
checking for krb5-config... not found
checking for pam library... not found
checking for c-client.h... not found
configure: error: a working c-client installation is
required for building mailsync

libssl is installed on my system in the following places:
/usr/lib/libssl.a
/usr/lib/libssl.so
/usr/local/lib/libssl.a
/usr/local/lib/libssl.so

libpam is installed on my system in the following places:
/usr/lib/libpam.a
/usr/lib/libpam.so

c-client.h is installed on my system in the following
places:
/usr/local/include/c-client/c-client.h

I have tried using the command line parameters as
follows:
./configure --with-openssl=/usr/lib --with-c-
client=/usr/local/include/c-client

and still recieve the same error.

I am running csh, not bash. If I run in sh I get the same
result.

If I edit the configure script and insert an "echo ${p}"
at line 5056 then I get the following result using the
above command line:

checking for libssl... not found
checking for krb5-config... not found
checking for pam library... not found
checking for c-client.h... {/usr/local/include/c-
client,/usr,/usr/local}{,/c-client,/lib/c-client,/include/c-
client,/include,/include/imap}
not found
configure: error: a working c-client installation is
required for building mailsync

Instead of processing each directory seperately, the
script is trying to locate the c-client.h file in this
strange glob. This leads me to think that the "for"
statement at line 5055 is not written correctly.

Discussion

  • Tomas Pospisek

    Tomas Pospisek - 2004-02-02

    Logged In: YES
    user_id=15179

    Could you verify, that this fails with the version from CVS too?
    *t

     
  • Nobody/Anonymous

    Logged In: NO

    I downloaded the CVS archive for Mailsync.

    There is no configure file, only the configure.ac and
    autogen.sh files.

    I installed automake and autoconf on my system, then ran
    autogen.sh. The configure file was not made.

    I then ran:
    autoconf configure.ac > configure
    chmod o+x configure
    ./configure

    configure did not find the above libraries.

    I then modified line 4768 and added the echo ${p} statement
    similar to above. This is the result:

    checking for libssl... not found
    checking for krb5-config... not found
    checking for pam library... not found
    checking for c-client.h... {/usr/local/include/c-
    client,/usr,/usr/local}{,/c-client,/lib/c-client,/include/c-
    client,/include,/include/imap}
    not found
    configure: error: a working c-client installation is required for
    building mailsync

     
  • Nobody/Anonymous

    Logged In: NO

    Installed BASH and ran configure from Mailsync 5.1.0 release.
    Configure ran perfectly and detected all libraries.

    Recommend changing README/INSTALL documents to note
    that configure is known to run from BASH, and that it may
    not be sufficient to run from sh/csh on FreeBSD 4.9, for
    example.

     
  • Tomas Pospisek

    Tomas Pospisek - 2004-09-20

    Logged In: YES
    user_id=15179

    Following what I read on the net, /bin/sh *must* be linked
    to a posix compliant shell [1]. AFAICS the following:

    BLA=sometext

    is a POSIX compliant statement [2]. However on my machine,
    csh doesn't understand that:

    $ csh
    executing .alias
    Badly placed ()'s.
    tpo2:~> BLA=sometext
    BLA=sometext: Command not found.

    I concurr that csh is not POSIX compliant, and you should
    fix your system and point /bin/sh to ksh or bash or something.

    Or am I wrong?
    *t

    [1] http://www.calpoly.edu/cgi-bin/man-cgi?sh+1
    [2]
    http://www.informatik.uni-frankfurt.de/doc/man/hpux/sh-posix.1.html

     
  • Tomas Pospisek

    Tomas Pospisek - 2020-11-10
    • status: open --> wont-fix
    • Group: -->
     
  • Tomas Pospisek

    Tomas Pospisek - 2020-11-10

    I'm closing this ticket, because:

    • since filing this ticket there have been multiple mailsync releases since, that maybe fix the autotools stuff
    • autotools have evolved as well

    all these arguments above are maybe nonsense because the main problem seems to be that:

    • csh did not seem to be compatible with autotools at the time

    So I won't be fix this: building mailsync with csh is currently not supported and I am not planing to work on csh support

     

Log in to post a comment.