* Ralf Wildenhues wrote on Thu, Nov 22, 2007 at 08:05:46AM CET:
>
> save_LDFLAGS=$LDFLAGS
> found=no
> for try in "" -L.../linux -L.../linux64; do
And there should be an
LDFLAGS="$LDFLAGS $try"
in here. Sorry about that.
> AC_LINK_IFELSE([AC_LANG_PROGRAM([PROLOGUE...], [BODY...])],
Hello Ting,
* susan xie wrote on Thu, Nov 22, 2007 at 04:10:27AM CET:
>
> > I want to use a third-party library in my Makefile.am. The static
> > third party library is put in a directory with 2 sub-directories:
> > 'linux' and 'linux64'. On 64bit machine, my code needs to link with
> > the stat
I'm getting pretty finalized on the automake build system for my
project. I was wondering, however, if anyone would mind going over
the configure.ac and Makefile.am files to proofread them and give any
suggestions, for instance if you see a better way to do things or if
it should be formatted diff
Hello Julien,
* Julien TIERNY (LIFL, TELECOM Lille 1) wrote on Wed, Nov 21, 2007 at
04:10:11PM CET:
> I use automake for the packaging of a software I wrote that uses third party
> shared libraries (at this point, everything's ok).
> Is it possible to force automake generate Makefiles such that
> From: [EMAIL PROTECTED]
> To: automake@gnu.org
> Date: Wed, 21 Nov 2007 15:47:29 -0500
> Subject: how to check 64bit or 32 bit machine?
>
>
> Hi,
>
> I want to use a third-party library in my Makefile.am. The static third party
> library is put in a directory with 2 sub-directories: 'linu
On Thu, 22 Nov 2007, Harlan Stenn wrote:
I use the last one quite often these days but sometimes I use the
first.
More than likely the various different possibilities I pointed out
seem a bit tiresome but they will eventually be important to someone.
I did miss one important case which is t
And of course, NFS file attribute caching can make detecting clock skew
a whole lot more interesting.
H
Bob Friesenhahn wrote:
> On Thu, 22 Nov 2007, Harlan Stenn wrote:
> > I *think* I'd be happy with 'clock skew in the build directory'.
>
> You mean like
>
>CPU -- NFS (Sources + Objects)
This is one case I know I care about.
> or
>
> NFS1 (Sources)
> /
>CPU
> \
>
On Thu, 22 Nov 2007, Harlan Stenn wrote:
All of these problems are possible. Some issues are seen by GNU make
and others are not.
I *think* I'd be happy with 'clock skew in the build directory'.
You mean like
CPU -- NFS (Sources + Objects)
or
NFS1 (Sources)
/
CPU
Bob Friesenhahn wrote:
> On Wed, 21 Nov 2007, Harlan Stenn wrote:
> >
> > A variety of problems can crop up if one is "doing things" in an
> > NFS-mounted filesystem and there is clock skew between the local machine
> > (NFS client box) and the machine that hosts the actual filesystem (NFS
> > ser
On Wed, 21 Nov 2007, Harlan Stenn wrote:
A variety of problems can crop up if one is "doing things" in an
NFS-mounted filesystem and there is clock skew between the local machine
(NFS client box) and the machine that hosts the actual filesystem (NFS
server box).
I suggest that you check out s
I have not put enough thought into the following.
A variety of problems can crop up if one is "doing things" in an
NFS-mounted filesystem and there is clock skew between the local machine
(NFS client box) and the machine that hosts the actual filesystem (NFS
server box).
I am thinking there may
Hi,
I want to use a third-party library in my Makefile.am. The static third party
library is put in a directory with 2 sub-directories: 'linux' and 'linux64'.
On 64bit machine, my code needs to link with the static library in 'linux64'
directory. While on 32 bit machine, it needs to link with
hi there!
I use automake for the packaging of a software I wrote that uses third party
shared libraries (at this point, everything's ok).
Is it possible to force automake generate Makefiles such that the final binary
program is statically linked to the third party libraries? (I've got *.so and
*
14 matches
Mail list logo
