Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#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:
Has a Patch: no Platform: All

Description

Doing a Grok for "bin/sed" shows that gzexe uses a hard coded path for sed.

Change History (2)

comment:1 Changed 9 years ago by mmadia

Resolution: fixed
Status: newclosed

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"

comment:2 in reply to:  1 Changed 9 years ago by bonefish

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.

Note: See TracTickets for help on using tickets.