[OGo-Developer] sope and lib64

[Sebastian Reitenbach]

developer@opengroupware.org wrote: 
> On 14.01.2008, at 02:06, Sebastian Reitenbach wrote:
> > To install into FHS, the library directory is hardcoded, in the  
> > files above there are statements like this:
> >
> > =================================================================
> >  tmp = [NSString stringWithFormat:
> > #if CONFIGURE_64BIT
> >                    @"/lib64/sope-%i.%i/dbadaptors",
> > #else
> >                    @"/lib/sope-%i.%i/dbadaptors",
> > #endif
> ...
> > this will break on OpenBSD 64Bit architectures, and I think on any  
> > other *BSD too, maybe there are also Linuxes around, that do not  
> > have these lib64 woes.
> 
> Not sure what you mean by 'woes'. lib64 is required to run 32bit and  
> 64bit alongside, which is often required.
> Anyways, Debian also has this woe of not providing lib64 ;-)
however, so Linux makes it extra complicated as some have lib64, some not. 
On suse I have a /etc/SuSE-release file, is there sth. similar on Debian?
How does it look like on other Debian based distributions, are these with or 
without lib64? Just these questions are the woes ;)

Any good idea on how to detect reliably whether there is lib or lib64?

> 
> > Instead of passing the define CONFIGURE_64BIT I'd go change it and  
> > just pass either lib or lib64 at compile time directly. I'd detect  
> > it when running configure and write it into config.make. Then only  
> > grab the value from that central place?
> 
> Sounds reasonable.
> 
I've done that, for sope SOGo and OGo, the sope stuff is in the subversion 
branch, the rest only exists as patches.

Sebastian