#13687 closed defect (fixed)
selfupdate 1.5.2 to 1.6.0 fails in registry (Panther)
Reported by: | william.allen.simpson@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts 1.7.0 |
Component: | base | Version: | 1.6.0 |
Keywords: | Cc: | william.allen.simpson@… | |
Port: |
Description
sudo port selfupdate Password: MacPorts base version 1.520 installed Downloaded MacPorts base version 1.600 Configuring, Building and Installing new MacPorts base Error: /opt/local/bin/port: selfupdate failed: Error installing new MacPorts base: shell command "cd /opt/local/var/macports/sources/rsync.macports.org/release/base && ./configure --prefix=/opt/local --with-install-user=root --with-install-group=admin --with-tclpackage=/Library/Tcl && make && make install" returned error 2 Command output: registry.c:305: error: `errPtr' undeclared (first use in this function) registry.c:306: error: request for member `status' in something not a structure or union registry.c: At top level: registry.c:321: error: parse error before '*' token registry.c: In function `reg_start_write': registry.c:322: error: `errPtr' undeclared (first use in this function) registry.c:323: error: request for member `status' in something not a structure or union registry.c: At top level: registry.c:333: error: parse error before '*' token registry.c: In function `reg_end': registry.c:334: error: request for member `status' in something not a structure or union registry.c:335: error: `errPtr' undeclared (first use in this function) registry.c:341: error: request for member `db' in something not a structure or union registry.c:341: error: `query' undeclared (first use in this function) registry.c:342: error: `SQLITE_OK' undeclared (first use in this function) registry.c:345: error: `SQLITE_BUSY' undeclared (first use in this function) registry.c:346: error: request for member `db' in something not a structure or union registry.c: At top level: registry.c:359: error: parse error before '*' token registry.c: In function `reg_commit': registry.c:360: error: `errPtr' undeclared (first use in this function) registry.c:361: error: request for member `status' in something not a structure or union registry.c: At top level: registry.c:376: error: parse error before '*' token registry.c: In function `reg_rollback': registry.c:377: error: `errPtr' undeclared (first use in this function) registry.c:378: error: request for member `status' in something not a structure or union make[2]: *** [registry.o] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1
Change History (10)
comment:1 Changed 17 years ago by raimue (Rainer Müller)
comment:2 Changed 17 years ago by william.allen.simpson@…
That was 2 days ago, and I'm reporting this in real time....
comment:3 Changed 17 years ago by raimue (Rainer Müller)
Yes, this was fixed in trunk, which does not affect the already released version 1.6.0.
comment:4 Changed 17 years ago by william.allen.simpson@…
Not cool. Panther users have to wait for 1.6.1? And I already have:
sqlite3 @3.5.2_0 (active)
So another problem could be that it's not using its own -I/opt/local/include, either!
comment:5 Changed 17 years ago by raimue (Rainer Müller)
If we would link against /opt/local/include, how should you be able to update anymore if the API changes? How should port selfupdate work, if the library it was linked to is gone? Therefore it uses a bundled sqlite3.
comment:6 Changed 17 years ago by william.allen.simpson@…
I was thinking more along the lines of falling back -- currently installed (/opt/local/include), OS, then bundled as backup.
AFAICT, "how should ... update anymore" didn't work out so well lately!
comment:7 Changed 17 years ago by ebgssth@…
verified ./configure; make works on 10.3 but I don't know how to test port itself.
comment:8 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)
Resolution: | → fixed |
---|---|
Status: | new → closed |
We simply cannot use anything within ${prefix}
when building MacPorts itself, as that would create some serious bootstrapping issues. There is a dmg for Panther in the works, which I haven't had a chance to look too much into lately, my fault, but unfortunately there's not much else we can do about this failure than waiting for that dmg and/or 1.6.1 (which arguably we could start pushing out sooner than later). The problem has been fixed in trunk and will be in 1.6.1, so I'm closing this ticket as fixed.
The reason why about two or three Panther specific bugs caught us by surprise is that there just aren't those many boxes out there any longer, and we're trying our best to maintain support for that legacy platform. Please bear with us!
-jmpp
comment:9 Changed 16 years ago by tobypeterson
Milestone: | MacPorts base bugs → MacPorts Future |
---|
Milestone MacPorts base bugs deleted
comment:10 Changed 15 years ago by jmroot (Joshua Root)
Milestone: | MacPorts Future → MacPorts 1.7.0 |
---|
I think this was fixed in r32212. Please confirm and close. See also #13631.