Opened 10 years ago
Closed 8 years ago
#42665 closed defect (fixed)
radare2 @0.9.6: error: unknown type name 'uint32_t'
| Reported by: | jwhowse4 | Owned by: | g5pw (Aljaž Srebrnič) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.1 |
| Keywords: | Cc: | cooljeanius (Eric Gallager) | |
| Port: | radare2 |
Description
I am using an Intel Mac Pro running Mac OS 10.8.5 (Mountain Lion) with XCode 5.0.2. When I try to upgrade the port radare from version 0.9.4 to version 0.9.6 the build fails with the attached error log. It appears that the system header file containing the type definition for uint32_t is not being included. I believe on Mountain Lion this file is called stdint.h. Any suggestions for a fix?
Attachments (1)
Change History (6)
Changed 10 years ago by jwhowse4
| Attachment: | radare2_main.log added |
|---|
comment:1 follow-up: 2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | g5pw@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to g5pw@… |
| Summary: | radare2 build failure → radare2 @0.9.6: error: unknown type name 'uint32_t' |
comment:2 Changed 10 years ago by jwhowse4
Replying to ryandesign@…:
I get the same error on Lion and a similar error on Snow Leopard (
sys.c:15: error: expected declaration specifiers or "..." before "uint32_t"). No problem on Mavericks. We should try updating the port to the latest version. If that doesn't help, the bug should be reported to the developers.
I believe version 0.9.6 is the latest version of radare2.
comment:4 Changed 10 years ago by g5pw (Aljaž Srebrnič)
Hello! 0.9.7 just got released, but it fails building on mavericks. I'm following it up with the developer upstream.
comment:5 Changed 8 years ago by g5pw (Aljaž Srebrnič)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This should be resolved with the upgrade to 0.9.9 in r142225.
I get the same error on Lion and a similar error on Snow Leopard (
sys.c:15: error: expected declaration specifiers or "..." before "uint32_t"). No problem on Mavericks. We should try updating the port to the latest version. If that doesn't help, the bug should be reported to the developers.