I found an implementation of these functions to Android, don't know if it apply to other platforms, may be useful. Seems to be using netlink:
Was going to spend a couple of hours this weekend trying to address this issue...
Need to know: which version of Solaris in the reference for building Poco?
Open Solaris 11, out-of-the-box (with no updates)
Oracle Solaris 11 (which I don't have budget to license... but would be respectful if someone had a machine with it installed that I could test on)
Illumos (which seems to have diverged significantly from both of the above)
On 9/18/12 12:50 PM, Alex Fabijanic wrote:
> I agree, we'll have to go ioctl SIOCGIFCONF route to support all platforms. Won't happen in 1.5 though
> Aleksandar Fabijanic
> Sent from my iPhone
> On Sep 18, 2012, at 14:41, Rangel Reale <firstname.lastname@example.org <mailto:email@example.com>> wrote:
>> Yes, I'm activelly testing trunk on Android, I can port to Android if possible.
>> According to this topic:
>> " The two usual ways of doing this on any Linux kernel is via
>> SIOCGIFCONF ioctl calls or netlink. "
>> It may be the same as the SIOCGLIF you were talking about.
>> On Tue, Sep 18, 2012 at 3:32 PM, Philip Prindeville <firstname.lastname@example.org <mailto:email@example.com>> wrote:
>> Odd, because Android is Linux and uses glibc.
>> If I provide a mock-up of getifaddrs() for Solaris, can you port it to Android?
>> On 9/18/12 11:38 AM, Rangel Reale wrote:
>> > Android also doesn't have <ifaddrs.h>, I had to comment all instances that use it so it would compile.
>> > On Tue, Sep 18, 2012 at 2:09 PM, Philip Prindeville <firstname.lastname@example.org <mailto:email@example.com> <mailto:firstname.lastname@example.org <mailto:email@example.com>>> wrote:Got visibility?
>> > What platforms are out there anyway that don't support getifaddrs() correctly (i.e. that don't include interfaces that are present but not configured)?
>> > We might have to provide a replacement version of getifaddrs() to do the right thing.
>> > I was poking around doing such a thing for Open Solaris 11 yesterday, and I noticed that (a) it didn't agree with the man pages, (2) the old BSD-standard ioctl's were partially broken and only the new "long-style" ioctl's (SIOCGLIF*) seemed to work, and (c) a lot of this damage has been around for a while as a known issue.
>> > Since Oracle isn't sharing source and isn't fixing well-known bugs, that means that the support burden for Solaris is going to be substantially higher than other platforms.
>> > -Philip
>> > On 9/17/12 9:06 PM, Philip Prindeville wrote:
>> > > That's a relief, because Oracle stop sharing source and it's not clear they're anxious to fix this any time soon.
>> > >
>> > > Alternatively, it might work if we use glibc-2 with Poco on Solaris... but there are still some ugly bugs in the Solaris kernel. I filed 3 defects today.
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
poco-develop mailing list