building editors/vim with GTK2 option

[Chess Griffin]

* Joe Marcus Clarke <marcus at marcuscom.com> [2008-01-07 18:31:47]:

> 
> On Mon, 2008-01-07 at 17:36 -0500, Chess Griffin wrote:
> > I can't seem to figure out how to build editors/vim with the GTK2 option
> > enabled.  I first followed the 'Configuring port OPTIONS' in the
> > readme and created a vim/options file with the following:
> > 
> > _OPTIONS_READ=vim-7.1.211
> > WITH_GTK2=yes
> > 
> > but that didn't work.  Tinderbox built the regular vim with the GTK1
> > interface.
> 
> Did you follow the rest of the instructions, and enable OPTIONS:
> 
> ./tc configOptions -e -o /options
> 
> What is the output of:
> 
> ./tc configOptions

Yes, I did follow the rest of the instruction and enabled OPTIONS.
The output you asked for:

rose# ./tc configOptions
OPTIONS_DIR=/options
OPTIONS_ENABLED=1

Options for other ports work fine in this Tinderbox.  It's just a
problem with Vim's, but as you noted below, it seems that creating an
options file won't work due to the Vim Makefile. 

> 
> > 
> > So, I then used a hook to copy a custom make.conf over into the Build
> > at the 'postBuildExtract' stage.  This make.conf only had
> > WITH_GTK2=yes in it.  The file copied over correctly, but it caused
> > vim to fail the build with an mtree error.  I can attach portions of
> > the log if that would help.
> 
> Sounds like a port bug to me, but the log would definitely be helpful.
> On the other hand, this may be an issue with the generated Makefile
> being out of sync with the Build environment.  When the Makefile is
> generated, the make.conf used will be the one in the Jail directory
> (e.g. /space/jails/JAIL/make.conf).  If that file doesn't exist, or you
> don't want to set your options there, then you need to use a .env file
> (e.g. portstree.env, build.env, jail.env).
> 
> This might change.  It would probably make more sense for makemake to
> check /space/build/BUILD/make.conf, but that's not how it works now.

Ok, cool.  I have not investigated the .env files yet, but I might try
that next.

> 
> > 
> > I then tried to build it manually without tindered by specifying the
> > -o option to ./tc addPort.  That did not work because the Vim
> > Makefile uses a different options configuration.  Doing 'make config'
> > with Vim doesn't do anything.  One needs to build it WITH_GTK2=yes or
> > WITH_OPTIONS=yes in which case some ncurses options are presented.
> 
> Then simply creating an options file won't help.  Looks like the
> make.conf approach is the way to go, but the port may be broken with
> GTK2.
> 

Yep, something odd is going on here.  Building the port on a
non-Tinderbox machine using WITH_GTK2=yes does work, so I would think
the make.conf approach would work on a Tinderbox.  I don't have
access to the log atm, but I will try and post it or link to it in the
next day or two.

Thanks for the assistance.  I'll keep poking at it and will report
back with any additional information.


-- 
Chess Griffin
GPG Public Key:  0x0C7558C3
http://www.chessgriffin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://marcuscom.com/pipermail/tinderbox-list/attachments/20080107/8d4b6405/attachment.bin