Ticket #21300 (closed defect: invalid)
zlib: Unable to open port: can't read "configure.cc_archflags": no such variable
| Reported by: | eed3si9n@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.0 |
| Keywords: | x86_64 cc_archflags | Cc: | ryandesign@… |
| Port: | zlib |
Description
Mac OS X Version 10.5.8.
After selfupdate to 1.8.0, I am having trouble running upgrade outdated.
Steps:
- Open macports.conf and set build_arch and universal_archs to x86_64.
- Run sudo port selfupgrade. This upgrades to 1.8.0.
- Run sudo port outdated. This lists libpng and zlib:
The following installed ports are outdated: libpng 1.2.37_0 < 1.2.38_0 zlib 1.2.3_2 < 1.2.3_3
- Run sudo port upgrade outdated.
Error: Unable to open port: can't read "configure.cc_archflags": no such variable
Attachments
Change History
Changed 4 years ago by eed3si9n@…
- Attachment macports.conf added
comment:1 Changed 4 years ago by blb@…
configure.cc_archflags should definitely be valid in MacPorts 1.8.0. Did you happen to be using port's interactive mode when you performed the steps? If so, selfupdate is definitely a bad command to run when in interactive mode if it updates MacPorts base code.
comment:2 Changed 4 years ago by ryandesign@…
- Cc ryandesign@… added
- Status changed from new to closed
- Resolution set to invalid
comment:3 Changed 4 years ago by eed3si9n@…
I ran sudo port selfupgrade from the Terminal. Also I confirmed the version number several times. Shouldn't it be 1.8.0 if port -v returns
MacPorts 1.8.0
Entering interactive mode... ("help" for help, "quit" to quit)
[work/helloworld] >
comment:5 Changed 4 years ago by ryandesign@…
- Status changed from closed to reopened
- Resolution invalid deleted
- Port changed from libpng, zlib to zlib
- Summary changed from zlib-1.2.38_0 "Error: Unable to open port: can't read "configure.cc_archflags": no such variable" to zlib: Unable to open port: can't read "configure.cc_archflags": no such variable
comment:6 Changed 4 years ago by blb@…
The output from
ls -l /opt/local/bin/port
would be most illuminating.
comment:7 Changed 4 years ago by eed3si9n@…
macsforever2000, blb, maybe I am running the version from trunk.
$ ls -l /opt/local/bin/port -r-xr-xr-x 1 root admin 122977 Jul 16 00:42 /opt/local/bin/port*
I'll install from package and see if the problem persists.
comment:8 Changed 4 years ago by eed3si9n@…
The problem went away after reinstalling 1.8.0 from package. I guess I had installed it from svn, and selfupdate didn't pick it up. I am sorry for the trouble, and thanks for your help.
comment:9 Changed 4 years ago by macsforever2000@…
- Status changed from reopened to closed
- Resolution set to invalid
Glad you got it working. Yes, if you install macports from trunk, selfupdate will not update it. You have to manually update it.
comment:10 Changed 4 years ago by blb@…
In the past (including up to 1.8.0) trunk-based installs wouldn't be affected by selfupdate, but now that we don't set the new trunk version to the next major release version, it should work better (trunk is currently 1.8.99 instead of 1.9.0). The basic issue was that 1.8.0 (trunk at any point along development) == 1.8.0 (final release), but with a timestamp of July 16, obviously that precedes the 1.8.0 final release in late August.
macports.conf