Re: [Sqlrelay-discussion] is SQL Relay "relocatable"?

[David M. <dav...@fi...>]

Using the disable-rpath options should prevent SQL Relay from looking in
the paths that the database libraries were found in at compile time.  If
it's not, then it sounds like there's a bug.

There are some other possible issues though.  The api's for perl, ruby,
python, etc. are compiled using compile strings generated by those
commands.  Those compile strings may introduce rpath's, depending on the
platform.  I'm not sure what to do about that other than modify the
configurations of perl, ruby, python, etc. so that they don't include
rpath.  I know on debian linux, they are already configured to exclude
rpath, but I'm not sure about other platforms.  I guess I could also add
code to filter the rpath's out, but that might turn out to be tricky.

Another issue is config file names and locations for temporary files.
The default paths for config files, debug files, temp files and so forth
are compiled into SQL Relay.  There are command line switches to make it
use other locations, but the default locations are compiled in.  I could
add an option requiring them to be specified on the command line though.

Dave
dav...@fi...

On Tue, 2008-03-04 at 09:57 +0000, Chris Underhill wrote: 
> ohn Klassa wrote:
> 
>  > Given this "definition" (if you will), is SQL Relay relocatable?  Do I
>  > need to do anything special, to make it so?
> 
> [Snip]
> 
>  > The closest thing I see is the rpath options, for which the "disable"
>  > versions are limited to:
>  >
>  >   --disable-oracle-rpath        Don't use -rpath when building Oracle 
> connection
>  >   --disable-freetds-rpath       Don't use -rpath when building FreeTDS
>  > connection
>  >   --disable-sybase-rpath      Don't use -rpath when building Sybase 
> connection
>  >   --disable-db2-rpath            Use -rpath when building DB2 connection
>  >
>  > This doesn't seem to cover all bases...
> 
> I've had similar problem in the past with sqlrelay linking to libraries 
> in my build environment. This I spotted as it caused grief with SELinux.
> 
> The solution (other than fixing the build scripts) is to install chrpath 
> and then run it against the libraries. If you're running Red Hat, it's 
> in the RPMForge repository. From the README file:
> 
> chrpath
> =======
> 
> chrpath allows you to modify the dynamic library load path (rpath) of
> compiled programs.  Currently, only removing and modifying the rpath
> is supported.  Eventually, I hope to be able to add an rpath if it is
> missing.
> 
> Cheers,
> 
> 
> Chris,.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Sqlrelay-discussion mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion
> 
> 
> __________________________________________________
> D O T E A S Y - "Join the web hosting revolution!"
>              http://www.doteasy.com



__________________________________________________
D O T E A S Y - "Join the web hosting revolution!"
             http://www.doteasy.com