#12234 closed defect (worksforme)
BUG: xrender configures incorrectly (causing failing build)
| Reported by: | tyler@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: |
Description
The xrender package is a tiny dependency for Xft2, which is in turn a dependency for gtk#, which in turn, is one of the dependencies for some of the Mono development I'm doing. The arguments that are passed into the autoconf process for building xrender are woefully incorrect, so you'll need to configure it yourself (presumably after MacPorts fails to build it) and then let MacPorts rebuild it. The progression is something like this:
- sudo port install xrender (this will probably fail)
- cd $MP_PREFIX/var/db/dports/sources/rsync.rsync.darwinports.org_dpupdate_dports/x11/xrender/work/libXrender-0.9.0
- sudo ./configure --prefix=$MP_PREFIX
- sudo port install xrender (this will probably work)
I currently am working through figuring out the blasted build system to correct this.
Change History (3)
comment:1 Changed 17 years ago by nox@…
| Milestone: | → Port Bugs |
|---|---|
| Priority: | Expected → Normal |
| Summary: | xrender configures incorrectly (causing failing build) → BUG: xrender configures incorrectly (causing failing build) |
| Version: | 1.4.40 |
comment:2 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
MacPorts has no trouble installing xrender for me, on Mac OS X 10.4.11 Intel with Xcode 2.4.1 and MacPorts built from trunk. Please "
sudo port selfupdate" and "sudo port clean --work xrender" and try again. If you still get the problem, please reopen this bug, and tell us your version of Mac OS X, Xcode, MacPorts, your processor architecture, and please paste in the error message you get from "sudo port install xrender"