Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#20139 closed defect (invalid)

vte fails to build

Reported by: jp@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.7.1
Keywords: gtk +no_x11 Cc:
Port: vte

Description

vte fails to build. See the debug output attached. I think the error is caused by a missing gdkx.h. Maybe it has sth to do with my variant of gtk2. I have gtk2 @2.16.3_0+no_x11+quartz.

Attachments (1)

vte-build.txt (85.2 KB) - added by jp@… 15 years ago.

Download all attachments as: .zip

Change History (7)

Changed 15 years ago by jp@…

Attachment: vte-build.txt added

comment:1 Changed 15 years ago by mf2k (Frank Schima)

Keywords: vte removed
Port: vte added

comment:2 in reply to:  description Changed 15 years ago by jp@…

Forgot my specs:

OS X 10.5.7 Macbook Unibody (Intel) XCode 3.1.2

comment:3 Changed 15 years ago by dbevans (David B. Evans)

Resolution: invalid
Status: newclosed

Yes, gtk2 is your problem. Please deactivate the current version and build without +no_x11 +quartz. vte does not currently support these variants. This means you'll probably have to rebuild pango and cairo as well and any other dependents that use these variants.

comment:4 in reply to:  3 Changed 15 years ago by jp@…

Replying to devans@…:

vte does not currently support these variants.

I wonder if there is a way in macports to mark conflicting ports/variants. To let the user run into compilation errors doesent seem like a sound solution.

comment:5 Changed 15 years ago by dbevans (David B. Evans)

In general, the default display support in MacPorts is to use X11. variants +no_x11 +quartz in general conflict with this although some ports (gimp for instance) can be built either way.

Furthermore, if you are using +no_x11 +quartz, then for things to work properly all dependent ports have to be built with these options as well.

So if you need to build both types of ports, then it is best, IMHO, to have two separate build environments, one for X11 and one for +no_x11 +quartz in two different locations. Each can then be consistent within itself and you can select with one you want to use by selecting the proper path.

In my case, since I support ports that can be built either way, I use the default install of MacPorts to build the default ports (X11) at /opt/local and a second one installed at /opt/gtk which I use for building +no_x11 +quartz ports.

In this second instance, I set /opt/gtk/etc/macports/variants.conf to include +no_x11 +quartz so that all ports built there have these variants applied automatically. Then all dependents are sure to build correctly.

So I can build gimp in each environment and if I run /opt/local/bin/gimp it runs the X11 app and if I run /opt/gtk/bin/gimp it runs the quartz one. I can even run the two at the same time without problems.

Its a little extra setup but it makes things a easier to maintain in the long run.

See http://guide.macports.org/#installing.macports.source.multiple for details on how to do this.

Hope this helps

comment:6 Changed 15 years ago by dbevans (David B. Evans)

Keywords: +no_x11 added

Committed changes in r53294 that allow vte to build even if gtk2 is installed +no_x11. This takes advantage of an internal define X_DISPLAY_MISSING that handles this case if defined but I would consider this experimental as vte does nothing during configure to try and set this. Let me know what your results are if you build vte with gtk2 +no_x11. Has no effect if gtk2 is installed without the +no_x11 variant.

Note: See TracTickets for help on using tickets.