On 22/10/02 16:07 -0700, James Michael DuPont wrote: > > --- Brian Ingerson <[EMAIL PROTECTED]> wrote: > > On 22/10/02 02:26 -0700, James Michael DuPont wrote: > > > > > > --- Brian Ingerson <[EMAIL PROTECTED]> wrote: > > > > On 22/10/02 01:46 -0700, James Michael DuPont wrote: > > > > > The makefile says : > > > > > PASTHRU = LIB="$(LIB)"\ > > > > > LIBPERL_A="$(LIBPERL_A)"\ > > > > > LINKTYPE="$(LINKTYPE)"\ > > > > > PREFIX="$(PREFIX)"\ > > > > > OPTIMIZE="$(OPTIMIZE)" > > > > > > > > > > LIB="$(LIB)" is evaled to LIB="blah\blah\blah\" that kills > > make. > > > > > I have change it to > > > > > PASTHRU = LIB="$(LIB) "\ > > > > > > > > What makefile? I really don't understand the comments above. > > Could > > > > you give > > > > me a little more context. > > > Sorry, > > > the Makefile.pl creates a Makefile. > > > The makefile somehow gets the LIB variable in the PASTHRU variable > > to > > > look like this : > > > LIB="D:\Program Files\Microsoft.Net\Odbc.Net\" > > LIBPERL_A="libperl.a" > > > LINKTYPE="dynamic" PREFIX="/usr" OPTIMIZE="" > > > > > > When it is passed to Inline:C, > > > LIB="D:\Program Files\Microsoft.Net\Odbc.Net\" is an unterminated > > > string, > > > LIB="D:\Program Files\Microsoft.Net\Odbc.Net\ " is ok. > > > > I get it now. Thanks. Looks like a bug caused by the new File::Spec > > changes. > > Could you send me the Inline invocation lines. Are you passing in a > > LIBS > > parameter? > > No this is junk that microsoft adding into my environment, > it affected all of my cygwin perl builds, sorry not a bug of inline.
Do you get the same bug with Inline-0.43? Do I need to fix something or not?? > > > > > > > I will try the cygwin inline python, cpr,cpp from CPAN. > > > I dont have java installed.... for cygwin, I have never used > > > inline::java. > > > > OK, cool. Just do whatever is readily available. > Well Inline::CPP built and tested fine. Python as well, but have not > tested it. > > > Here is an idea: Inline::Gateway. > > I want to use the OpenC++ and Boost Graph Lib from perl, but dont want > to pay alot. They have Python bindings, Why not use Inline::Python and > then reexport into Perl? What do you think ingy? I'd need more details. Cheers, Brian
