Opened 13 years ago
Closed 13 years ago
#33113 closed defect (invalid)
openssl: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
| Reported by: | pkubaj@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | mww@…, jmroot (Joshua Root) | |
| Port: | openssl |
Description
I want to upgrade openssl 1.0.0f_0 to 1.0.0g_0 When I do, there are always plenty of error like in the title.
Attachments (1)
Change History (7)
Changed 13 years ago by pkubaj@…
comment:1 Changed 13 years ago by mf2k (Frank Schima)
| Keywords: | openssl 1.0.0g_0 removed |
|---|
comment:2 Changed 13 years ago by mww@…
| Cc: | jmr@… added |
|---|
comment:3 Changed 13 years ago by jmroot (Joshua Root)
Not really sure why I'm cc'd, but "shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory" suggests it's changed to a directory and then deleted it. Upgrading universal openssl worked fine here, so unless this happens for everyone on 10.7 (I'm on 10.6), you probably want to start by checking for filesystem corruption.
comment:4 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | openssl @1.0.0g_0 "No such file or directory" errors → openssl: shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory |
|---|
comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
pkubaj, have you made any progress with this? Is this still a problem with openssl 1.0.1, or with any other port? I can't see how it would be an openssl-specific problem.
comment:6 Changed 13 years ago by mww@…
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
I would also dismiss this report as a file system error. Please re-open if this problem persists with 1.0.1 and/or other ports!
I suppose this is a universal build?