New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #16396 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

XFree86 warnings about X11 installs are incorrect on 10.5

Reported by: jburt@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: XRENDER Cc: ryandesign@…, jmr@…
Port:

Description


Install for XRENDER incorrectly fails to detect X11SDK is already installed. Moving X11 as suggested (in order to bypass error) does not work... still detects X11 as installed. PS... X11 is installed at /usr/X11, not at /usr/X11R6


CPU168:usr 168admin$ sudo port install xrender ---> Fetching XFree86 Error: Target org.macports.fetch returned:

You have an Apple X11 installation already.

MacPorts will not overwrite it.

If you wish to use Apple X11,

install the X11SDK included with Xcode tools.

If you really want to use XFree86 instead,

please move it aside first :

sudo mv /usr/X11R6 /usr/X11R6.apple

Error: The following dependencies failed to build: XFree86 Error: Status 1 encountered during processing.

Attachments

xfree-check.diff (523 bytes) - added by jmr@… 6 years ago.

Change History

comment:1 in reply to: ↑ description ; follow-up: ↓ 5 Changed 6 years ago by jburt@…


Edited: 20080827 11:26am

XCode Tools / X11SDK does not place a receipt in "/Library/Receipts", therefore when installer for XRENDER investigates for this receipt, it incorrectly concludes that X11SDK is not installed.

OS: MAC OS-X Leopard 10.5.4 XCODE: xcode31_2199_developerdvd.dmg, X11SDK.pkg


Replying to jburt@…:


Install for XRENDER incorrectly fails to detect X11SDK is already installed. Moving X11 as suggested (in order to bypass error) does not work... still detects X11 as installed. PS... X11 is installed at /usr/X11, not at /usr/X11R6


CPU168:usr 168admin$ sudo port install xrender ---> Fetching XFree86 Error: Target org.macports.fetch returned:

You have an Apple X11 installation already.

MacPorts will not overwrite it.

If you wish to use Apple X11,

install the X11SDK included with Xcode tools.

If you really want to use XFree86 instead,

please move it aside first :

sudo mv /usr/X11R6 /usr/X11R6.apple

Error: The following dependencies failed to build: XFree86 Error: Status 1 encountered during processing.

comment:2 Changed 6 years ago by blb@…

What is the result from running /usr/sbin/pkgutil --pkgs=X11?

comment:3 Changed 6 years ago by jburt@…

Hello,

I am glad that you wrote. In fact, I have a change to make to the report I made.

It seems that "X11" was actually not yet installed on that machine. However, MacPorts Installer said that it was. I am not sure why this erroneous report came from the installer. Based upon the installer's report, I installed "X11 SDK", however this was probably not registered because X11 was not yet installed.

After I later installed X11, MacPorts recognized that X11 SDK was installed, and proceeded with the XRENDER install.

So, it seems that the report should be changed to read:

Macports Installer for XRENDER (and others?) incorrectly reports "X11 is installed" and tells user

You have an Apple X11 installation already.

MacPorts will not overwrite it.

If you wish to use Apple X11,

install the X11SDK included with Xcode tools.

If you really want to use XFree86 instead,

please move it aside first :

When in truth.... X11 is not installed. I am not sure what MacPorts is inspecting to determine if X11 is installed, but apparently this can generate an incorrect result that X11 is installed. It tells the user to install X11SDK, which he does.. it is not registered correctly with the system because X11 is not installed. When user attempts another Macports install... it tells him once again to install X11SDK! Lol... an endless loop!

comment:4 Changed 6 years ago by blb@…

  • Summary changed from XRender Install Error to XFree86 warnings about X11 installs are incorrect on 10.5

That message comes from the XFree86 port; the paths it tests appear to be good for up to 10.4, but on 10.5 quartz-wm appears to be installed with the BSD package. Seems like the path testing needs to be further enhanced for 10.5.

comment:5 in reply to: ↑ 1 Changed 6 years ago by ryandesign@…

  • Cc ryandesign@… added

Replying to jburt@…:

XCode Tools / X11SDK does not place a receipt in "/Library/Receipts", therefore when installer for XRENDER investigates for this receipt, it incorrectly concludes that X11SDK is not installed.

The XFree86 port, which is the one printing the error message (not the xrender port), does not investigate the contents of /Library/Receipts. You can see what it does by reading the platform macosx section of the XFree86 Portfile. I have not yet evaluated it to determine whether what it does is still appropriate for Leopard, however r36950, the latest change to the port, made 3 months ago, claims to have fixed detection issues on Leopard. Are you sure your ports are up to date? Try sudo port sync, then try again.

Replying to jburt@…:

PS... X11 is installed at /usr/X11, not at /usr/X11R6

Another change made in r36950 is to use the variable ${x11prefix} in the error message instead of always showing /usr/X11R6. So either you have changed x11prefix from /usr/X11 to /usr/X11R6 in ${prefix}/etc/macports/macports.conf, or you have installed MacPorts for Tiger instead of MacPorts for Leopard, or most probably your ports are out of date (sudo port sync).

comment:6 Changed 6 years ago by jmr@…

Per blb's comment it seems that r36950 didn't have the intended effect (I just noted the changed location of quartz-wm on Leopard). Attaching a patch to check for Xquartz instead, which should work on both Tiger and Leopard.

Changed 6 years ago by jmr@…

comment:7 Changed 6 years ago by blb@…

Xquartz looks like a good choice; grepping on 10.4 and pkgutil on 10.5 show it to be owned by X11User (and updates), and of course the xquartz package if you install that for the newer X11.

comment:8 Changed 6 years ago by jmr@…

  • Cc jmr@… added
  • Status changed from new to closed
  • Resolution set to fixed

Committed the patch in r39668.

comment:9 Changed 6 years ago by anonymous

  • Milestone Port Bugs deleted

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.