llvm-3.3 - requires rebuild against libffi

[mzryz]

While installing OpenSSH Macport also attempted to update legacy-support but failed, stopping the process from installing the plist daemon for launching openssh. OS PPC Leopard.

Main.log attached with trace enabled.

[cjones051073 (Chris Jones)]

Issue is nothing to do with legacy support, but llvm-3.3

info:build dyld: Library not loaded: /opt/local/lib/libffi.7.dylib
508	:info:build   Referenced from: /opt/local/libexec/llvm-3.3/lib/libLTO.dylib

Looks like it might just need to be rebuilt against a new libffi.

[jmroot (Joshua Root)]

It already had a rev bump in [949b3480c346f83276ef6534a02d1d5dbbe09537/macports-ports].

[cjones051073 (Chris Jones)]

Mzryz, please check your ports are up to date.

sudo port -d sync
sudo port upgrade outdated

also make sure that first command successfully runs, i.e. the update is not blocked due to e.g. rsync being blocked by a local firewall.

[mzryz]

Replying to cjones051073:

Mzryz, please check your ports are up to date.

sudo port -d sync
sudo port upgrade outdated

also make sure that first command successfully runs, i.e. the update is not blocked due to e.g. rsync being blocked by a local firewall.

Thank you,

After doing 'sudo port -d sync'

I get the output:

Adding port irc/quassel
Adding subport quassel-client
Failed to parse file python/py-tensorflow-macos/Portfile: can't read "minimum_supported_major_version": no such variable
Failed to parse file python/py-tensorflow-metal/Portfile: can't read "minimum_supported_major_version": no such variable
Adding port science/magic
Adding port security/grype

Total number of ports parsed:	398 
Ports successfully parsed:	396 
Ports failed:			2 
Up-to-date ports skipped:	27724

DEBUG: Synchronization of 1 source failed
    while executing
"mportsync [array get global_options]"
port sync failed: Synchronization of 1 source failed

Will this be a problem? I assume the failure is in regards to that tensorflow error?

I have started the upgrade process as I imagine it may take a few days...

Cheers

[ryandesign (Ryan Carsten Schmidt)]

Replying to mzryz:

Failed to parse file python/py-tensorflow-macos/Portfile: can't read "minimum_supported_major_version": no such variable
Failed to parse file python/py-tensorflow-metal/Portfile: can't read "minimum_supported_major_version": no such variable

Will this be a problem? I assume the failure is in regards to that tensorflow error?

This will cause no problem, since it would only affect you if you tried to install py-tensorflow-macos or py-tensorflow-metal, which you can't on your OS or processor anyway. This "failed to parse" problem is tracked in #64313.

[mzryz]

Replying to ryandesign:

Replying to mzryz:

Failed to parse file python/py-tensorflow-macos/Portfile: can't read "minimum_supported_major_version": no such variable
Failed to parse file python/py-tensorflow-metal/Portfile: can't read "minimum_supported_major_version": no such variable

Will this be a problem? I assume the failure is in regards to that tensorflow error?

This will cause no problem, since it would only affect you if you tried to install py-tensorflow-macos or py-tensorflow-metal, which you can't on your OS or processor anyway. This "failed to parse" problem is tracked in #64313.

Alrighty, everything was updating perfectly till it hit libgcc7 @7.5.0_1, left it building over night, in the morning the terminal still said 'building' but it didn't seem active, so I checked system processes and saw 0% cpu usage and no compilers active. Very odd.

By the way - I am using a local repo, @kencu 's LeopardPorts so I already have the previous GCC installed and would be fine leaving as-is. I think this 'upgrade outdated' may be ignoring the pegged version he has? Sorry for my lack of knowledge I am quite a novice at this.

In the mean time I have asked for it to install OpenSSH again, hoping most parts that it needed are up-to-date now, and so far it looks promising and is happily compiling kerberos5 where as before it wouldn't. So I may be fine.

I guess is there a way I can tell Macports to ignore trying to update gcc7 in the future? Thanks for your patience.

[kencu (Ken)]

My sincere apologies, the LeopardPorts repo is a bit behind.

I had in fact taken it down for a while, but there were too many requests to put it back up so I restored it.

I would tell you not to use it at all any more, but to be honest, I see there are still fixes in there that can't be found anywhere else, for example libsdl2 for Leopard and the parts to install gimp on 10.5.

If you do use it, you'll have to be a bit cautious and check to make sure that your issue (like revbumping llvm-3.3 against libffi) is not coming from there. Feel free not to use the repo, or use it selectively.

I can't promise I will fix it. Some other users have been mobilizing fixes out of there, and the matching TigerPorts repo, and trying to incorporate them to MacPorts, with some success.

[cjones051073 (Chris Jones)]

Thanks for the explanation Ken. I am thus going to close this as its not an issue with the main repo., but your unofficial forked repo. Whilst I understand why they exist, and how it can be hard to get the fixes for the old OS into the main repo, this ticket is a good example of why I don't think we should really promote their use.

[kencu (Ken)]

Indeed, five or six years ago when those were invented I was silly enough to think that people might welcome a semi-official overlay for older systems rather than spaghetti up hundreds of ports with workarounds.

They worked well until I lost all interest and stopped maintaining them. I may take them down again.

[mzryz]

Just an update @kencu @cjones051073 my machine just successfully finished building gcc7 and updating all its ports. I think the issue was a combination of me having a strange combination of un-upgraded ports, the custom repo and also I found I hadn't selected a default gcc. I selected default gcc as mp-gcc7 and re-ran all my updates last night, and today they're all done.

Thanks again for helping a noob.

FYI kencu - without LeopardPorts many people wouldn't be able to use MacPorts at all with PPC, honestly the discovery of LeopardPorts enabled many in the community to use this amazing system. Even now my machine is working fine with it & I don't think the repo was to blame, just my silly configuration.