Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
There is a bug in the configure script that enables pango support when passing --without-pango to the configure script.
Thanks for the report, but you could go in more detail of what is the bug that you're experiencing?
When I try to disable pango support in the configure script:
$ ./configure --without-pango
It still tries to configure with pango support:
checking for CAIRO... yes
checking for PANGO... no
configure: error: Package requirements (pango >= 1.10) were not met:
No package 'pango' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables PANGO_CFLAGS
and PANGO_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
There is a bug in the line 29 of configure.ac script that will try to enable pango even when passing --disable-pango.
AC_ARG_WITH(pango, [ --with-pango],[text_v=pango],[text_v=cairo])
Ops. In the last paragraph, when I said --disable-pango, please read --without-pango.
libgdiplus by default doesn't use pango, it uses font rendering from cairo.
If you pass --with-pango (even --with-pango=no) it will probe the system for pango.
I understand the behavior, but it is not intuitive.
Probing for pango even when passing --without-pango makes no sense, and would confuse the user.
Good point, not way to know it without reading configure.ac.
I guess the code would be similar to what's done for libtiff.
It would be if you could try the change and make a PR out of it.
I'll send a patch to fix it.
Resolving as fixed, the rest can be discussed in a PR.