<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/configure, branch 0.4</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.4</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.4'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2010-10-30T20:20:33Z</updated>
<entry>
<title>configure: Add a check for the -Wl,--as-needed flag.</title>
<updated>2010-10-30T20:20:33Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-30T20:20:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6b9a717c26229accc6d871b3c7d77cb34d5a68ac'/>
<id>urn:sha1:6b9a717c26229accc6d871b3c7d77cb34d5a68ac</id>
<content type='text'>
This fits with our general build philosophy of checking at configure
time for desired support, (rather than putting platform-specific
conditionals into our Makefiles).
</content>
</entry>
<entry>
<title>fixup</title>
<updated>2010-10-30T20:16:50Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-30T20:16:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e94db26c5c7250c82cc2e2445fbb58cdb41847de'/>
<id>urn:sha1:e94db26c5c7250c82cc2e2445fbb58cdb41847de</id>
<content type='text'>
</content>
</entry>
<entry>
<title>configure: Remove a debugging print message.</title>
<updated>2010-10-30T20:15:00Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-30T20:11:22Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=660510ee4cdc25bcaf60a74000d2754c0f7794ff'/>
<id>urn:sha1:660510ee4cdc25bcaf60a74000d2754c0f7794ff</id>
<content type='text'>
This was never intended to be committed.
</content>
</entry>
<entry>
<title>configure: Test for flag to set rpath</title>
<updated>2010-10-30T20:15:00Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-30T19:55:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8753b9defa14bdc320ccb3b57b01a4ee7b81df00'/>
<id>urn:sha1:8753b9defa14bdc320ccb3b57b01a4ee7b81df00</id>
<content type='text'>
This is better than the previous approach which had a hardcoded Linux-specific
value in the Makefile.
</content>
</entry>
<entry>
<title>configure: Test for each compiler warning before enabling it.</title>
<updated>2010-10-30T20:11:56Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-30T19:36:06Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b802c18d3b9b0a2f5909e4c92ef7d6e7db234825'/>
<id>urn:sha1:b802c18d3b9b0a2f5909e4c92ef7d6e7db234825</id>
<content type='text'>
This should allow the build to be much more automatically portable
to compilers with different sets of warning options.
</content>
</entry>
<entry>
<title>configure: Set XAPIAN_CONFIG to only "xapian-config" by default.</title>
<updated>2010-10-29T21:49:20Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-10-29T21:49:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6e3007bec0b453e40d577bb98350cdc122379385'/>
<id>urn:sha1:6e3007bec0b453e40d577bb98350cdc122379385</id>
<content type='text'>
Previously, we preferred a value of "xapian-config-1.1" first. This
was convenient for compiling against Xapian 1.1 while Xapian 1.2 was
unreleased. But now that Xapian 1.2 is realease, and since it ships a
xapian-config, the xapian-config-1.1 value can mask the newer library.

Instead of trying to track the latest xapian-config-1.x in our
configure script let's simply expect the user to set
XAPIAN_CONFIG=xapian-config-1.x in order to compile against an
unreleased Xapian.
</content>
</entry>
<entry>
<title>configure: optimize uname finding a bit</title>
<updated>2010-10-29T21:33:14Z</updated>
<author>
<name>Felipe Contreras</name>
<email>felipe.contreras@gmail.com</email>
</author>
<published>2010-06-05T11:05:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9d9668e3e7b0e4ed5e054125841dd729a46abd79'/>
<id>urn:sha1:9d9668e3e7b0e4ed5e054125841dd729a46abd79</id>
<content type='text'>
Signed-off-by: Felipe Contreras &lt;felipe.contreras@gmail.com&gt;
</content>
</entry>
<entry>
<title>make install: Run ldconfig or install a DT_RUNPATH in binary as appropriate.</title>
<updated>2010-06-04T23:52:56Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-06-04T23:52:56Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d64d0cc8d9f9e9f23fa4432328db2ea4739bae0f'/>
<id>urn:sha1:d64d0cc8d9f9e9f23fa4432328db2ea4739bae0f</id>
<content type='text'>
Various users were confused as to why they couldn't run notmuch
immediately after "make install", (with linker errors saying that
libnotmuch.so could not be found). The errors came from two different
causes:

1. The user had installed to a system library directory, but had not
   yet run ldconfig.

2. The user had installed to some non-system directory, and had not
   set the LD_LIBRARY_PATH variable.

With this change we fix both problems (on Linux) without the user
having to do anything additional. We first use ldconfig to find the
system library directories. If the user is installing to one of these,
then we run ldconfig as part of "make install".

For case (2) we use the -rpath and --enable-new-dtags linker options
to install a DT_RUNPATH entry in the binary. This entry tells the
dynamic linker where to find libnotmuch. Without the
--enable-new-dtags option only a DT_RPATH option would be installed,
(which has the drawback of not allowing any override with the
LD_LIBRARY_PATH variable).

Distributions (such as Debian and Fedora) don't want to see binaries
packaged with a DT_RPATH or DT_RUNPATH entry. This should be avoided
automatically as long as the packages install to standard locations,
(such as /usr/lib).
</content>
</entry>
<entry>
<title>configure: Remove space from IFS (using tab as necessary)</title>
<updated>2010-06-04T23:51:32Z</updated>
<author>
<name>Carl Worth</name>
<email>cworth@cworth.org</email>
</author>
<published>2010-06-04T23:51:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b3076ed2693c6e32fd70a9ec78e36bc71727356e'/>
<id>urn:sha1:b3076ed2693c6e32fd70a9ec78e36bc71727356e</id>
<content type='text'>
The idea here is to more easily support filenames with spaces in them
in various loops. We're about to add a loop over the paths configured
by the dynamic linker. Hopefully, they wouldn't contain spaces, but
one never knows so we might as well be prepared.
</content>
</entry>
<entry>
<title>Add support for the Solaris platform</title>
<updated>2010-06-04T01:17:03Z</updated>
<author>
<name>Tomas Carnecky</name>
<email>tom@dbservice.com</email>
</author>
<published>2010-04-30T19:00:24Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a54cecfc8e8fb501d783806b1b603c7b283e00a1'/>
<id>urn:sha1:a54cecfc8e8fb501d783806b1b603c7b283e00a1</id>
<content type='text'>
Like on Mac OS X, the linker doesn't automatically resolve dependencies.

Signed-off-by: Tomas Carnecky &lt;tom@dbservice.com&gt;
</content>
</entry>
</feed>
