#5565 closed bug (fixed)
/bin/gzexe is hardcoded for /bin/sed
Reported by: | mmadia | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/Command Line Tools | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Doing a Grok for "bin/sed" shows that gzexe uses a hard coded path for sed.
Change History (2)
follow-up: 2 comment:1 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 15 years ago
Replying to mmadia:
Applied hrev35832. In testing, only some applications can be gzexe'd and run successfully, such as Clockwerk. Other applications such as BePDF, BeZillaBrowser, and WonderBrush cause runtime_loader to complain "runtime_loader: Cannot open file <a needed lib>.so: No such file or directory"
I bet gzexe unzips the application to /tmp or something and runs them there, which will cause the application's local libraries not to be found anymore. A correct port would take that into account. I wouldn't be surprised, if there were problems with attributes, too.
Applied hrev35832. In testing, only some applications can be gzexe'd and run successfully, such as Clockwerk. Other applications such as BePDF, BeZillaBrowser, and WonderBrush cause runtime_loader to complain "runtime_loader: Cannot open file <a needed lib>.so: No such file or directory"