10:59 a.m.
The latest gisi changes break the build:
pep.c: In function ‘g_isi_pep_create’:
pep.c:80: error: ‘SOCK_NONBLOCK’ undeclared (first use in this function)
pep.c:80: error: (Each undeclared identifier is reported only once
pep.c:80: error: for each function it appears in.)
pep.c:80: error: ‘SOCK_CLOEXEC’ undeclared (first use in this function)
make[2]: *** [pep.lo] Error 1
make[1]: *** [all-recursive] Error 1
SOCK_NONBLOCK and SOCK_CLOEXEC are only available on kernel >= 2.6.28 & glibc
= 2.9. I know this is hardly bleeding edge, but oFono should continue
working with older systems. Perhaps a --disable-isi configure option is
_really_ in order?
Regards,
-Denis
4:55 p.m.
On Wed, 19 Aug 2009 19:59:37 -0500, Denis Kenzior <denkenz(a)gmail.com>
wrote:
The latest gisi changes break the build:
pep.c: In function ‘g_isi_pep_create’:
pep.c:80: error: ‘SOCK_NONBLOCK’ undeclared (first use in this
function)
pep.c:80: error: (Each undeclared identifier is reported only once
pep.c:80: error: for each function it appears in.)
pep.c:80: error: ‘SOCK_CLOEXEC’ undeclared (first use in this
function)
make[2]: *** [pep.lo] Error 1
make[1]: *** [all-recursive] Error 1
SOCK_NONBLOCK and SOCK_CLOEXEC are only available on kernel >= 2.6.28 &
glibc
kernel <= 2.6.27 do not support ISI...
--
Rémi Denis-Courmont
5:54 p.m.
On Wed, 19 Aug 2009 19:59:37 -0500, Denis Kenzior <denkenz(a)gmail.com>
wrote:
The latest gisi changes break the build:
pep.c: In function ‘g_isi_pep_create’:
pep.c:80: error: ‘SOCK_NONBLOCK’ undeclared (first use in this
function)
pep.c:80: error: (Each undeclared identifier is reported only once
pep.c:80: error: for each function it appears in.)
pep.c:80: error: ‘SOCK_CLOEXEC’ undeclared (first use in this
function)
make[2]: *** [pep.lo] Error 1
make[1]: *** [all-recursive] Error 1
SOCK_NONBLOCK and SOCK_CLOEXEC are only available on kernel >= 2.6.28 &
glibc >= 2.9.
Attached patch should fix it.
--
Rémi Denis-Courmont
6:26 p.m.
2009/8/20 Denis Kenzior <denkenz(a)gmail.com>:
SOCK_NONBLOCK and SOCK_CLOEXEC are only available on kernel >=
2.6.28 & glibc
>= 2.9. I know this is hardly bleeding edge, but oFono should continue
working with older systems. Perhaps a --disable-isi configure option is
_really_ in order?
I think I've seen enough of these issues. I agree this is not nice, so
I'll push a patch for a --disable-isi configure switch, along with
Rémi's patch that fixes the actual build issue.
But it seems the build is broken in git, but for a different reason:
atmodem/atmodem.c:40:35: error: ofono/message-waiting.h: No such file
or directory
atmodem/atmodem.c:42:23: error: ofono/sim.h: No such file or directory
atmodem/atmodem.c:43:23: error: ofono/sms.h: No such file or directory
atmodem/atmodem.c:46:29: error: ofono/voicecall.h: No such file or directory
atmodem/atmodem.c: In function ‘create_cb’:
atmodem/atmodem.c:381: warning: assignment makes pointer from integer
without a cast
Perhaps a --disable-at switch? I kid, I kid... ;-)
Cheers,
Aki
12:58 a.m.
Hi Aki,
But it seems the build is broken in git, but for a different reason:
atmodem/atmodem.c:40:35: error: ofono/message-waiting.h: No such file
or directory
atmodem/atmodem.c:42:23: error: ofono/sim.h: No such file or directory
atmodem/atmodem.c:43:23: error: ofono/sms.h: No such file or directory
atmodem/atmodem.c:46:29: error: ofono/voicecall.h: No such file or
I already complained about this to Marcel. Any time a header is added a make
clean is required. There were lots of new headers added.
directory atmodem/atmodem.c: In function ‘create_cb’:
atmodem/atmodem.c:381: warning: assignment makes pointer from integer
without a cast
This probably happens because the message-waiting header isn't found :)
Perhaps a --disable-at switch? I kid, I kid... ;-)
I've actually already said this should be the case :) If one is building for
a Nokia device, atmodem plugin is wasted space.
Regards,
-Denis
4777
days inactive
4777
days old
4 comments
3 participants
participants (3)
-
Aki Niemi -
Denis Kenzior -
Rémi Denis-Courmont