title: Perl can't install Glib on Mac Big Sur
body: <p>I'm trying to install Gtk2 from CPAN on my Mac (Big Sur), but it requires Glib, and Glib install is failing.  The tail of the installer output is here:</p>
  <pre><code>echo Generating POD...
  Generating POD...
  &quot;/usr/bin/perl&quot; -I blib/lib -I blib/arch -MGlib::GenPod -MGlib \
          -e &quot;add_types (qq(doctypes));  Glib::GenPod::set_copyright(qq/Copyright (C) 2003-2011 by the gtk2-perl team.\n\nThis software is licensed under the LGPL.  See L&lt;Glib&gt; for a full notice.\n/); Glib::GenPod::set_main_mod(qq(Glib));  xsdoc2pod(q(build/doc.pl), q(blib/lib), q(build/podindex));&quot;
  Can't load 'blib/arch/auto/Glib/Glib.bundle' for module Glib: dlopen(blib/arch/auto/Glib/Glib.bundle, 0x0001): open(&quot;&quot;, O_RDONLY) failed with errno=2 at /System/Library/Perl/5.30/darwin-thread-multi-2level/DynaLoader.pm line 197.
   at blib/lib/Glib/GenPod.pm line 21.
  Compilation failed in require at blib/lib/Glib/GenPod.pm line 21.
  BEGIN failed--compilation aborted at blib/lib/Glib/GenPod.pm line 21.
  Compilation failed in require.
  BEGIN failed--compilation aborted.
  make: *** [build/podindex] Error 2
  FAIL
  ! Installing Glib failed. See /Users/principal/.cpanm/work/1626461722.68580/build.log for details. Retry with --force to force install it.
  </code></pre>
  <p>Retry with --force gives the same results.  The specified build.log file gives less detail than the console output above.</p>
  <p>If I understand what it's telling me, it is that the GenPod.m module fails at the point where it is trying to &quot;use Glib;&quot;.  But when I look at the specified search point (blib/arch/auto/Glib/Glib.bundle) there is such a file there.</p>
  <p>I'm using the Mac-installed Perl (5.30) and have had no other issues installing via CPAN.  Any help would be appreciated.  I would even welcome knowing how to bypass the &quot;GenPod&quot; step, as having working code is better than having documentation.  The latest post I could find on the topic of Glib failing to install on Mac was four years ago in the El Capitan days, and the OP there was having an entirely different problem.</p>