Re: libasr
On Sun, Oct 11, 2015 at 07:39:26PM +, G B wrote:
> I'm again attempting to build OpenSMTPD on the latest OpenIndiana release
> since
> it has a newer toolchain. I've downloaded the newest libasr from June, 2015
> and configure and make completed without any errors. However, during "gmake
> install" it stopped with:
>
> libtool: install: chmod 644 /usr/local/lib/libaasr.a
> libtool: install: ranlib /usr/local/lib/libasr.a
> gmake install-exec-hook
> gmake[3]: Entering directory `/tmp/libasr-1.0.2/src'
> manpage=`echo asr_run.3.out | sed 's/\.out$//'`; \
> if test "man" = "man"; then
> /usr/bin/cat ${manpage} | nawk -f ../mk/mdoc2man.awk >
> asr_run.3.out;
> \
> else \
> /usr/bin/cat ${manpage} > asr_run.3.out; \
> fi
> nawk: you can only delete array[element] at source line 110 in function
> splitwor
> ds
> context is
>delete dest >>>
> <<< while (length(l) > 0) {
> nawk: syntax error at source line 110 in function splitwords
> nawk: illegal statement at source line 110 in function splitwords
> missing )
> gmake[3]: *** [asr_run.3.out] Error 2
> gmake[3]: Leaving directory `/tmp/libasr-1.0.2/src'
> gmake[2]: *** [install-exec-am] Error 2
> gmake[2]: Leaving directory `/tmp/libasr-1.0.2/src'
> gmake[1]: *** [install-am] Error 2
> gmake[1]: Leaving directory `/tmp/libasr-1.0.2/src'
> gmake: *** [install-recursive] Error 1
Try a different implementation of AWK (e.g. GNU awk):
% gmake clean
% AWK=/path/to/bin/gawk ./configure ...
% gmake
# gmake install
--
Herbert
--
You received this mail because you are subscribed to misc@opensmtpd.org
To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
Re: libasr missing on Ubuntu 15.04
Hi, i made a ubuntu ppa for opensmtpd https://launchpad.net/~segler-alex/+archive/ubuntu/opensmtpd have packages only for 14.04 at the moment, but would be no problem for me to do it for 15.04 too. greetings alex Am 2015-07-20 03:41, schrieb Alan Cheng: Hello, I'm trying to compile latest opensmptd (portable) on my ubuntu 15.04 machine, but I got the libasr missing error while runing ./configure or ./configure --with-asr=/usr/local. I've compiled and installed libasr using the source from github. any pointers? Here is the log during ./configure: .. checking for inet_net_pton in -lresolv... yes checking if programs using libevent functions will link... no checking for asr.h... yes checking for asr_resolver in -lasr... no configure: error: *** libasr missing - please install first or check config.log *** I can see libasr is installed on my machine: root@cactus:~/opensmtpd# ls -l /usr/local/lib total 712 -rw-r--r-- 1 root root 463398 Jul 20 00:25 libasr.a -rw-r--r-- 1 root root 919 Jul 20 00:25 libasr.la lrwxrwxrwx 1 root root 15 Jul 20 00:25 libasr.so - libasr.so.0.0.2 lrwxrwxrwx 1 root root 15 Jul 20 00:25 libasr.so.0 - libasr.so.0.0.2 -rw-r--r-- 1 root root 240848 Jul 20 00:25 libasr.so.0.0.2 -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
Re: libasr: LICENSE, LICENCE
I'm for the American one (license). This naming is pretty common nowadays. On Dec 28, 2014 8:29 AM, Jason Barbier jab...@serversave.us wrote: Agreed we probably should standardize on a dialect otherwise we may be in for some confusion on how to standardise naming in the future. This rift between EN_GB and EN_US was one that always irritated me. On 12/27/2014 03:56 PM, Hugo Osvaldo Barrera wrote: On 2014-12-28 05:01, Denis Fateyev wrote: In English both versions are possible. But 'license' indeed sounds better, IMO. I'm just pointing out that different tarballs are inconsistent, which is a bit odd. I was unaware that both spellings were correct though. On Dec 28, 2014 4:10 AM, Hugo Osvaldo Barrera h...@barrera.io h...@barrera.io wrote: The snapshot tarball contains LICENSE. The 1.0.0 release contains LICENCE. It looks like only the release is misspelt, and that former snapshots were right as well. Cheers, -- Hugo Osvaldo Barrera A: Because we read from top to bottom, left to right. Q: Why should I start my reply below the quoted text?
Re: libasr: LICENSE, LICENCE
As a 'Murrican I am all for EN_US On 12/27/2014 07:16 PM, Denis Fateyev wrote: I'm for the American one (license). This naming is pretty common nowadays. On Dec 28, 2014 8:29 AM, Jason Barbier jab...@serversave.us mailto:jab...@serversave.us wrote: Agreed we probably should standardize on a dialect otherwise we may be in for some confusion on how to standardise naming in the future. This rift between EN_GB and EN_US was one that always irritated me. On 12/27/2014 03:56 PM, Hugo Osvaldo Barrera wrote: On 2014-12-28 05:01, Denis Fateyev wrote: In English both versions are possible. But 'license' indeed sounds better, IMO. I'm just pointing out that different tarballs are inconsistent, which is a bit odd. I was unaware that both spellings were correct though. On Dec 28, 2014 4:10 AM, Hugo Osvaldo Barrerah...@barrera.io mailto:h...@barrera.io wrote: The snapshot tarball contains LICENSE. The 1.0.0 release contains LICENCE. It looks like only the release is misspelt, and that former snapshots were right as well. Cheers, -- Hugo Osvaldo Barrera A: Because we read from top to bottom, left to right. Q: Why should I start my reply below the quoted text?
Re: libasr on linux
On 2014-07-15 09:55, Gilles Chehade wrote: On Mon, Jul 14, 2014 at 01:30:55AM -0300, Hugo Osvaldo Barrera wrote: I'm now using the latest smtpd from git with libasr on ArchLinux, and it works find (I maintain unstable packages for both). I'm not using this on my server though, just my laptop for outgoing mail. I'm wreckless, but not that much! ;) Anyway, I though you might care to know it all works on this very bleeding edge distro. Cheers Nice, Out of curiosity, are you the new Arch Linux maintainer ? No, I maintain (and have since before you went stable) the -snapshot and the -git packages at the Arch User Repositories (based on snapshots and the latest git checkout respectively). The stable package is maintained in the official repos by someone else. -- Gilles Chehade https://www.poolp.org @poolpOrg -- Hugo Osvaldo Barrera A: Because we read from top to bottom, left to right. Q: Why should I start my reply below the quoted text? pgp3SfE1iQ9jO.pgp Description: PGP signature
