Opened 3 years ago
Closed 3 years ago
#63600 closed defect (fixed)
vim @8.2.2681: +tiny and +small will not compile
Reported by: | evanmiller (Evan Miller) | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | vim |
Description
This appears to be a bug in the vim source, rather than in anything to do with MacPorts. Some functions / structs that rely on FEAT_EVAL
are called from vim9script.c even when FEAT_EVAL
is not defined.
:info:build /opt/local/bin/gcc-apple-4.2 -std=gnu99 -c -I. -Iproto -DHAVE_CONFIG_H -I/opt/local/include -DMACOS_X -DMACOS_X_DARWIN -pipe -Os -arch ppc -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/vim9script.o vim9script.c :info:build vim9script.c: In function 'current_script_is_vim9': :info:build vim9script.c:41: warning: implicit declaration of function 'SCRIPT_ID_VALID' :info:build vim9script.c:41: error: 'sctx_T' has no member named 'sc_sid' :info:build vim9script.c:42: warning: implicit declaration of function 'SCRIPT_ITEM' :info:build vim9script.c:42: error: 'sctx_T' has no member named 'sc_sid' :info:build vim9script.c:42: error: invalid type argument of '->' :info:build make[1]: *** [objects/vim9script.o] Error 1
+normal and larger sizes are not affected.
Change History (5)
comment:1 Changed 3 years ago by reneeotten (Renee Otten)
comment:2 Changed 3 years ago by evanmiller (Evan Miller)
It appears to have been fixed two revisions later:
https://github.com/vim/vim/releases/tag/v8.2.2683
So a very minor version bump should solve it.
comment:3 Changed 3 years ago by cooljeanius (Eric Gallager)
Cc: | cooljeanius added |
---|
comment:4 Changed 3 years ago by evanmiller (Evan Miller)
comment:5 Changed 3 years ago by evanmiller (Evan Miller)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
can you please report this to upstream then and provide the link here? I don't think that anyone here is going to fix this if it's not caused by MacPorts.