From: Cathryn Mataga <cathrynm@junglevision.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: IMPORTANT: LinuxNode v0.3.2
Date: Tue, 09 Sep 2003 05:49:22 -0700 [thread overview]
Message-ID: <3F5DCC52.7040505@junglevision.com> (raw)
In-Reply-To: <1061923547.1292.66.camel@oh2bns.ampr.org>
Tomi Manninen wrote:
> Hello all,
>
> I just uploaded a new version of LinuxNode to:
>
> http://hes.iki.fi/pub/ham/unix/linux/ax25/
>
> You'll find a source tar.gz, a source RPM and a binary RPM
> (compiled on RedHat 9).
>
> This version contains fixes for *SERIOUS* security flaws (read
> "remote root"). Upgrading all systems immediately is highly
> recommended!!!
>
> Thanks to Morgan, SM6TKY for pointing out the flaws and helping
> in fixing them!
>
I'm trying to compile 0.3.2 on Redhat 6.2. I get this error.
/usr/local/include/netax25/axlib.h:49: parse error before `null_ax25_address'
/usr/local/include/netax25/axlib.h:49: warning: data definition has no type or storage class
/usr/local/include/netax25/axlib.h:67: warning: `struct full_sockaddr_ax25' declared inside parameter list
/usr/local/include/netax25/axlib.h:67: warning: its scope is only this definition or declaration,
/usr/local/include/netax25/axlib.h:67: warning: which is probably not what you want.
/usr/local/include/netax25/axlib.h:74: warning: `struct full_sockaddr_ax25' declared inside parameter list
/usr/local/include/netax25/axlib.h:88: parse error before `*'
/usr/local/include/netax25/axlib.h:95: parse error before `*'
/usr/local/include/netax25/axlib.h:101: parse error before `*'
/usr/local/include/netax25/axlib.h:107: parse error before `*'
next prev parent reply other threads:[~2003-09-09 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 18:45 IMPORTANT: LinuxNode v0.3.2 Tomi Manninen
2003-09-02 17:11 ` Arno Verhoeven
2003-09-09 12:49 ` Cathryn Mataga [this message]
2003-09-09 14:25 ` M Taylor
2003-09-09 16:50 ` Tomi Manninen
2003-09-09 18:34 ` Cathryn Mataga
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=3F5DCC52.7040505@junglevision.com \
--to=cathrynm@junglevision.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.