Re: [Sqlrelay-discussion] New oracle7 driver build error with 0.36.4 and oracle 10.1.0 client?

[Firstworks/4access <dav...@fi...>]

I've seen something similar before.  On 64 bit machines, "unsigned long"
may be a 64 bit integer, which is the same as an "unsigned long long".
I've seen compilers make mistakes when generating function signatures.

Ie.  startSendingLong(unsigned long) gets turned into
startSendingLong(unsigned long long) and then programs fail to find
startSendingLong(unsigned long) at link time.

You might be running into a problem like that.  If you run:
nm --demangle src/connection/.libs/libsqlrconnection.so
and send me the result, I'll take a look and see if that's what's
going on.  If your nm doesn't support the --demangle option, you may
have to figure out what the c++ function name demangling option is for
your nm.

If that's what's going on, you might see if there's an update for your
compiler.

SQL Relay 0.37 will use (u)int(16|32|64)_t types rather than long/short
types and that should fix the problem.

There's a prerelease of sqlrelay/rudiments available at
http://www.firstworks.com/sqlrelay-0.37pre2.tar.gz

You might want to give it a try and see if you still have the problem.

Let me know what you find out.

David Muse
dav...@fi...

On Fri, 2005-08-26 at 07:15 -0700, Eric Rybski wrote:
> I've successfully built 64-bit SQL Relay using 0.36.3 with the following setup:
> 	Solaris 9 (Generic_117171-17)
> 	Oracle 10.1.0 Client
> 	Rudiments 0.28.2
> 
> I recently downloaded 0.36.4, and tried to perform an installation on the same
> system with the same configuration options, but ended up with the following
> error during make:
> 
> Undefined                       first referenced
>  symbol                             in file
> sqlrconnection::startSendingLong(unsigned long).libs/oracle7connection.o
> ld: fatal: Symbol referencing errors. No output written to
> sqlr-connection-oracle7
> 
> Has anyone else had this problem with this new version of SQL Relay?  Any ideas
> on how to resolve it?
> 
> I've included the entire event log below.
> 
> Regards,
> Eric
> 

[snip]