Matthew Hawkins wrote:
> On Fri, 01 Dec 2000, Bram Moolenaar wrote:
> > Was GTK support broken? It always worked for me...
> It seems only if compiling from the port (/usr/ports/editors/vim6).
> What happens is link.sh removes libXt, and naturally not long after,
> linking fails. The same thing _dosn't_ happen if one simply compiles
> from the tarball.
I don't see how link.sh can remove a library and make linking fail. If
linking fails, link.sh won't remove the library.
I'm using FreeBSD myself, and it all works fine for me. I wonder what strange
thing the port does to break it?
> I was fixing this for the port maintainer (not a big fan of GTK) when I
> discovered the sigaltstack thing (I wanted python support in my own
> setup, so I added it in and *boom*).
> My fix for the port issue though is nasty (I brute-force -lXt in if
> building with GTK support) but it works. Hopefully David will accept it
Please send problems for Vim itself to me. The FreeBSD port shouldn't contain
any patches for the code, since Vim compiles fine without.
FATHER: You killed eight wedding guests in all!
LAUNCELOT: Er, Well ... the thing is ... I thought your son was a lady.
FATHER: I can understand that.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar Bram@... http://www.moolenaar.net
\\\ Vim: http://www.vim.org
ICCF Holland: http://iccf-holland.org