Strange behaviour of trace mode in MacPorts 2.4.3 / 10.13

[Ken Cunningham]

It’s almost _always_ pkg-config that is responsible for these wacky errors.

That has bit me dozens of times, including a week ago. Wasted hours.

We should probably just make pkg-config a default dependency for _every_ build and save everyone a pile of heartburn.

Ken






> On Apr 29, 2018, at 6:23 PM, Helmut K. C. Tessarek <tessarek at evermeet.cx> wrote:
> 
> On 2018-04-29 07:23, Joshua Root wrote:
>> Were dependencies declared on the ports providing those libraries? If
>> not, trace mode was just doing its job.
> 
> $ sudo port build -vst fontforge
> --->  Computing dependencies for fontforge
> --->  Fetching distfiles for fontforge
> --->  Verifying checksums for fontforge
> --->  Extracting fontforge
> --->  Applying patches to fontforge
> --->  Configuring fontforge
> Error: Failed to configure fontforge, consult
> /opt/local/var/macports/build/_Users_kct_data_work_ports_graphics_fontforge/fontforge/work/fontforge-2.0.20170731/config.log
> Warning: The following existing files were hidden from the build system
> by trace mode:
>  /opt/local/bin/pkg-config
>  /opt/local/bin/potrace
>  /opt/local/bin/update-desktop-database
>  /opt/local/bin/wget
>  /var/db/timezone/zoneinfo/America/Toronto
> Error: Failed to configure fontforge: configure failure: command
> execution failed
> Error: See
> /opt/local/var/macports/logs/_Users_kct_data_work_ports_graphics_fontforge/fontforge/main.log
> for details.
> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
> Error: Processing of port fontforge failed
> 
> In the config.log I can see this:
> 
> configure:20386: checking for zlib.h
> configure:20386: result: yes
> configure:20404: checking for GLIB
> configure:20472: result: no
> configure:20474: error: in
> `/opt/local/var/macports/build/_Users_kct_data_work_ports_graphics_fontforge/fontforge/work/fontforge-2.0.20170731':
> configure:20476: error: The pkg-config script could not be found or is
> too old.  Make sure it
> is in your PATH or set the PKG_CONFIG environment variable to the full
> path to pkg-config.
> 
> Alternatively, you may set the environment variables GLIB_CFLAGS
> and GLIB_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> 
> To get pkg-config, see <http://pkg-config.freedesktop.org/>.
> See `config.log' for more details
> 
> Hmm, so the trace mode hides /opt/local/bin/pkg-config, but then
> complains that pkg-config is too old.
> 
> What? Really? Hmmm. Double Hmmm.
> 
> Btw, glib is in /opt/local/lib:
> 
> $ ls *glib*
> libglib-2.0.0.dylib libglib-2.0.a       libglib-2.0.dylib
> 
> 
> Cheers,
>  K. C.
> 
> -- 
> regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
> Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
> 
> /*
>   Thou shalt not follow the NULL pointer for chaos and madness
>   await thee at its end.
> */
>