Menu
▾
▴
firebird-devel
|
From: marius a. p. <ma...@gm...> - 2012-07-19 09:58:16
|
On Thu, Jul 19, 2012 at 12:31 PM, Damyan Ivanov <dm...@de...> wrote: > -=| J-L M, 19.07.2012 10:57:53 +0200 |=- > > We are trying to compile Firebird 2.1 > > for Android in order to use the embedded version in our mobile device > > of our software. > > But > > for the moment it seems impossible for some reasons : Android > > uses his own Libc called Bionic. And the problem is that there is a > > lot of missing features in. There is no implementation of the POSIX > > IPC or System V IPC inside, Android drop this to avoid > > denial-of-service. So, use of > > semaphore, shared memory, etc, is not possible. > > Perhaps you can try 2.5? It no longer uses semaphores. > > Not sure about the availability of pthread mutexes in bionic, though. > The NDK appears to have support for pthread mutexes<http://www.xgc.com/manuals/xgclib/x5257.html> http://stackoverflow.com/questions/11048260/does-android-support-pthread |
|
From: Alex P. <pes...@ma...> - 2012-07-19 09:59:28
|
On 07/19/12 13:31, Damyan Ivanov wrote: > Not sure about the availability of pthread mutexes in bionic, though. Shared mutexes are not present. |
|
From: Alex P. <pes...@ma...> - 2012-07-19 09:58:56
|
On 07/19/12 12:57, J-L M wrote: > Hello, > We are trying to compile Firebird 2.1 > for Android in order to use the embedded version in our mobile device > of our software. > But > for the moment it seems impossible for some reasons : Android > uses his own Libc called Bionic. And the problem is that there is a > lot of missing features in. There is no implementation of the POSIX > IPC or System V IPC inside, Android drop this to avoid > denial-of-service. NO - they just _say_ that Posix IPC was dropped to avoid DOS, actually Bionic is FreeBSD-based, and they never supported Posix IPC. > So, use of > semaphore, shared memory, etc, is not possible. Unfortunately yes. > We > have written a more complet document of this porterage which > describes the problems in detail. > Not needed - it's obvious :) > > Somebody > have already attempt to compile or to make an Android version of > Firebird ? Yes. We can now build client library for Android. > What > would be the good way to do that ? First of all - do not use old 2.1 version. Good idea is doing development in trunk, may be later backport to 2.5. In my future plans for Android port is to have our IPC implemented using Android binder. > Otherwise, > how to interest Firebird developpers to make this Android version ? Probably http://www.firebirdsql.org/en/how-to-become-a-sponsor/ > (Maybe I can create a topic in the tracker ) It exists http://tracker.firebirdsql.org/browse/CORE-3885 And tracker is bad place for discussing ports. |
|
From: JLM <so4...@ho...> - 2012-07-20 12:40:13
|
Hello, Thanks all for your answers. I didn't know that it was possible to build client library for Android. It's for ARM ? How do buil that ? Cross-compilation of Firebird runs with difficulty. Do you use a classic gcc cross-compiler of do you use the NDK toolset ? Regards, Jean-Louis Meuriot On 19/07/2012 11:58, Alex Peshkoff wrote: > On 07/19/12 12:57, J-L M wrote: >> Hello, >> We are trying to compile Firebird 2.1 >> for Android in order to use the embedded version in our mobile device >> of our software. >> But >> for the moment it seems impossible for some reasons : Android >> uses his own Libc called Bionic. And the problem is that there is a >> lot of missing features in. There is no implementation of the POSIX >> IPC or System V IPC inside, Android drop this to avoid >> denial-of-service. > > NO - they just _say_ that Posix IPC was dropped to avoid DOS, actually > Bionic is FreeBSD-based, and they never supported Posix IPC. > >> So, use of >> semaphore, shared memory, etc, is not possible. > > Unfortunately yes. > >> We >> have written a more complet document of this porterage which >> describes the problems in detail. >> > > Not needed - it's obvious :) > >> >> Somebody >> have already attempt to compile or to make an Android version of >> Firebird ? > > Yes. We can now build client library for Android. > >> What >> would be the good way to do that ? > > First of all - do not use old 2.1 version. > Good idea is doing development in trunk, may be later backport to 2.5. > In my future plans for Android port is to have our IPC implemented using > Android binder. > >> Otherwise, >> how to interest Firebird developpers to make this Android version ? > > Probably http://www.firebirdsql.org/en/how-to-become-a-sponsor/ > >> (Maybe I can create a topic in the tracker ) > > It exists http://tracker.firebirdsql.org/browse/CORE-3885 > And tracker is bad place for discussing ports. > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel > |
|
From: Alex P. <pes...@ma...> - 2012-07-20 13:09:34
|
On 07/20/12 16:20, JLM wrote: > Hello, > > Thanks all for your answers. > I didn't know that it was possible to build client library for Android. Hmm... I've written about it in a comment in the tracker :) > It's for ARM ? Yes. > How do buil that ? Checkout trunk and use the following configure (autogen.sh) parameter --with-cross-build=android.arme BTW - I did not find any VM in android's NDK. What is the best way to check/debug android's soft? Please also check correctness of defines in src/include/cross/android.arme - for lear reasons I had to emulate autogen's output manually. > Cross-compilation of Firebird runs with difficulty. Yes. Firebird requires a number of newly-built binaries to be executed during build. In trunk cross-compilation problem is partially solved (up to fbclient). The solution is clear - first of all I build required tools in gen/Native. Later during port I plan to solve all cross-compile issues up to getting installable package for cross architecture. > Do you use a classic > gcc cross-compiler of do you use the NDK toolset ? NDK toolset. But not in google-recommended mode - I just call required binaries like g++ from standard Makefile. |
|
From: Adriano d. S. F. <adr...@gm...> - 2012-07-23 02:03:30
|
On 20-07-2012 10:09, Alex Peshkoff wrote:
> On 07/20/12 16:20, JLM wrote:
>> Hello,
>>
>> Thanks all for your answers.
>> I didn't know that it was possible to build client library for Android.
>
> Hmm...
> I've written about it in a comment in the tracker :)
>
>> It's for ARM ?
>
> Yes.
>
>> How do buil that ?
>
> Checkout trunk and use the following configure (autogen.sh) parameter
> --with-cross-build=android.arme
>
I tried it, with official NDK but got error compiling common/CharSet.cpp
which needs ICU. So not even the client compiled.
---------------------------------------
asfernandes:~/fb/dev/trunk.git$ echo $NDK
/home/asfernandes/android/android-ndk-r8
asfernandes:~/fb/dev/trunk.git$ ./autogen.sh --with-cross-build=android.arme
/home/asfernandes/android/android-ndk-r8/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-g++
-ggdb -DFB_SEND_FLAGS=MSG_NOSIGNAL -DLINUX -DANDROID -DARM -pipe -MMD
-fPIC -fmessage-length=0
-I/home/asfernandes/fb/dev/trunk.git/extern/libtommath
--sysroot=/home/asfernandes/android/android-ndk-r8/platforms/android-9/arch-arm
-I/home/asfernandes/fb/dev/trunk.git/extern/icu/source/common
-I/home/asfernandes/fb/dev/trunk.git/extern/icu/source/i18n -O3
-fno-omit-frame-pointer
-I/home/asfernandes/fb/dev/trunk.git/src/include/gen
-I/home/asfernandes/fb/dev/trunk.git/src/include -pthread -fno-rtti
-c /home/asfernandes/fb/dev/trunk.git/src/common/CharSet.cpp -o
/home/asfernandes/fb/dev/trunk.git/temp/Release/common/CharSet.o
In file included from
/home/asfernandes/fb/dev/trunk.git/extern/icu/source/common/unicode/utypes.h:36,
from
/home/asfernandes/fb/dev/trunk.git/extern/icu/source/common/unicode/ucnv.h:56,
from
/home/asfernandes/fb/dev/trunk.git/src/common/../jrd/../common/unicode_util.h:33,
from
/home/asfernandes/fb/dev/trunk.git/src/common/../jrd/intl_classes.h:35,
from
/home/asfernandes/fb/dev/trunk.git/src/common/CharSet.cpp:95:
/home/asfernandes/fb/dev/trunk.git/extern/icu/source/common/unicode/umachine.h:52:33:
error: unicode/platform.h: No such file or directory
---------------------------------------
> BTW - I did not find any VM in android's NDK. What is the best way to
> check/debug android's soft?
The VM comes with the *SDK*. AFAIU, Android Apps can't be standalone
native executable. It must have a Java (Dalvik) laucher which calls the
native part as JNI.
> Please also check correctness of defines in
> src/include/cross/android.arme - for lear reasons I had to emulate
> autogen's output manually.
>
>> Cross-compilation of Firebird runs with difficulty.
>
> Yes. Firebird requires a number of newly-built binaries to be executed
> during build. In trunk cross-compilation problem is partially solved (up
> to fbclient). The solution is clear - first of all I build required
> tools in gen/Native. Later during port I plan to solve all cross-compile
> issues up to getting installable package for cross architecture.
>
>> Do you use a classic
>> gcc cross-compiler of do you use the NDK toolset ?
>
> NDK toolset. But not in google-recommended mode - I just call required binaries like g++ from standard Makefile.
>
Please note file docs/STANDALONE-TOOLCHAIN.html. It says that without
installing the toolchain in different location, RTTI, STL and exceptions
can't be used.
Adriano
|
|
From: Alex P. <pes...@ma...> - 2012-07-23 09:49:44
|
On 07/23/12 06:03, Adriano dos Santos Fernandes wrote: >> Checkout trunk and use the following configure (autogen.sh) parameter >> --with-cross-build=android.arme >> > I tried it, with official NDK but got error compiling common/CharSet.cpp > which needs ICU. So not even the client compiled. > > --------------------------------------- > asfernandes:~/fb/dev/trunk.git$ echo $NDK > /home/asfernandes/android/android-ndk-r8 > > asfernandes:~/fb/dev/trunk.git$ ./autogen.sh --with-cross-build=android.arme > > /home/asfernandes/android/android-ndk-r8/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-g++ > -ggdb -DFB_SEND_FLAGS=MSG_NOSIGNAL -DLINUX -DANDROID -DARM -pipe -MMD > -fPIC -fmessage-length=0 > -I/home/asfernandes/fb/dev/trunk.git/extern/libtommath > --sysroot=/home/asfernandes/android/android-ndk-r8/platforms/android-9/arch-arm > -I/home/asfernandes/fb/dev/trunk.git/extern/icu/source/common > -I/home/asfernandes/fb/dev/trunk.git/extern/icu/source/i18n -O3 > -fno-omit-frame-pointer > -I/home/asfernandes/fb/dev/trunk.git/src/include/gen > -I/home/asfernandes/fb/dev/trunk.git/src/include -pthread -fno-rtti > -c /home/asfernandes/fb/dev/trunk.git/src/common/CharSet.cpp -o > /home/asfernandes/fb/dev/trunk.git/temp/Release/common/CharSet.o > In file included from > /home/asfernandes/fb/dev/trunk.git/extern/icu/source/common/unicode/utypes.h:36, > from > /home/asfernandes/fb/dev/trunk.git/extern/icu/source/common/unicode/ucnv.h:56, > from > /home/asfernandes/fb/dev/trunk.git/src/common/../jrd/../common/unicode_util.h:33, > from > /home/asfernandes/fb/dev/trunk.git/src/common/../jrd/intl_classes.h:35, > from > /home/asfernandes/fb/dev/trunk.git/src/common/CharSet.cpp:95: > /home/asfernandes/fb/dev/trunk.git/extern/icu/source/common/unicode/umachine.h:52:33: > error: unicode/platform.h: No such file or directory > --------------------------------------- > Somewhy it happened that in my trunk I have platform.h in extern/icu/source/common/unicode. No idea how did it arrive in that dir (certainly, not under version control). As far as I know about Android, icu libraries are present in default device's setup. But question comes - what is best way to access them when doing cross-build? >> BTW - I did not find any VM in android's NDK. What is the best way to >> check/debug android's soft? > The VM comes with the *SDK*. Ahh - thank you. > AFAIU, Android Apps can't be standalone > native executable. It must have a Java (Dalvik) laucher which calls the > native part as JNI. Using latest NDK one can build complete native application. But for firebird this does not appear critical - first of all we provide libraries, out utlities do not make much sense (except for people who have non-standard Android with command line support). I hope that to start daemon on linux we need not have Java wrapper for it? :-) > Please note file docs/STANDALONE-TOOLCHAIN.html. It says that without > installing the toolchain in different location, RTTI, STL and exceptions > can't be used. That's not completely true. Setting correct flags for linker one can use at least exceptions without any problems. They should not cross module boundaries - but that's OK for us. |
|
From: Adriano d. S. F. <adr...@gm...> - 2012-07-23 10:42:05
|
On 23/07/2012 06:49, Alex Peshkoff wrote: > Somewhy it happened that in my trunk I have platform.h in > extern/icu/source/common/unicode. No idea how did it arrive in that dir > (certainly, not under version control). As far as I know about Android, > icu libraries are present in default device's setup. But question comes > - what is best way to access them when doing cross-build? If it's not in the NDK, then the library is unsupported and may not be in all versions. It's there just to the OS. So in this case we should supply it. But for client only we would not need ICU. This is a problem of our "common" library who have server-code which is never called by the client. Adriano |
|
From: Alex P. <pes...@ma...> - 2012-07-23 13:34:22
|
On 07/23/12 14:41, Adriano dos Santos Fernandes wrote: > On 23/07/2012 06:49, Alex Peshkoff wrote: >> Somewhy it happened that in my trunk I have platform.h in >> extern/icu/source/common/unicode. No idea how did it arrive in that dir >> (certainly, not under version control). As far as I know about Android, >> icu libraries are present in default device's setup. But question comes >> - what is best way to access them when doing cross-build? > If it's not in the NDK, then the library is unsupported and may not be > in all versions. It's there just to the OS. > > So in this case we should supply it. But for client only we would not > need ICU. This is a problem of our "common" library who have server-code > which is never called by the client. Hmm... I do remember that I had to add CharSet.cpp to common in order to build client. Will recheck. |
|
From: Adriano d. S. F. <adr...@gm...> - 2012-07-23 13:48:40
|
On 23/07/2012 10:34, Alex Peshkoff wrote: > On 07/23/12 14:41, Adriano dos Santos Fernandes wrote: >> On 23/07/2012 06:49, Alex Peshkoff wrote: >>> Somewhy it happened that in my trunk I have platform.h in >>> extern/icu/source/common/unicode. No idea how did it arrive in that dir >>> (certainly, not under version control). As far as I know about Android, >>> icu libraries are present in default device's setup. But question comes >>> - what is best way to access them when doing cross-build? >> If it's not in the NDK, then the library is unsupported and may not be >> in all versions. It's there just to the OS. >> >> So in this case we should supply it. But for client only we would not >> need ICU. This is a problem of our "common" library who have server-code >> which is never called by the client. > Hmm... > I do remember that I had to add CharSet.cpp to common in order to build > client. Will recheck. > > The problem is that some things (specially unicode_util) was added to common, but in fact, it's a piece needed only in engine and intl libraries. Adriano |
|
From: Alex P. <pes...@ma...> - 2012-07-24 13:15:54
|
On 07/23/12 17:48, Adriano dos Santos Fernandes wrote: > On 23/07/2012 10:34, Alex Peshkoff wrote: >> On 07/23/12 14:41, Adriano dos Santos Fernandes wrote: >>> On 23/07/2012 06:49, Alex Peshkoff wrote: >>>> Somewhy it happened that in my trunk I have platform.h in >>>> extern/icu/source/common/unicode. No idea how did it arrive in that dir >>>> (certainly, not under version control). As far as I know about Android, >>>> icu libraries are present in default device's setup. But question comes >>>> - what is best way to access them when doing cross-build? >>> If it's not in the NDK, then the library is unsupported and may not be >>> in all versions. It's there just to the OS. >>> >>> So in this case we should supply it. But for client only we would not >>> need ICU. This is a problem of our "common" library who have server-code >>> which is never called by the client. >> Hmm... >> I do remember that I had to add CharSet.cpp to common in order to build >> client. Will recheck. >> >> > The problem is that some things (specially unicode_util) was added to > common, but in fact, it's a piece needed only in engine and intl libraries. > Do you want to say that a member of static library, not used to resolve symbols during link, will anyway cause errors when it references non-existent library? I've always thought that ld is not so foolish. |
|
From: Adriano d. S. F. <adr...@gm...> - 2012-07-24 13:25:51
|
On 24/07/2012 10:15, Alex Peshkoff wrote: >> The problem is that some things (specially unicode_util) was added to >> common, but in fact, it's a piece needed only in engine and intl libraries. >> > Do you want to say that a member of static library, not used to resolve > symbols during link, will anyway cause errors when it references > non-existent library? I've always thought that ld is not so foolish. > > No, as we saw, it is working in trunk. It's not the greatest design, but... As I pointed it out, Android SDK/NDK has no ICU library and then our client (which technically does not need ICU) does not build without first manually build/install ICU. Weird. Adriano |
|
From: Adriano d. S. F. <adr...@gm...> - 2012-07-25 12:01:38
|
On 25/07/2012 06:17, Alex Peshkoff wrote: > On 07/24/12 17:25, Adriano dos Santos Fernandes wrote: >> On 24/07/2012 10:15, Alex Peshkoff wrote: >>>> The problem is that some things (specially unicode_util) was added to >>>> common, but in fact, it's a piece needed only in engine and intl libraries. >>>> >>> Do you want to say that a member of static library, not used to resolve >>> symbols during link, will anyway cause errors when it references >>> non-existent library? I've always thought that ld is not so foolish. >>> >>> >> No, as we saw, it is working in trunk. > Never tried to build/run on a box without ICU :) How did you build/installed the ICU ARM/Android library then to build fbclient? >> It's not the greatest design, but... >> > Do you think that creating separate library for intl-related things is > better? I'm not sure... > Any better suggestion? I can rework posix build schema easily. IMO yes. A good design needs common library not depending on non-common ones. Adriano |
|
From: Alex P. <pes...@ma...> - 2012-07-25 12:14:18
|
On 07/25/12 16:01, Adriano dos Santos Fernandes wrote: > On 25/07/2012 06:17, Alex Peshkoff wrote: >> On 07/24/12 17:25, Adriano dos Santos Fernandes wrote: >>> On 24/07/2012 10:15, Alex Peshkoff wrote: >>>>> The problem is that some things (specially unicode_util) was added to >>>>> common, but in fact, it's a piece needed only in engine and intl libraries. >>>>> >>>> Do you want to say that a member of static library, not used to resolve >>>> symbols during link, will anyway cause errors when it references >>>> non-existent library? I've always thought that ld is not so foolish. >>>> >>>> >>> No, as we saw, it is working in trunk. >> Never tried to build/run on a box without ICU :) > How did you build/installed the ICU ARM/Android library then to build > fbclient? > As I've already said: > Somewhy it happened that in my trunk I have platform.h in > extern/icu/source/common/unicode. No idea how did it arrive in that dir therefore fbclient was building successfully. With that file present no more ICU install was needed, cause I've added -I flags, pointing to iur builtin ICU 3.0. |
|
From: Alex P. <pes...@ma...> - 2012-07-25 09:18:01
|
On 07/24/12 17:25, Adriano dos Santos Fernandes wrote: > On 24/07/2012 10:15, Alex Peshkoff wrote: >>> The problem is that some things (specially unicode_util) was added to >>> common, but in fact, it's a piece needed only in engine and intl libraries. >>> >> Do you want to say that a member of static library, not used to resolve >> symbols during link, will anyway cause errors when it references >> non-existent library? I've always thought that ld is not so foolish. >> >> > No, as we saw, it is working in trunk. Never tried to build/run on a box without ICU :) > It's not the greatest design, but... > Do you think that creating separate library for intl-related things is better? I'm not sure... Any better suggestion? I can rework posix build schema easily. > As I pointed it out, Android SDK/NDK has no ICU library and then our > client (which technically does not need ICU) does not build without > first manually build/install ICU. Weird. > Taking into an account that our final aim is to build full firebird for android, not _too_ weird. But returning to full build. ICU is always present on android devices. Here is short abstract from google docs: > Locale > data > > > > Note that locale data comes solely from ICU. User-supplied locale > service providers (using the java.text.spi or java.util.spi mechanisms) > are not supported. > > Here are the versions of ICU (and the corresponding CLDR and Unicode > versions) used in various Android releases: > cupcake/donut/eclair ICU 3.8 [318]CLDR 1.5 [319]Unicode 5.0 > froyo ICU 4.2 [320]CLDR 1.7 [321]Unicode 5.1 > gingerbread/honeycomb ICU 4.4 [322]CLDR 1.8 [323]Unicode 5.2 > ice cream sandwich ICU 4.6 [324]CLDR 1.9 [325]Unicode 6.0 > jelly bean ICU 4.8 [326]CLDR 2.0 [327]Unicode 6.0 It's clear why it's not present in official API - ICU did not provide backward compatibility in new versions. But our trunk can work with any version! I.e. the only problem I see particularly for android port - is how to better provide correct platform.h for android on arm? |
|
From: JLM <so4...@ho...> - 2012-07-24 12:57:10
|
On 20/07/2012 15:09, Alex Peshkoff wrote: > On 07/20/12 16:20, JLM wrote: > Checkout trunk and use the following configure (autogen.sh) parameter > --with-cross-build=android.arme > > BTW - I did not find any VM in android's NDK. What is the best way to > check/debug android's soft? > Please also check correctness of defines in > src/include/cross/android.arme - for lear reasons I had to emulate > autogen's output manually. > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel Hello, I don't understand : yesterday I succeed in compiling libfbclient and today after I had checkout the trunk again, it used to run. It says "configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'." And configure seems to not read the android.arme file, I can try any name of file, it doesn't look in the file. Same thing when I put --host=arm-linux-androideabi in parameters of the configure, it stop at "checking whether setpgrp takes no argument... configure: error: cannot check setpgrp when cross compiling" whereas the android.arme file is there to fix this kind of problem. Regards, Jean-Louis Meuriot |
|
From: Alex P. <pes...@ma...> - 2012-07-24 13:02:55
|
On 07/24/12 16:56, JLM wrote: > On 20/07/2012 15:09, Alex Peshkoff wrote: >> On 07/20/12 16:20, JLM wrote: >> Checkout trunk and use the following configure (autogen.sh) parameter >> --with-cross-build=android.arme >> >> BTW - I did not find any VM in android's NDK. What is the best way to >> check/debug android's soft? >> Please also check correctness of defines in >> src/include/cross/android.arme - for lear reasons I had to emulate >> autogen's output manually. >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel > Hello, > > I don't understand : yesterday I succeed in compiling libfbclient and > today after I had checkout the trunk again, it used to run. > It says "configure: error: cannot run C compiled programs. > If you meant to cross compile, use `--host'." > > And configure seems to not read the android.arme file, I can try any > name of file, it doesn't look in the file. > Same thing when I put --host=arm-linux-androideabi in parameters of the > configure, it stop at > "checking whether setpgrp takes no argument... configure: error: cannot > check setpgrp when cross compiling" > whereas the android.arme file is there to fix this kind of problem. Sooner of all you've used slightly different switches in configure. BTW, --host should not be used. |
|
From: JLM <so4...@ho...> - 2012-07-25 09:44:44
|
Hello, I'm trying again to compile libfbclient but I can't. The configure script dot not succeed, because I'am cross-compiling. > echo $CC > arm-linux-androideabi-gcc > Running ./configure --enable-binreloc --with-cross-buil=android.arme ... > configure: WARNING: unrecognized options: --with-cross-buil > checking whether make sets $(MAKE)... yes > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-linux-gnu > checking whether binary relocation support should be enabled... yes > checking for gcc... arm-linux-androideabi-gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... configure: error: in `/home/jl/download/firebird': > configure: error: cannot run C compiled programs. > If you meant to cross compile, use `--host'. I have the last trunk's sources of today. With just "./autogen.sh --with-cross-buil=android.arme" it must succeed ? Regards, Jean-Louis Meuriot |
|
From: Alex P. <pes...@ma...> - 2012-07-25 11:28:50
|
On 07/25/12 13:44, JLM wrote: >> Running ./configure --enable-binreloc --with-cross-buil=android.arme ... >> configure: WARNING: unrecognized options: --with-cross-buil You shoud use --with-cross-build instead --with-cross-buil. You've lost last letter. |
|
From: JLM <so4...@ho...> - 2012-07-25 12:05:05
|
It's an error of my last trial, but even with ./autogen.sh --with-cross-build=android.arme it not succeed : > ./configure --with-cross-build=android.arme > checking whether make sets $(MAKE)... yes > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-linux-gnu > checking for /proc/self/maps... yes > checking whether everything is installed to the same prefix... no > checking whether binary relocation support should be enabled... no > checking for gcc... arm-linux-androideabi-gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... configure: error: in `/home/menlog/Téléchargements/firebird': > configure: error: cannot run C compiled programs. > If you meant to cross compile, use `--host'. > See `config.log' for more details On 25/07/2012 13:28, Alex Peshkoff wrote: > On 07/25/12 13:44, JLM wrote: > > >>> Running ./configure --enable-binreloc --with-cross-buil=android.arme ... >>> configure: WARNING: unrecognized options: --with-cross-buil > > You shoud use --with-cross-build instead --with-cross-buil. > You've lost last letter. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel > |
|
From: Alex P. <pes...@ma...> - 2012-07-25 12:23:18
|
On 07/25/12 16:04, JLM wrote: > It's an error of my last trial, but even with ./autogen.sh > --with-cross-build=android.arme it not succeed : > > >> ./configure --with-cross-build=android.arme >> checking whether make sets $(MAKE)... yes >> checking build system type... i686-pc-linux-gnu >> checking host system type... i686-pc-linux-gnu >> checking target system type... i686-pc-linux-gnu >> checking for /proc/self/maps... yes >> checking whether everything is installed to the same prefix... no >> checking whether binary relocation support should be enabled... no >> checking for gcc... arm-linux-androideabi-gcc >> checking whether the C compiler works... yes >> checking for C compiler default output file name... a.out >> checking for suffix of executables... >> checking whether we are cross compiling... configure: error: in `/home/menlog/Téléchargements/firebird': >> configure: error: cannot run C compiled programs. >> If you meant to cross compile, use `--host'. >> See `config.log' for more details Try to use --with-system-editline --enable-binreloc --with-cross-build=android.arme parameters. |
|
From: JLM <so4...@ho...> - 2012-07-25 12:44:18
|
On 25/07/2012 14:23, Alex Peshkoff wrote: > On 07/25/12 16:04, JLM wrote: >> It's an error of my last trial, but even with ./autogen.sh >> --with-cross-build=android.arme it not succeed : >> >> >>> ./configure --with-cross-build=android.arme >>> checking whether make sets $(MAKE)... yes >>> checking build system type... i686-pc-linux-gnu >>> checking host system type... i686-pc-linux-gnu >>> checking target system type... i686-pc-linux-gnu >>> checking for /proc/self/maps... yes >>> checking whether everything is installed to the same prefix... no >>> checking whether binary relocation support should be enabled... no >>> checking for gcc... arm-linux-androideabi-gcc >>> checking whether the C compiler works... yes >>> checking for C compiler default output file name... a.out >>> checking for suffix of executables... >>> checking whether we are cross compiling... configure: error: in `/home/menlog/Téléchargements/firebird': >>> configure: error: cannot run C compiled programs. >>> If you meant to cross compile, use `--host'. >>> See `config.log' for more details > > Try to use > --with-system-editline --enable-binreloc --with-cross-build=android.arme > parameters. Thanks for your response, but it's still not running, this parameter has changed nothing : ./configure --with-system-editline --enable-binreloc --with-cross-build=android.arme checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking whether binary relocation support should be enabled... yes checking for gcc... arm-linux-androideabi-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... configure: error: in `/home/menlog/Téléchargements/firebird': configure: error: cannot run C compiled programs. Regards, Jean-Louis Meuriot |
|
From: Alex P. <pes...@ma...> - 2012-07-25 12:51:43
|
On 07/25/12 16:43, JLM wrote: > On 25/07/2012 14:23, Alex Peshkoff wrote: >> On 07/25/12 16:04, JLM wrote: >>> It's an error of my last trial, but even with ./autogen.sh >>> --with-cross-build=android.arme it not succeed : >>> >>> >>>> ./configure --with-cross-build=android.arme >>>> checking whether make sets $(MAKE)... yes >>>> checking build system type... i686-pc-linux-gnu >>>> checking host system type... i686-pc-linux-gnu >>>> checking target system type... i686-pc-linux-gnu >>>> checking for /proc/self/maps... yes >>>> checking whether everything is installed to the same prefix... no >>>> checking whether binary relocation support should be enabled... no >>>> checking for gcc... arm-linux-androideabi-gcc >>>> checking whether the C compiler works... yes >>>> checking for C compiler default output file name... a.out >>>> checking for suffix of executables... >>>> checking whether we are cross compiling... configure: error: in `/home/menlog/Téléchargements/firebird': >>>> configure: error: cannot run C compiled programs. >>>> If you meant to cross compile, use `--host'. >>>> See `config.log' for more details >> Try to use >> --with-system-editline --enable-binreloc --with-cross-build=android.arme >> parameters. > Thanks for your response, but it's still not running, this parameter has > changed nothing Please send full console log and file config.log privately to pes...@ma... |
|
From: JLM <so4...@ho...> - 2012-07-26 07:19:20
|
On 25/07/2012 15:01, Alex Peshkoff wrote: > >>>>>> checking for gcc... arm-linux-androideabi-gcc > >>> Thanks for your response, but it's still not running, this parameter has >>> changed nothing > > Default compiler should be your native gcc, not cross-compiler. > That means I can't cross-compile with the configure script ? |
|
From: Alex P. <pes...@ma...> - 2012-07-26 08:11:12
|
On 07/26/12 11:18, JLM wrote: > On 25/07/2012 15:01, Alex Peshkoff wrote: >>>>>>> checking for gcc... arm-linux-androideabi-gcc >>>> Thanks for your response, but it's still not running, this parameter has >>>> changed nothing >> Default compiler should be your native gcc, not cross-compiler. >> > That means I can't cross-compile with the configure script ? Not sure what exactly means 'cross-compile with the configure script'. That means that you must export NDK=/path/to/ndk and when needed make will switch to cross-compiler from NDK. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X