How is glibc used?

[Tollef Fog Heen]

]] Michael Felt 

> I mention this because make check is reporting nearly all failures,
> while pkg-config-0-29.1 does seem to work?
> 
> Q. Why concerned about glibc?
> A. Because I am not using gcc as a compiler, and glibc demands
> "constructor" support, which my compiler does not have.

Are you confusing glibc and glib?  pkg-config uses glib, not
(necessarily) glibc.

> FAIL: check-cflags
> FAIL: check-libs
> FAIL: check-mixed-flags
> FAIL: check-non-l-flags
> FAIL: check-define-variable
> FAIL: check-libs-private
> FAIL: check-requires-private
> FAIL: check-circular-requires
> FAIL: check-includedir
> FAIL: check-conflicts
> FAIL: check-missing
> FAIL: check-special-flags
> FAIL: check-sort-order
> FAIL: check-duplicate-flags
> FAIL: check-whitespace
> FAIL: check-cmd-options
> FAIL: check-version
> FAIL: check-requires-version
> FAIL: check-print-options
> FAIL: check-path
> FAIL: check-sysroot
> FAIL: check-uninstalled
> FAIL: check-debug
> FAIL: check-gtk
> FAIL: check-tilde
> FAIL: check-relocatable
> FAIL: check-variable-override
> FAIL: check-variables
> ==============================================================================
> 28 of 28 tests failed
> Please report to
> https://bugs.freedesktop.org/enter_bug.cgi?product=pkg-config
> ==============================================================================
> 
> I am not left with a lot of confidence that "all is well".
> 
> Maybe you can see that the problem is because my shell is not bash,
> and my make is not gmake.

There should be a log file in there, can you give us what's in that? (Or
just run one of the tests manually.)

Cheers,
-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are