Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 00:34, JonY wrote: On 9/10/2013 02:12, Ozkan Sezer wrote: *** Warning: linker path does not have real file for library -lole32. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a ***

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 09:08, Ozkan Sezer wrote: Tell me if you need anything else. Let's focus on the libtool 2.4.2.393-5d4a if that's ok with you. Can you provide the output from libtool --config and config.log? I'm not set up to easily duplicate your environment... Cheers, Peter

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 09:47, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:08, Ozkan Sezer wrote: Tell me if you need anything else. Let's focus on the libtool 2.4.2.393-5d4a if that's ok with you. Can you provide the output from libtool --config and

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 10:55, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:47, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:08, Ozkan Sezer wrote: Tell me if you need anything else. Let's focus on the libtool

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 11:26, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 10:55, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:47, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 11:50, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 11:26, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 10:55, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 12:25, Ozkan Sezer wrote: On 9/10/13, Ozkan Sezer seze...@gmail.com wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 11:26, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 10:55, Ozkan Sezer wrote: On 9/10/13, Peter

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 12:52, Ozkan Sezer wrote: That effectively cripples libtool for cross-compilers. Can the behavior be refined instead? Can you contact Charles Wilson about this? He should be reading this list, if he has time... Anyway, does this work? Cheers, Peter diff --git a/m4/libtool.m4

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 15:00, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 12:52, Ozkan Sezer wrote: That effectively cripples libtool for cross-compilers. Can the behavior be refined instead? Can you contact Charles Wilson about this? He should be reading this

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 15:29, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 15:00, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 12:52, Ozkan Sezer wrote: That effectively cripples libtool for cross-compilers. Can the behavior

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, JonY 10wa...@gmail.com wrote: On 9/10/2013 02:12, Ozkan Sezer wrote: *** Warning: linker path does not have real file for library -lole32. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a

./libs directory is not creating automatically

2013-09-10 Thread starz
I have used thic command libtool --mode=compile gcc -g -o -c foo.c The .o file is creating in the current directory. .libs in not creating. Actual output should be like this after the command: $libtool --mode=compile gcc -g -O -c foo.c mkdir .libs gcc -g -O -c foo.c -fPIC -DPIC -o

Re: Fwd: Fwd: android support

2013-09-10 Thread David Turner
Hello, Glad seeing this being addressed :-) On Tue, Sep 10, 2013 at 12:41 AM, Brooks Moses bmo...@google.com wrote: Hello, Marco, Thanks for pinging this -- I'm trying to work through some of the libtool patch backlog, and I'll have a look at this in the next few days. I note that David

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 12:52, Ozkan Sezer wrote: That effectively cripples libtool for cross-compilers. Can the behavior be refined instead? Can you contact Charles Wilson about this? He should be reading this list, if he has time... Anyway, does

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:47, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:08, Ozkan Sezer wrote: Tell me if you need anything else. Let's focus on the libtool 2.4.2.393-5d4a if that's ok with you. Can you

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 00:34, JonY wrote: On 9/10/2013 02:12, Ozkan Sezer wrote: *** Warning: linker path does not have real file for library -lole32. *** I have the capability to make that library automatically link in when *** you link to this

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 10:55, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:47, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:08, Ozkan Sezer wrote: Tell me if you need

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Ozkan Sezer seze...@gmail.com wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:08, Ozkan Sezer wrote: Tell me if you need anything else. Let's focus on the libtool 2.4.2.393-5d4a if that's ok with you. Can you provide the output from libtool --config

Re: libtool woes

2013-09-10 Thread Peter Rosin
On 2013-09-10 15:56, Ozkan Sezer wrote: OK then, I'll keep an eye on mails from this list. (On an irrelevant note, the archive pages at http://lists.gnu.org/archive/html/libtool/2013-09/index.html http://lists.gnu.org/archive/html/bug-libtool/2013-09/index.html doesn't list any mails from

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 11:26, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 10:55, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 09:47, Ozkan Sezer wrote: On 9/10/13, Peter

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 15:00, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 12:52, Ozkan Sezer wrote: That effectively cripples libtool for cross-compilers. Can the behavior be refined instead? Can you contact

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Ozkan Sezer seze...@gmail.com wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 11:26, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On 2013-09-10 10:55, Ozkan Sezer wrote: On 9/10/13, Peter Rosin p...@lysator.liu.se wrote: On

Re: Fwd: Fwd: android support

2013-09-10 Thread Brooks Moses
On Tue, Sep 10, 2013 at 1:05 AM, David Turner di...@google.com wrote: For the record, I've kept the $release to keep the structure similar to the glibc one. I admit I don't really know what that corresponds to, but I could successfully build working shared libraries for a few projects with my