Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#55131 closed defect (duplicate)

squeak doesn't compile.

Reported by: informatimago (Pascal J. Bourguignon) Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: squeak

Description


Attachments (1)

main.log (447.7 KB) - added by informatimago (Pascal J. Bourguignon) 7 years ago.
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_squeak/squeak/main.log

Download all attachments as: .zip

Change History (3)

Changed 7 years ago by informatimago (Pascal J. Bourguignon)

Attachment: main.log added

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_squeak/squeak/main.log

comment:1 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: duplicate
Status: newclosed

The log says:

:info:build In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_squeak/squeak/work/Squeak-3.9/platforms/unix/vm/debug.c:3:
:info:build /usr/include/stdio.h:445:18: error: too many arguments provided to function-like macro invocation
:info:build int     dprintf(int, const char * __restrict, ...) __printflike(2, 3) __OSX_AVAILABLE_STARTING(__MAC_10_7, __IPHONE_4_3);
:info:build                      ^
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_squeak/squeak/work/Squeak-3.9/platforms/unix/vm/debug.h:18:10: note: macro 'dprintf' defined here
:info:build # define dprintf(ARGS)  ((void)0)
:info:build          ^

So, the operating system defines a function dprintf, which it uses in its headers, but squeak defines a dprintf macro that overrides it and is incompatible. squeak shouldn't be doing that.

Duplicate of #36369.

comment:2 Changed 7 years ago by informatimago (Pascal J. Bourguignon)

The manual page says: dprintf() and vdprintf() conform to IEEE Std 1003.1-2008 (POSIX.1). So I guess, indeed, programs should avoid it.

Note: See TracTickets for help on using tickets.