From: JoseAlberto <bass@gentoo.org>
To: gnap-dev@lists.gentoo.org
Subject: Re: [gnap-dev] Update GNAP core files
Date: Fri, 23 Oct 2009 11:01:04 +0200 [thread overview]
Message-ID: <1256288464.15953.1.camel@supercoco> (raw)
In-Reply-To: <200910221915.34367.jaervosz@gentoo.org>
happy to hears good news :)
sadly i dont have time with real-life work for gnap (i'm still using
old-good gnap), so any update will be great welcome
El jue, 22-10-2009 a las 19:15 +0200, Sune Kloppenborg Jeppesen
escribió:
> To anyone still on this list,
>
> I've updated GNAP to build again with GCC 4.4.1 from the hardened overlay.
> It's still uclibc based and not much else changed. For more detail please see:
>
> http://dev.gentoo.org/~jaervosz/gnap/mainpage.html
>
> It's been running stable on my router Soekris box for a few days now without
> any problems.
>
next prev parent reply other threads:[~2009-10-23 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 17:15 [gnap-dev] Update GNAP core files Sune Kloppenborg Jeppesen
2009-10-22 17:43 ` Vít Vomáčko
2009-10-23 9:01 ` JoseAlberto [this message]
2009-10-23 17:47 ` Sune Kloppenborg Jeppesen
2009-10-26 9:54 ` JoseAlberto
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=1256288464.15953.1.camel@supercoco \
--to=bass@gentoo.org \
--cc=gnap-dev@lists.gentoo.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