sqlite. I notice on my system there's
both .pc files. Have you checked with .pc files are found for sqlite
and sqlite3?
Regards, Thomas
--
Thomas Jahns
DKRZ GmbH, Department: Application software
Deutsches Klimarechenzentrum
Bundesstraße 45a
D-20146 Hamburg
Phone: +49-40-460094-151
ay
you think. But you could use an m4 define.
AC_SUBST([SQLITE3_CFLAGS])
AC_SUBST([SQLITE3_LIBS])
Or instead of putting SQLITE3 above use AC_SUBST([SQLITE3_CFLAGS],
["$SQLITE_CFLAGS"])
Regards, Thomas
--
Thomas Jahns
DKRZ GmbH, Department: Application software
Deutsches
Hello Felix,
not an automake issue, but...
On 01/16/14 13:02, Felix Salfelder wrote:
[rpath in uninstalled binary]
The normal mode of using libtool to run the binary with adjusted paths in
circumstances like yours is
./libtool --mode=execute main/program
Regards, Thomas
--
Thomas Jahns
DKRZ
I think this is an issue with your use of libtool and you might need to ensure
your tests run non-installed binaries prefixed with
$abs_topbuilddir/libtool --mode=execute
although the versions of libtool I know generate wrappers which arrange for that
automatically.
Regards, Thomas
--
Tho
Hello Andy,
On Mar 4, 2015, at 20:05 , Andy Falanga (afalanga) wrote:
The team I work with has a project which is a C++ shared library
which is exposed in two different manners. The first is a
traditional C++ library and the second is it's exposed, through
Boost.python, as a module. I fou
Hello Vincent,
On 03/05/15 18:43, Vincent Torri wrote:
I would also use $(top_builddir) instead of relative path. It could
help when building in another directory than the source one (like with
make distcheck)
I cannot see how .. would ever refer to the source tree and since libhwmgmt.la
is g
On 03/05/15 18:28, Andy Falanga (afalanga) wrote:
-Original Message-
From: Thomas Jahns [mailto:ja...@dkrz.de]
Sent: Wednesday, March 04, 2015 5:45 PM
To: Andy Falanga (afalanga)
Cc: automake@gnu.org
Subject: Re: How to use ld options correctly for --whole-archive in
automake and libtool
Hello,
On 06/22/15 15:44, Alex Vong wrote:
Is there any easy way to turn off c compiler warnings (those printed
to stderr) portably?
From my point of view, the easy way is to write portable code which does not
generate warnings. This is also the preferred and recommended way.
But automake i
Hi Alex,
On 06/28/15 16:21, Alex Vong wrote:
Besides, the code base is quite old and as we know compilers always
add new warnings. I have asked upstream about fixing the warnings, but
it seems there is no easy way to fix all of them. So I want to know is
there a portable way to silent all compil
he >/dev/null and instead make STREAM be
either '2>/dev/null' or the empty string ''?
Regards, Thomas
--
Thomas Jahns
HD(CP)^2
Abteilung Anwendungssoftware
Deutsches Klimarechenzentrum GmbH
Bundesstraße 45a • D-20146 Hamburg • Germany
Phone: +49 40 460094-151
Fax:
Hello,
I've run into the problem where a compiler we regularly use (NAG Fortran
compiler) has flag conventions that are at odds with libtool (i.e. nagfor uses
-Wc,opt to pass opt to the C compiler it uses as backend). For this reason I'd
like to add the compiler options to FCFLAGS in a form th
On 01/20/2017 11:21 AM, Bernhard Seckinger wrote:
I've got a program, that contains some php-script frontend (cli not web)
(and other stuff, which is irrelevant here). I've put the php-scripts into
$pkgdatadir. Now I'd like to have a link from $bindir to the main script i.e.
ln -s ${pkgdatadir}/
On 08/25/17 04:02, Kip Warner wrote:
I'd like to transform the following variable in my Makefile.am from...
files_only = a.foo b.foo c.foo d.foo ...
Into...
files_with_path = dir/a.foo dir/b.foo dir/c.foo dir/d.foo ...
Can you give more context why you need to substitute on the lef
Hello,
On 09/06/17 00:57, Nick Bowler wrote:
On 2017-09-05, Kip Warner wrote:
[...]
Hey Thomas. Good question. It could well be that no hackery at all is
required with this. Here is my Makefile.am:
https://github.com/cartesiantheatre/narayan-designer/blob/master/Source/Makefile.am
See parser
On 11/09/17 05:10, Jeffrey Walton wrote:
On Wed, Nov 8, 2017 at 3:53 PM, Jeffrey Walton wrote:
On Tue, Nov 7, 2017 at 12:33 PM, Jeffrey Walton wrote:
I'm trying to run 'make check' on Solaris. It results in:
$ ./cryptestcwd v
ld.so.1: cryptestcwd: fatal:
/export/home/cryptopp/.libs/libcrypto
On 01/25/18 04:07, Jay K wrote:
I have a bunch of C.
I want to move to C++.
I'm using automake.
I don't want to rename any files.
that's unwise and not going to serve you well in the long run. I very much
advise against not renaming files converted from C to C++. While it can be done,
this is
Hi,
On 10/28/18 1:42 AM, Harlan Stenn wrote:
pkg-conf offers the following ways to get "link flags":
--libsAll link flags
use the above and put it in the LIBS variable. No need to make this more
complicated.
--libs-only-L The -L/-R stuff
--libs-only-l The -l stuff
enable you to keep much more under control than only the sources. Users
would receive a complete environment that's almost guaranteed to produce
identical results to what you prepared for lectures/hands-on sessions.
Thomas Jahns
On 4/15/21 4:41 PM, Laurence Marks wrote:
As you say, i
netrable to a number of
scientists, who otherwise knew and used Python.
Regards, Thomas
--
Thomas Jahns
HPC-Gruppe
Abteilung Anwendungssoftware
Deutsches Klimarechenzentrum GmbH
Bundesstraße 45a • D-20146 Hamburg • Germany
Phone: +49 40 460094-151
Fax:+49 40 460094-270
Email: Thomas Jah
On 4/27/22 3:49 PM, R. Diez wrote:
Is there a way to speed 'automake' up?
While you are probably looking for system-independent advice, the best
results I've had with speeding up ephemeral builds is to simply use
/dev/shm for backing storage on Linux, i.e. first try to put build
directories
> On Apr 30, 2022, at 01:31 , Jan Engelhardt wrote:
>
> On Friday 2022-04-29 22:59, Thomas Jahns wrote:
>> On 4/27/22 3:49 PM, R. Diez wrote:
>>> Is there a way to speed 'automake' up?
>>
>> While you are probably looking for system-independent
On May 2, 2022, at 15:07 , Jan Engelhardt wrote:
>
>
> On Monday 2022-05-02 14:20, Thomas Jahns wrote:
>>>>> Is there a way to speed 'automake' up?
>>>>
>>>> [...let] ephemeral builds [..] use /dev/shm [...]
>>>
>>>
sible
approaches is highly welcome.
Kind regards, Thomas Jahns
smime.p7s
Description: S/MIME cryptographic signature
> On Nov 21, 2022, at 17:10 , Jan Engelhardt wrote:
> On Monday 2022-11-21 16:22, Thomas Jahns wrote:
>
>> The question consequently is: how would I create a Makefile.am that accounts
>> for a list of C sources, when the sources are not yet present/known from the
>&
On Nov 21, 2022, at 18:37 , Russ Allbery wrote:
> Thomas Jahns writes:
>
>> I know I can write a Makefile.in myself, but given the number of
>> additional targets users expect, I'd really prefer sticking to build
>> instructions as much as possible and delegate dis
25 matches
Mail list logo
