msp430-gdb: All compilers are either blacklisted or unavailable; defaulting to first fallback option

[btywoniuk (Bart)]

msp430-gdb port declares that it is not compatible with some compilers: in fact, it declares that it is not compatible with every compiler that is compatible with the operating system. Therefore, no compilers remain that can compile this port, so you cannot compile this port on your operating system.

[btywoniuk (Bart)]

Error log main.log

[mf2k (Frank Schima)]

In the future, please add the port maintainer(s) to Cc (port info --maintainers msp430-gdb), if any.

[jmroot (Joshua Root)]

Avoiding the use of clang in this port dates back to when the port was first created in r88657, before the compiler.blacklist option existed. I can only assume it didn't compile with the version of clang that was shipped by Apple at the time.

[ryandesign (Ryan Carsten Schmidt)]

Well the log shows that it also doesn't compile with the version of clang in Xcode 9.3.

[mojca (Mojca Miklavec)]

See ​https://github.com/macports/macports-ports/pull/3336

[jmroot (Joshua Root)]

The PR was merged. Is this working now?

[mojca (Mojca Miklavec)]

Actually, the PR was about gcc and binutils (and it didn't even obsolete/replace the old ports), gdb wasn't brought up to date (we lack a nice portgroup for that).

However ryandesign made a bunch of changes to this port in August which probably fixed the reported issue itself, judging from commit messages.

• 95a774fe3d

msp430-gdb, msp430-gdb-devel: Reduce differences

• 28e09fe347

msp430-gdb, msp430-gdb-devel: Fix for Xcode 10

• 7026bf4a25

msp430-gdb, msp430-gdb-devel: Fix build with clang

Closes: #46291

That said, we should at some point:

• create a PortGroup for crossgdb
• create msp430-elf-gdb port using that group and the latest gdb
• make the old msp430* ports obsolete