Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#37461 closed defect (fixed)

libgsasl @1.6.1 build failure: typedef redefinition with different types

Reported by: ltb@… Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: seanfarley (Sean Farley)
Port: libgsasl

Description

Recently upgraded to OS X 10.8.2, upgraded to XCode 4.5.2, attempted to migrate macports and reinstall my ports, step 4 (running the Perl script to upgrade all the ports In myports.txt failed due to permissions, then tried to install msmtp port so I could send emails from my MUA. The build of libgsasl (on which msmtp depends) failed.

Attachments (1)

main.log (67.3 KB) - added by ltb@… 8 years ago.
log file for libgsasl build failure

Download all attachments as: .zip

Change History (9)

Changed 8 years ago by ltb@…

Attachment: main.log added

log file for libgsasl build failure

comment:1 Changed 8 years ago by jmroot (Joshua Root)

Owner: changed from macports-tickets@… to ryandesign@…
Summary: org.macports.build for port libgsasl returned: command execution failedlibgsasl @1.6.1 build failure: typedef redefinition with different types

Please remember to Cc the maintainer.

comment:2 Changed 8 years ago by seanfarley (Sean Farley)

Resolution: fixed
Status: newclosed

I went ahead and fixed this by updating to 1.8.0 in r101370. I hope that doesn't step on your toes too much, Ryan.

comment:3 Changed 8 years ago by ryandesign (Ryan Schmidt)

Cc: sean@… added

Thanks for updating the port since I had not gotten around to doing so, but additional steps are needed; see comment:ticket:35345:7.

comment:4 in reply to:  3 ; Changed 8 years ago by seanfarley (Sean Farley)

Replying to ryandesign@…:

Thanks for updating the port since I had not gotten around to doing so, but additional steps are needed; see comment:ticket:35345:7.

Oh no! Man, I wish Trac had better searching and linking so I could have seen that :-( I see the following ports explicitly depend on libgsasl: libinfinity, anubis, libvmime, mpop, msmtp, jabberd, and gobby. I'm guessing there's no easy way save for watching the buildbot fail to see if there are silently linked ports?

comment:5 in reply to:  4 ; Changed 8 years ago by ryandesign (Ryan Schmidt)

Replying to sean@…:

Replying to ryandesign@…:

Thanks for updating the port since I had not gotten around to doing so, but additional steps are needed; see comment:ticket:35345:7.

Oh no! Man, I wish Trac had better searching and linking so I could have seen that :-(

I always search Trac using a browser shortcut which expands to e.g. ?status=!closed&summary=~libgsasl. This relies on the port name being in the Summary field, but our ticket filing instructions say people should put it there, and if I find tickets without the port name in the Summary, I add it. You can also search on the Port field instead e.g. ?status=!closed&port=~libgsasl. You can also use report 16 which searches the port field e.g. 16?PORT=libgsasl. But I find more users neglect to put the port name in the Port field than those that neglect to put it in the Summary.

I see the following ports explicitly depend on libgsasl: libinfinity, anubis, libvmime, mpop, msmtp, jabberd, and gobby. I'm guessing there's no easy way save for watching the buildbot fail to see if there are silently linked ports?

I agree that's the list of 7 ports depending on libgsasl so they should be revbumped. The rev-upgrade feature, if you've left it turned on, should tell you if there are any linking errors among the ports you've installed, but won't help you find other mislinked ports that you hadn't installed. We could try installing any ports that depend on any of those 7 ports and see if any of them are linked to libgsasl. Or we could install those ports from the binaries and see if they're mislinked (or download and check the binaries manually). And we can just wait for users to file tickets as they encounter problems and fix them then.

comment:6 in reply to:  5 ; Changed 8 years ago by seanfarley (Sean Farley)

Replying to ryandesign@…:

Replying to sean@…:

Replying to ryandesign@…:

Thanks for updating the port since I had not gotten around to doing so, but additional steps are needed; see comment:ticket:35345:7.

Oh no! Man, I wish Trac had better searching and linking so I could have seen that :-(

I always search Trac using a browser shortcut which expands to e.g. ?status=!closed&summary=~libgsasl. This relies on the port name being in the Summary field, but our ticket filing instructions say people should put it there, and if I find tickets without the port name in the Summary, I add it. You can also search on the Port field instead e.g. ?status=!closed&port=~libgsasl. You can also use report 16 which searches the port field e.g. 16?PORT=libgsasl. But I find more users neglect to put the port name in the Port field than those that neglect to put it in the Summary.

Ah, very helpful; thanks!

I see the following ports explicitly depend on libgsasl: libinfinity, anubis, libvmime, mpop, msmtp, jabberd, and gobby. I'm guessing there's no easy way save for watching the buildbot fail to see if there are silently linked ports?

I agree that's the list of 7 ports depending on libgsasl so they should be revbumped. The rev-upgrade feature, if you've left it turned on, should tell you if there are any linking errors among the ports you've installed, but won't help you find other mislinked ports that you hadn't installed. We could try installing any ports that depend on any of those 7 ports and see if any of them are linked to libgsasl. Or we could install those ports from the binaries and see if they're mislinked (or download and check the binaries manually). And we can just wait for users to file tickets as they encounter problems and fix them then.

One of the reasons I didn't see this is because I didn't have any ports that depend on libgsasl and neither did the buildbot, it seems. Hopefully, rev bumping will get the buildbot to tell us if that will work or not :-/

comment:7 in reply to:  6 ; Changed 8 years ago by ryandesign (Ryan Schmidt)

Replying to sean@…:

One of the reasons I didn't see this is because I didn't have any ports that depend on libgsasl and neither did the buildbot, it seems.

The buildbot doesn't have any ports installed. All ports are uninstalled after every build.

Hopefully, rev bumping will get the buildbot to tell us if that will work or not :-/

The buildbot should hopefully successfully build the 7 ports you revbump, but this won't tell us about any other ports that may have indirect or undeclared dependencies on libgsasl.

comment:8 in reply to:  7 Changed 8 years ago by seanfarley (Sean Farley)

Replying to ryandesign@…:

Replying to sean@…:

One of the reasons I didn't see this is because I didn't have any ports that depend on libgsasl and neither did the buildbot, it seems.

The buildbot doesn't have any ports installed. All ports are uninstalled after every build.

Ah, I did not know that. Thanks for the info.

Hopefully, rev bumping will get the buildbot to tell us if that will work or not :-/

The buildbot should hopefully successfully build the 7 ports you revbump, but this won't tell us about any other ports that may have indirect or undeclared dependencies on libgsasl.

Gotcha. I'll revbump these 7 ports and watch the results.

Note: See TracTickets for help on using tickets.