Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#146 with_expat breaks cppflags

closed-fixed
nobody
None
5
2005-10-28
2005-09-13
Anonymous
No

From: Ilya N. Golubev <gin@mo.msk.ru>
Versions: 1.0.0, 1.0.3

If `--with-expat' `configure' option argument specifies
a directory,
`LDFLAGS' and `CPPFLAGS' are set unconditionally as if
this directory
was a prefix in default autoconf installation
directories layout. Not
only this is useless if expat package is installed in a
different way.
Consider gcc on a system which native compiler is a
non-gnu one. It
uses its own modified versions of system headers, and
puts its
directory with these versions in front of its include
directory list.
If wv is compiled on a such system, and
`-I/usr/include' is specified
to it, native system headers will be included instead,
which will
break compilation.

Allowing to specify explicit, perhaps empty, values for
expat cppflags
and ldflags in build configuration is necessary.
Understand that
doing that for each external package used by your one
is tedious.
This is what <http://pkgconfig.freedesktop.org> is
for. If wv
installs some libraries for use by other packages,
please consider
using pkgconfig to install description of their
installation
configuration.

Discussion

  • Dom Lachowicz
    Dom Lachowicz
    2005-10-28

    Logged In: YES
    user_id=69417

    this was fixed in the 1.2.x release. we no longer support expat.

     
  • Dom Lachowicz
    Dom Lachowicz
    2005-10-28

    • status: open --> closed-fixed