On a x86_64 host, libdir is expanded to exec_prefix/lib, as on i586.
However, most Linux distribution (and I guess FHS too) specify to use
exec_prefix/lib64, to make simultaneous installation of 32 and 64 bits
programs possible.
Am i supposed to manually set libdir according to build host to get
c
Hi Guillaume,
* Guillaume Rousse wrote on Thu, Mar 23, 2006 at 09:27:59AM CET:
> On a x86_64 host, libdir is expanded to exec_prefix/lib, as on i586.
> However, most Linux distribution (and I guess FHS too) specify to use
> exec_prefix/lib64, to make simultaneous installation of 32 and 64 bits
> p
Ralf Wildenhues wrote:
> * Guillaume Rousse wrote:
> > Am i supposed to manually set libdir according to build host to get
> > compliance with such constraint ?
>
> Yes, you can specify --libdir at configure time. Note for system
> installations you will usually have to set more options, for
> ex
I am looking for a way that automake or any other tool to scan source
code (.c or .cpp) files and generate list of depedencies( meaning header
files) needed to compile the module. And if there is another tool how
to interface it with automake
Jeff Safier
Cornell-Mayo Associates
600 Lanidex Plaza
Hi Jeff
Jeff Safier wrote:
I am looking for a way that automake or any other tool to scan source
code (.c or .cpp) files and generate list of depedencies( meaning header
files) needed to compile the module. And if there is another tool how
to interface it with automake
I think Automake does t
Hi!
On Tue, 2006-03-21 at 10:58 -0500, Jeff Safier wrote:
> I am looking for a way that automake or any other tool to scan source
> code (.c or .cpp) files and generate list of depedencies( meaning header
> files) needed to compile the module. And if there is another tool how
> to interface it wi