Re: APXS troubles

2007-07-21 Thread Farokh Irani
On Fri, Jul 20, 2007 at 11:39:35PM -0400, Farokh Irani wrote: I took a further look at apxs, and it appears that the bad coding for the source files continues. In my apxs around line 406, you'll find the following: foreach $s (@srcs) { my $slo = $s; $slo =~ s|\.c$|

Re: APXS troubles

2007-07-21 Thread Mike
On Fri, Jul 20, 2007 at 11:39:35PM -0400, Farokh Irani wrote: > I took a further look at apxs, and it appears that the bad coding for the > source files continues. In my apxs around line 406, you'll find the > following: > > foreach $s (@srcs) { > my $slo = $s; > $slo =~

Re: APXS troubles

2007-07-20 Thread Farokh Irani
On Fri, 2007-07-20 at 14:39 +0200, Mike wrote: On 7/20/07, Farokh Irani <[EMAIL PROTECTED]> wrote: > So, somewhere there is still something going on with .c vs .cpp. I'll > poke at apxs a bit and see if I can figure out why, but a crash > course in perl wasn't what I was looking at doing righ

Re: APXS troubles

2007-07-20 Thread William A. Rowe, Jr.
Mike wrote: > On 7/20/07, Farokh Irani <[EMAIL PROTECTED]> wrote: >> >So you mean a change from *.cpp to *.c is the only real working >> >solution? That's strange but anyway it works now... >> That is how it appears to be. Unfortunately, it's not a good solution >> because I really don't want to ha

Re: APXS troubles

2007-07-20 Thread Mike
On 7/20/07, Farokh Irani <[EMAIL PROTECTED]> wrote: >So you mean a change from *.cpp to *.c is the only real working >solution? That's strange but anyway it works now... That is how it appears to be. Unfortunately, it's not a good solution because I really don't want to have to rename a bunch of

Re: APXS troubles

2007-07-20 Thread Farokh Irani
On 7/20/07, Farokh Irani <[EMAIL PROTECTED]> wrote: So, somewhere there is still something going on with .c vs .cpp. I'll poke at apxs a bit and see if I can figure out why, but a crash course in perl wasn't what I was looking at doing right now :) So you mean a change from *.cpp to *.c is the o

Re: APXS troubles

2007-07-20 Thread Ralf Mattes
On Fri, 2007-07-20 at 14:39 +0200, Mike wrote: > On 7/20/07, Farokh Irani <[EMAIL PROTECTED]> wrote: > > So, somewhere there is still something going on with .c vs .cpp. I'll > > poke at apxs a bit and see if I can figure out why, but a crash > > course in perl wasn't what I was looking at doing ri

Re: APXS troubles

2007-07-20 Thread Mike
On 7/20/07, Farokh Irani <[EMAIL PROTECTED]> wrote: So, somewhere there is still something going on with .c vs .cpp. I'll poke at apxs a bit and see if I can figure out why, but a crash course in perl wasn't what I was looking at doing right now :) So you mean a change from *.cpp to *.c is the o

Re: APXS troubles

2007-07-20 Thread Mike
On 7/20/07, Ralf Mattes <[EMAIL PROTECTED]> wrote: I'd go for: if ( $f = ~m/\.c(c|pp){0,1}$/i ) This variant avoids backtracking and makes the regexp case insensitive. Yes, it does accept monsters like 'Foo.cPp'. but who cares :-) which is equal to if ( $f =~m/\.c(c|pp)?$/i )

Re: APXS troubles

2007-07-20 Thread Farokh Irani
There's a typo. It should be: if ( $f =~ m/\.c(c|pp){0,1}$/i ) OK, that seemed to work, but the .so file is once again an empty library. I then recompiled using .c as the extension, but when I tried to load apache, it complained of an unknown symbol, something with _gxx_personality. Mike

Re: APXS troubles

2007-07-20 Thread Ralf Mattes
On Fri, 2007-07-20 at 12:38 +0100, Jeremy Sowden wrote: > Farokh Irani wrote: > > >On Fri, 2007-07-20 at 08:36 +0200, Mike wrote: > > >> > > if ($f =~ m|\.c$|) { < Here, bad > > coder! BAD! > > >> > I don't know perl at all, so those were > > >> > stabs in the dark. Any poi

Re: APXS troubles

2007-07-20 Thread Jeremy Sowden
Farokh Irani wrote: > >On Fri, 2007-07-20 at 08:36 +0200, Mike wrote: > >> > > if ($f =~ m|\.c$|) { < Here, bad > coder! BAD! > >> > I don't know perl at all, so those were > >> > stabs in the dark. Any pointers on that would be appreciated. > >> Try: > > > if( $f =~ m/\.c$

Re: APXS troubles

2007-07-20 Thread Farokh Irani
On Fri, 2007-07-20 at 08:36 +0200, Mike wrote: > > if ($f =~ m|\.c$|) { < Here, bad coder! BAD! > I don't know perl at all, so those were > stabs in the dark. Any pointers on that would be appreciated. Try: > if( $f =~ m/\.c$|\.cpp$|\.cc$/ ) OK, I tried this and w

Re: APXS troubles

2007-07-20 Thread Ralf Mattes
On Fri, 2007-07-20 at 08:36 +0200, Mike wrote: > > > if ($f =~ m|\.c$|) { < Here, bad coder! BAD! > > I don't know perl at all, so those were > > stabs in the dark. Any pointers on that would be appreciated. > Try: > if( $f =~ m/\.c$|\.cpp$|\.cc$/ ) > Kind regards. I'd go

Re: APXS troubles

2007-07-19 Thread Mike
> if ($f =~ m|\.c$|) { < Here, bad coder! BAD! I don't know perl at all, so those were stabs in the dark. Any pointers on that would be appreciated. Try: if( $f =~ m/\.c$|\.cpp$|\.cc$/ ) Kind regards.

Re: APXS troubles

2007-07-19 Thread Farokh Irani
On Thu, 2007-07-19 at 10:41 -0400, Farokh Irani wrote: Did you get the file OK and have you had a chance to look at it?\ Yes and yes - even so it was binhexed ... Whoops. Sorry about that. I allready replied yesterday evening - no idea why you didn't get my mail. Anyway - indeed there is a

Re: APXS troubles

2007-07-19 Thread Mike
On Thu, Jul 19, 2007 at 06:12:26PM +0200, Ralf Mattes wrote: > Anyway - indeed there is a bug in APXS. Unless your input files have the > extention '.c' APXS won't invoke libtool in compile mode (hence it's > missing from your trace). Libtool in link mode will just create an empty > library ... [cu