From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
To: linux-hams@vger.kernel.org
Subject: Re: Error compiling aprsd-2.2.6-4 from CVS
Date: Tue, 17 Apr 2007 19:36:57 +0200 [thread overview]
Message-ID: <462505B9.3020402@ccr.jussieu.fr> (raw)
In-Reply-To: <4624FB5F.1030508@ccr.jussieu.fr>
Bernard Pidoux wrote:
> Hi All,
>
> In aprsd directory captured from CVS sourceforge (aprsd-2.2.6-4)
> I changed boostrap.sh file permission to a+x and ran the script.
> It built configure script and then I was able to run ./configure and make.
> ...
I looked at configure.log file and found some error report that could be
interesting for aprsd developpers.
I will report here only the errors or warnings lines :
-----------------------
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by aprsd configure 2.2.6-4, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure
...
configure:2351: g++ -c -g -O2 conftest.cc >&5
conftest.cc: In function 'int main()':
conftest.cc:17: error: 'exit' was not declared in this scope
...
configure:3157: gcc -c -g -O2 conftest.c >&5
conftest.c:2: error: expected '=', ',', ';', 'asm' or '__attribute__'
before 'me'
...
configure:3642: gcc -E conftest.c
conftest.c:18:28: error: ac_nonexistent.h: No such file or directory
...
configure:3749: gcc -E conftest.c
conftest.c:18:28: error: ac_nonexistent.h: No such file or directory
...
configure:3947: gcc -o conftest -g -O2 conftest.c -lcrypt -lpthread >&5
conftest.c: In function 'main':
conftest.c:35: warning: incompatible implicit declaration of built-in
function 'exit'
...
configure:5613: gcc -c -g -O2 conftest.c >&5
conftest.c:85:19: error: vfork.h: No such file or directory
...
configure:5656: gcc -E conftest.c
conftest.c:51:19: error: vfork.h: No such file or directory
...
configure:5742: checking for fork
configure:5799: gcc -o conftest -g -O2 conftest.c -lcrypt -lpthread
-lax25 >&5
conftest.c:75: warning: conflicting types for built-in function 'fork'
73 de bernard, f6bvp
next prev parent reply other threads:[~2007-04-17 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 11:55 [NET] AX.25 Kconfig and docs updates and fixes Ralf Baechle
2007-03-24 19:54 ` David Miller
2007-04-17 14:28 ` Error compiling aprsd-2.2.5-15 Bernard Pidoux
2007-04-17 16:08 ` Curt, WE7U
2007-04-17 16:52 ` Error compiling aprsd-2.2.6-4 from CVS Bernard Pidoux
2007-04-17 17:25 ` Curt, WE7U
2007-04-17 17:36 ` Bernard Pidoux [this message]
2007-04-17 17:57 ` Curt, WE7U
2007-04-17 22:14 ` Hamish Moffatt
2007-04-17 22:13 ` Error compiling aprsd-2.2.5-15 Hamish Moffatt
2007-04-17 23:40 ` Jim Tittsler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462505B9.3020402@ccr.jussieu.fr \
--to=pidoux@ccr.jussieu.fr \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox