Opened 19 years ago

Closed 18 years ago

#4737 closed defect (fixed)

BUG: dnsupdate does not build on Tiger

Reported by: darwinports@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.0
Keywords: Cc: markd@…
Port:

Description

I started with a system on which I installed Tiger from scratch (wiped out everything that was previously there). Then I iterated Apple update until it stopped pulling in new items. Then I installed a freshly downloaded copy of XCode 2.1 (default install, no special settings). Then I downloaded the latest darwin ports, and after installing it, did a selfupdate.

Then I did a sudo port -c -d install dnsupdate Things start well, all the compiling goes fine, we land up with, in /opt/local/var/db/dports/build/file.blah.dnsupdate_dports_aqua_dnsupdate/work/DNSUpdate2/build two directories, a Deployment and a DNSUpdate2.build.

Unfortunately after the compiling/linking stage we have an install stage that operates based on copying things out of /opt/local/var/db/dports/build/file.blah.dnsupdate_dports_aqua_dnsupdate/work/DNSUpdate2/build/ DNSUpdate2.app and there is no such item. A look at the port file and the scrolling terminal text reveals no reference to such an item. My guess is that older versions of XCode/PBX generated this as part of their default project setup, and that XCode has changed in this respect, but what do I know --- I've always used Metrowerks, not XCode.

Anyway it would be nice if someone could look into this. If my hypothesis is correct, it might be worth trying to understand the dependency logic that caused this problem and doing a search across all port files to see what else is affected by this.

Change History (4)

comment:1 Changed 19 years ago by toby@…

severity: blockernormal

comment:2 Changed 19 years ago by mww@…

Summary: dnsupdate does not build on TigerBUG: dnsupdate does not build on Tiger

comment:3 Changed 18 years ago by markd@…

Cc: markd@… added

(In reply to comment #0)

Anyway it would be nice if someone could look into this. If my hypothesis is correct, it might be worth trying to understand the dependency logic that caused this problem and doing a search across all port files to see what else is affected by this.

I committed a fix for this just now. I can't explain it yet I'll have to ask the DP list myself. An update to Xcode handles a certain statement differently and creates a path problem. I don't know if this will break it on Panther yet, but I'd rather add in support for an older system if so than have it broken for the latest one right now.

comment:4 Changed 18 years ago by blb@…

Resolution: fixed
Status: newclosed

Resolving per markd@'s comment.

Note: See TracTickets for help on using tickets.