When I try to build existing GNU toolchain projects
using the Android and NDK sometimes I run into
problems with pthread. I get errors like this:
../../arm-linux-androideabi/bin/ld: cannot find -lpthread
Is there a switch to libtool to would ignore -lpthread
if it is found since Android
On Tue, 3 Apr 2012, greno wrote:
When I try to build existing GNU toolchain projects
using the Android and NDK sometimes I run into
problems with pthread. I get errors like this:
../../arm-linux-androideabi/bin/ld: cannot find -lpthread
Is there a switch to libtool to would ignore -lpthread
On Tue, 3 Apr 2012, Gerry Reno wrote:
Hi Bob. I think it's more of an issue that Android does not need an external
pthread library.
These projects all compiled and linked fine on Linux. But when you try to link
them using Android you get the error I
showed above.
The error is correct
And that is certainly an option although a highly intrusive one which for many
projects is not necessary.
I mean we have many different GNU toolchain projects that work on many
different platforms from a single codebase.
Libtool makes adjustments for other types of platforms. And this is just
On 04/03/2012 03:20 PM, Bob Friesenhahn wrote:
On Tue, 3 Apr 2012, Gerry Reno wrote:
Hi Bob. I think it's more of an issue that Android does not need an
external pthread library.
These projects all compiled and linked fine on Linux. But when you try to
link them using Android you get
Hello,
I am fixing leaks in one of my software projects that embeds libltdl
2.4.2 to load plugins. I noticed that when the plugin depends on the
dynamic library that the main program doesn't depend on, valgrind
reports some leaks.
We created a small testcase reproducing the problem. It's
On Tue, 3 Apr 2012, Brice Goglin wrote:
I am fixing leaks in one of my software projects that embeds libltdl
2.4.2 to load plugins. I noticed that when the plugin depends on the
dynamic library that the main program doesn't depend on, valgrind
reports some leaks.
If the main program is
Le 03/04/2012 23:13, Bob Friesenhahn a écrit :
On Tue, 3 Apr 2012, Brice Goglin wrote:
I am fixing leaks in one of my software projects that embeds libltdl
2.4.2 to load plugins. I noticed that when the plugin depends on the
dynamic library that the main program doesn't depend on, valgrind
On Tue, 3 Apr 2012, Brice Goglin wrote:
It is common for glibc to secretly allocate some memory for its own
use, and this is particularly true for multi-threaded programs. Often
it has no way to safely release this memory.
I tried with another dependency (libpci instead of libpthread), the
Le 04/04/2012 00:04, Bob Friesenhahn a écrit :
On Tue, 3 Apr 2012, Brice Goglin wrote:
It is common for glibc to secretly allocate some memory for its own
use, and this is particularly true for multi-threaded programs. Often
it has no way to safely release this memory.
I tried with another
10 matches
Mail list logo
