Opened 15 years ago

Closed 14 years ago

#7991 closed defect (wontfix)

BUG: vim 6.4.8 is linked against system libraries, libraries from ports are ignored

Reported by: master@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.2
Keywords: Cc: mij@…, yeled@…, markd@…
Port:

Description

Dear Jim,

otool -L on a newly generated binary showed me ncurses libray from /usr/lib, although ncurses port was installed.

Cause of the bug is that /usr/local/lib and /usr/local/include are hardcoded in configure as locations of local libraries and headers.

That can be fixed by rewriting /usr/local to ${prefix} by the following lines in Portfile pre-patch {

reinplace "s+/usr/local+${prefix}+g" "${worksrcpath}/src/configure.in" reinplace "s+/usr/local+${prefix}+g" "${worksrcpath}/src/auto/configure"

} or (may be) by setting LDFLAGS and CFLAGS to reference locations under ${prefix}.

Sincerely, Michail

Change History (6)

comment:1 Changed 15 years ago by yeled@…

Cc: yeled@… added
Status: newassigned

is this an issue for you? ncurses is rather fully featured on OS X.

comment:2 Changed 14 years ago by master@…

(In reply to comment #1)

is this an issue for you? ncurses is rather fully featured on OS X.

Dear Charlie,

Reductio ad absurdum : System vim is rather fully featured on OS X too. Thus vim port may be well left in unusable state.

Seriously, is seems to be darwinports policy to provide newer version s of system libraries and use them in preference to sustem ones (see zlib case). And maintainers are to maintain ports, not to judge if users need new versions or not. Every plaintiff able to present a case proving that a new minor version of a program is worth updating the port is much more likely to just compile it for himself and leave the obsolete or broken port as it is.

On another hand, ncurses lib was used as an example. Other libraries vim is linked agains are now taken from system set instead of the set formed by darwinports. In other cases changes between system and darwinports versions may be more important, than for ncurses (5.4 system vs 5.5 ports).

Sincerely, Michail

comment:3 Changed 14 years ago by yeled@…

Thanks, I understand the argument, was just wondering if you were experiencing a problem. I have found not linking ncurses to be a pain in Portfiles before is all.

comment:4 Changed 14 years ago by master@…

(In reply to comment #3)

Thanks, I understand the argument, was just wondering if you were experiencing a problem. I have found not linking ncurses to be a pain in Portfiles before is all.

No. I have not encountered any real problem. Just my mode of opertaion - when starting to work with a program, get the newest stable version, since if any problem arises (and they do), one of the first steps is to check if it is a bug fixed in releases more recent than the one used.

On the other hand, the new and shiny wide-char features of ncurses are not used widely, while 8-bit part seems to be stable. Thus the changes in recent ncureses versions are really minor for most users (who run Word, not vim anyway ;)

comment:5 Changed 14 years ago by markd@…

Cc: markd@… added

Can this bug be closed?

comment:6 Changed 14 years ago by markd@…

Resolution: wontfix
Status: assignedclosed
Note: See TracTickets for help on using tickets.