the resulting .gir file. this was broken for ports where the library name matches
a part of the build directory, like libgweather, libical and libgepub.
the parser would incorrectly match on the 'exe' line, which contains the temporary
object file created by g-ir-scanner with the gobject-introspection namespace identifier.
for example: libgweather-3.28.1/build-amd64/tmp-introspecteuljis0a/GWeather-3.0 instead
of libgweather-3.so.3.2.
so skip the first three lines of ldd output to prevent matching on the incorrect line
for now. it's not a pretty solution but allows further discussion with upstream on
a more correct fix.
debugged with and ok aja@
in the checks.
Someone clearly did not read the autoconf documentation because
using the following functions with a function declaration inside
the body will end up declaring a function inside a function.
- AC_TRY_COMPILE( [], [ int main() { return 0; } ],
- AC_LANG_PROGRAM([[]], [[int main (void) { return 0; }]])],
- AC_TRY_LINK([], [int main (void) { return 0; }],
Result:
int
main ()
{
int main (void) { return 0; }
;
return 0;
}
nested functions is a gcc extension which is not supported by
clang.
test.c:4:17: error: function definition is not allowed here
int main (void) { return 0; }
^
1 error generated.
This causes tests to fail in the configure scripts resulting in
missing compile and link time flags from the builds.
This resulted in weird behaviour of several software, like gnome
hanging completely due to gtk+3 not being built properly.
This change intrudces the following fixes:
- remove int main() declaration from AC_TRY_COMPILE, AC_LANG_PROGRAM, AC_TRY_LINK
as it comes with a declaration already, and people misused them
- change to use AC_LANG_SOURCE when needed in case a complete source block is specified
Most of the changes are in configure.(ac|in), however there were some cases
where autoconf is either broken or the build failed because of an autoconf
generated configure script. Everytihng else is switched to autoconf, so
the maintainers can go ahead and upstream these diffs.
There are more to come, we are continously checking the tree for these issues
and in the future the infrastructure will error if such a case is found.
- if CC is not set, fall back to cc
- do not forcibly add ${X11BASE}/include nor ${LOCALBASE}/include, now
the scanner is supposed to properly pass CFLAGS
- forcing -pthread should not be needed anymore
Tested with a handful of ports that were known to need these tweaks.
Any regression, please let me know directly.
ok jasper@
instead. It is just too hard to maintain a coherent list of still
reachable homepages for GNOME projects so use wiki.gnome.org which is
the entry point for *all* GNOME apps.
