[LFS Trac] #2071: Perl doesn't know its vendor library location

Randy McMurchy lfs-user at mcmurchy.com
Fri Sep 7 08:57:04 PDT 2007

LFS Trac wrote these words on 09/07/07 09:20 CST:
> #2071: Perl doesn't know its vendor library location
>  Some packages (e.g., dpkg) run this command in order to know where they
>  should install their perl modules:
>  {{{
>  perl -MConfig -e 'print $Config{vendorlib}'
>  }}}
>  However, at least on the LiveCD, this prints an empty string. Please close
>  this ticket as invalid if the bug is LiveCD-specific.

I don't think it is a LiveCD issue, but I could be wrong. I say this
because the Pilot-Link package requires a patch to build the Perl
bindings. And the Perl part of the patch changes the "vendor" string
to the "site" string.

I've needed this for the last two versions of Pilot-Link.


rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux i686]
10:56:00 up 3 days, 10:58, 1 user, load average: 0.23, 0.20, 0.08

More information about the lfs-book mailing list