Opened 14 years ago

Closed 14 years ago

#2482 closed defect (invalid)

Perl config for toolchain may not exclude host references

Reported by: NPM Owned by: lfs-book@…
Priority: normal Milestone: Future
Component: Book Version: 6.5
Severity: normal Keywords:
Cc:

Description

As shown in 5.27 (Perl 5.10.0), Configure's parameters can allow Perl to reference the host's libraries, headers and perl installation, which can lead to a build failure. If your host system has the GDBM library and headers installed, Configure can find them and use them as part of its "let me help you" mode; the build will fail when the GDBM library cannot be found in the toolchain lib dir.

Since the intent is to build a minimal Perl for the toolchain, I think the following may be a more proper set of params for Configure:

sh Configure -des -Dprefix=/tools -Dstatic_ext="Data/Dumper Fcntl IO POSIX" -Donlyextensions="Data/Dumper Fcntl IO POSIX" -Dglincpth="$LFS/tools/include" -Dglibpth="$LFS/tools/lib" -Dinc_version_list=none

The desired extensions are linked statically, *only* those extensions are built, Configure will look only in $LFS for 'extras', and it will not look for an existing Perl installation to mimic. It should do a better job of keeping the host out of the tool chain.

Change History (3)

comment:1 by Gilles Espinasse, 14 years ago

I don't understand why you use directly /tools for -Dprefix but choose to use the $LFS/tools for the 2 paths. Could it no be /tools for the three?

comment:2 by NPM, 14 years ago

Oops. You are correct. I do actually use /tools. In making my report 'conform' to normal LFS usage, I neglected to change 'prefix'. It was a mistake to attempt to make my report conform. Removing the $LFS from my example will make it clearer.

comment:3 by bdubbs@…, 14 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.