mspdebug: compilation error

[quantum7@…]

I am getting errors trying to install mspdebug. I'm getting compile errors. There's a number of errors (see attached log), but the core seems to be a problem with jtaglib:

:info:build cc  -DUSE_READLINE -I/opt/local/include -O1 -Wall -Wno-char-subscripts -ggdb -I. -Isimio -Iformats -Itransport -Idrivers -Iutil -Iui -DLIB_DIR=\"/usr/local/lib/\"  -o drivers/pif.o -c drivers/pif.c
:info:build In file included from drivers/jtaglib.c:28:
:info:build drivers/jtaglib.h:45:7: error: unknown type name 'address_t'
:info:build                                   address_t address);
:info:build                                   ^

I have included two log files for comparison:

• main_cleaned.log gives a full log after running port clean
• main_rerun.log gives a smaller set of errors after a second port install command.

[quantum7@…]

log from a clean install

[quantum7@…]

log after rerunning port install without cleaning

[quantum7@…]

I forgot to add my system info:

Mac OS 10.8.5

MacPorts 2.2.1

[g5pw (Aljaž Srebrnič)]

Hmm... did you install command line tools?

[quantum7@…]

I did have an older version of command line tools installed. I updated Xcode and the CLT to the latest mountain lion versions and re-accepted the license terms. Unfortunately, I'm still getting the same error.

Note that I tried installing mspdebug on another computer with a clean Macports install on mavericks and it compiled fine. So this is either specific to mountain lion or it's conflicting with one of my other ports.

[g5pw (Aljaž Srebrnič)]

Hello! is the bug still around? Does anyone still have problems with mspdebug?

[quantum7@…]

Replying to g5pw@…:

Hello! is the bug still around? Does anyone still have problems with mspdebug?

I'm still seeing the bug on my 10.8 macbook. It's not my primary computer so I haven't been too bothered by the compile failure, but I'd be happy to help debug the problem. Is there any information in addition to the logs that would help?

[g5pw (Aljaž Srebrnič)]

Ah, I found the problem. Solved in r116152. Please do a selfupdate and try again, feel free to reopen the ticket if it still fails.