I had an issue a little while ago where for some reason the source for
DBD::ODBC had got ^M appended to every line, which our C compiler took a
dislike to.
Take a look at the some of the files mentioned below in the source code
and see if the same thing is happening.
Regards,
Rob
-----Original Message-----
From: [EMAIL PROTECTED]
[SMTP:[EMAIL PROTECTED]]
Sent: Thursday, September 19, 2002 9:32 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: FW: problem in installing DBD:ODBC
sorry!
Now i have setenv the CC complier
even then i get this error, Iam not able to help myself here.
error:
------
janarthp@sys1:/u/janarthp/DBD> make
/usr/local/bin/perl -I/usr/local/lib/perl5/5.6.1/sun4-solaris
-I/usr/local/lib/perl5/5.6.1 -MExtUtils::Command -e mkpath
blib/lib/DBD/ODBC
rm -f blib/lib/DBD/ODBC/Changes.pm
cp Changes blib/lib/DBD/ODBC/Changes.pm
cc -c -I. -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI
-I/usr/local/include -I/usr/include -I/usr/local/gnu/include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O -DVERSION=\"0.45_17\"
-DXS_VERSION=\"0.45_17\" -KPIC
-I/usr/local/lib/perl5/5.6.1/sun4-solaris/CORE
-I/u/janarthp/ODBC/iODBC/include ODBC.c
"ODBC.xs", line 1: warning: invalid white space character in directive
"./ODBC.h", line 9: warning: invalid white space character in directive
"./fixup_c.h", line 5: warning: invalid white space character in
directive
"./fixup_c.h", line 7: warning: invalid white space character in
directive
"./fixup_c.h", line 9: warning: invalid white space character in
directive
"./fixup_c.h", line 11: warning: invalid white space character in
directive
"./ODBC.h", line 11: warning: invalid white space character in directive
"./ODBC.h", line 13: warning: invalid white space character in directive
"./ODBC.h", line 15: warning: invalid white space character in directive
"./ODBC.h", line 17: warning: invalid white space character in directive
"ODBC.xs", line 172: undefined symbol: SQL_API_ODBC3_ALL_FUNCTIONS_SIZE
"ODBC.xs", line 185: undefined symbol: SQL_API_ODBC3_ALL_FUNCTIONS
"ODBC.xs", line 185: integral constant expression expected
"ODBC.xs", line 208: warning: invalid white space character in directive
"ODBC.xs", line 213: warning: invalid white space character in directive
"ODBC.xs", line 232: warning: argument #1 is incompatible with prototype:
prototype: pointer to char : "/usr/include/iso/string_iso.h",
line
66
argument : pointer to unsigned char
"ODBC.xs", line 252: warning: argument #1 is incompatible with prototype:
prototype: pointer to const char :
"/usr/local/lib/perl5/5.6.1/sun4-solaris/CORE/proto.h", line 550
argument : pointer to unsigned char
"ODBC.xs", line 260: warning: invalid white space character in directive
cc: acomp failed for ODBC.c
*** Error code 2
make: Fatal error: Command failed for target `ODBC.o'
janarthp@sys1:/u/janarthp/DBD>
-------
help!
thanks
Prassana
> -----Original Message-----
> From: Janarthanan, Prasanna > Sent: Thursday, September 19, 2002 1:34
PM
> To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Subject: problem in installing DBD:ODBC
> > hi > i have problem while installing DBD:ODBC.
> > I have tested the driver with the 'odbctest' of iODBC its working
> properly.
> > Error:
> janarthp@sys1:/u/janarthp/DBD> perl Makefile.PL -o
/u/janarthp/ODBC/iODBC
> > Configuring DBD::ODBC ...
> > >>> Remember to actually *READ* the README file!
> And re-read it if you have any problems.
> > Using DBI 1.21 installed in
> /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI
> Using ODBC in /u/janarthp/ODBC/iODBC
> > Umm, this looks like a iodbc type of driver manager.
> > We expect to find the isql.h, isqlext.h and iodbc.h files (which were
> supplied with iODBC) in $ODBCHOME/include directory alongside
> the /u/janarthp/ODBC/iODBC/lib/libiodbc.a
> /u/janarthp/ODBC/iODBC/lib/libiodbc.so
> /u/janarthp/ODBC/iODBC/lib/libiodbcinst.a
> /u/janarthp/ODBC/iODBC/lib/libiodbcinst.so library.
> > > Checking if your kit is complete...
> Looks good
> Using DBI 1.21 installed in
> /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI
> Writing Makefile for DBD::ODBC
> > The DBD::ODBC tests will use these values for the database
connection:
> DBI_DSN= e.g. dbi:ODBC:demo
> DBI_USER=
> DBI_PASS=
> Warning: not all required environment variables are set.
> > janarthp@sys1:/u/janarthp/DBD> nake
> nake: Command not found.
> janarthp@sys1:/u/janarthp/DBD> make
> /usr/local/bin/perl -I/usr/local/lib/perl5/5.6.1/sun4-solaris
> -I/usr/local/lib/perl5/5.6.1 -MExtUtils::Command -e mkpath
> blib/lib/DBD/ODBC
> rm -f blib/lib/DBD/ODBC/Changes.pm
> cp Changes blib/lib/DBD/ODBC/Changes.pm
> cp ODBC.pm blib/lib/DBD/ODBC.pm
> /usr/local/bin/perl -p -e "s/~DRIVER~/ODBC/g" <
> /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI/Driver.xst >
> ODBC.xsi
> /usr/local/bin/perl -I/usr/local/lib/perl5/5.6.1/sun4-solaris
> -I/usr/local/lib/perl5/5.6.1 /usr/local/lib/perl5/5.6.1/ExtUtils/xsubpp
> -typemap /usr/local/lib/perl5/5.6.1/ExtUtils/typemap ODBC.xs > ODBC.xsc
&&
> mv ODBC.xsc ODBC.c
> cc -c -I. -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI
> -I/usr/local/include -I/usr/include -I/usr/local/gnu/include
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O -DVERSION=\"0.45_17\"
> -DXS_VERSION=\"0.45_17\" -KPIC
> -I/usr/local/lib/perl5/5.6.1/sun4-solaris/CORE
> -I/u/janarthp/ODBC/iODBC/include ODBC.c
> sh: cc: not found
> *** Error code 1
> make: Fatal error: Command failed for target `ODBC.o'
> janarthp@sys1:/u/janarthp/DBD> make install
> cc -c -I. -I/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/DBI
> -I/usr/local/include -I/usr/include -I/usr/local/gnu/include
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O -DVERSION=\"0.45_17\"
> -DXS_VERSION=\"0.45_17\" -KPIC
> -I/usr/local/lib/perl5/5.6.1/sun4-solaris/CORE
> -I/u/janarthp/ODBC/iODBC/include ODBC.c
> sh: cc: not found
> *** Error code 1
> make: Fatal error: Command failed for target `ODBC.o'
> janarthp@sys1:/u/janarthp/DBD> > > -----
> > help!
> > thanks
> Prassana
>
This message is intended only for the use of the person(s) ("The intended
Recipient(s)") to whom it is addressed. It may contain information which
is privileged and confidential within the meaning of applicable law. If
you are not the intended recipient, please contact the sender as soon as
possible. The views expressed in this communication are not necessarily
those held by LYNX Express Limited.
