Opened 16 years ago
Closed 16 years ago
#3764 closed bug (invalid)
Config.pm doesn't extract from Autoconf or Perl zipfiles
Reported by: | haiqu | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/Command Line Tools | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
When installing Development options, the files called Config.pm do not extract from Autoconf or Perl. It appears they are protected somehow so that a foreign configuration file isn't used on the wrong system. I also tried to copy one from another drive and failed earlier tonight.
Puzzling.
Change History (7)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
In an apparently related fault, the latest build now locks up while trying to extract Autoconf. Building from BeOS 5.0.3 here.
comment:3 by , 16 years ago
This is likely something wrong with your host platform (BeOS 5.0.3) - as I have seen neither of these issues from a Linux host.
It's probably worth noting that the build system uses its own zip tool, rather than the host's own version of zip:
http://dev.haiku-os.org/browser/haiku/trunk/src/tools/zip
Perhaps something is configured wrong when this is compiled for BeOS during the first jam?
comment:4 by , 16 years ago
From within Haiku, if I open the Perl sources and extract them I still get missing files. This rules out BeOS as the culprit for the first problem, at least. Since the second happened only the next day I drew a link between them, but it also may have been coincidental.
comment:6 by , 16 years ago
As at hrev30266 I can no longer duplicate this fault. Consider it closed.
comment:7 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
I also tried unpacking the Perl sources (.tar.gz format) and these files were still missing. Expander shows them as being in the file, so there's possibly a problem with Expander, or rather the underlying shell executable that it calls.