On Thu, 2013-08-22 15:44:43 +0100, Laszlo Papp wrote:
On Thu, Aug 22, 2013 at 3:34 PM, Ludolf Holzheid < [email protected]> wrote:
On Thu, 2013-08-22 14:43:55 +0100, Laszlo Papp wrote:
Here you can find the log file in question for details:
[..]
In file included from /usr//include/features.h:324:0, from /usr//include/pthread.h:23, from common.h:158, from str.c:38:
/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/sysroots/foo/usr/include/bits/predefs.h:23:3:
error: #error "Never use <bits/predefs.h> directly; include
<stdc-predef.h>
Laszlo,
Are you sure /usr//include is the right include directory for cross- compiling? I must confess, I'm not familiar with cross-compiling, but this looks fishy.
Most certainly not, but other softwares get it right. I will assume that it has something to do with how the Makefile is generated for stunnel. Got a clue in that area?
I would try to remove -I/usr//include (and -pedantic) from the compiler flags, but again, I'm no expert in autoconf and cross-compiling.
Ludolf
On Thu, Aug 22, 2013 at 4:25 PM, Ludolf Holzheid < [email protected]> wrote:
On Thu, 2013-08-22 15:44:43 +0100, Laszlo Papp wrote:
On Thu, Aug 22, 2013 at 3:34 PM, Ludolf Holzheid < [email protected]> wrote:
On Thu, 2013-08-22 14:43:55 +0100, Laszlo Papp wrote:
Here you can find the log file in question for details:
[..]
In file included from /usr//include/features.h:324:0, from /usr//include/pthread.h:23, from common.h:158, from str.c:38:
/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/sysroots/foo/usr/include/bits/predefs.h:23:3:
error: #error "Never use <bits/predefs.h> directly; include
<stdc-predef.h>
Laszlo,
Are you sure /usr//include is the right include directory for cross- compiling? I must confess, I'm not familiar with cross-compiling, but this looks fishy.
Most certainly not, but other softwares get it right. I will assume that
it
has something to do with how the Makefile is generated for stunnel. Got a clue in that area?
I would try to remove -I/usr//include (and -pedantic) from the compiler flags, but again, I'm no expert in autoconf and cross-compiling.
I would not know how to do that inside the stunnel codebase. The problem is not outside because every other software works. The buildsystem is probably hard coding something without the opportunity for downstream to override it. Has stunnel ever been compiled for embedded and ARM with cross-compilation?
Hmm, --with-ssl seems to have helped. It is strange one has to explicitly specify the cross compilation include stuff. Perhaps, it is a room for improvement?
On Thu, Aug 22, 2013 at 4:28 PM, Laszlo Papp [email protected] wrote:
On Thu, Aug 22, 2013 at 4:25 PM, Ludolf Holzheid < [email protected]> wrote:
On Thu, 2013-08-22 15:44:43 +0100, Laszlo Papp wrote:
On Thu, Aug 22, 2013 at 3:34 PM, Ludolf Holzheid < [email protected]> wrote:
On Thu, 2013-08-22 14:43:55 +0100, Laszlo Papp wrote:
Here you can find the log file in question for details:
[..]
In file included from /usr//include/features.h:324:0, from /usr//include/pthread.h:23, from common.h:158, from str.c:38:
/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/sysroots/foo/usr/include/bits/predefs.h:23:3:
error: #error "Never use <bits/predefs.h> directly; include
<stdc-predef.h>
Laszlo,
Are you sure /usr//include is the right include directory for cross- compiling? I must confess, I'm not familiar with cross-compiling, but this looks fishy.
Most certainly not, but other softwares get it right. I will assume
that it
has something to do with how the Makefile is generated for stunnel. Got
a
clue in that area?
I would try to remove -I/usr//include (and -pedantic) from the compiler flags, but again, I'm no expert in autoconf and cross-compiling.
I would not know how to do that inside the stunnel codebase. The problem is not outside because every other software works. The buildsystem is probably hard coding something without the opportunity for downstream to override it. Has stunnel ever been compiled for embedded and ARM with cross-compilation?
On 08/22/2013 07:11 PM, Laszlo Papp wrote:
Hmm, --with-ssl seems to have helped. It is strange one has to explicitly specify the cross compilation include stuff. Perhaps, it is a room for improvement?
Perhaps it is. I will appreciate more specific suggestions.
The way I use cross-compilation is: ./configure --build=i686-pc-linux-gnu --host=arm-linux-androideabi --prefix=/data/local --with-ssl=/opt/androideabi/sysroot
Mike
-
Laszlo Papp -
Ludolf Holzheid -
Michal Trojnara