Hi, I've ripped out Xprint from the xorg ports on the 2.4 branch. There's (at least) one port that depends on libXp though, which is Xaw3d. The following stupid patch makes it work (ie, Xaw3d doesn't actually need libXp. I confirmed it using opt/gv) xmkmf + sed -i -e 's/^EXTRAXAWREQS =.*/EXTRAXAWREQS=/' Makefile make -j1 However, I have no idea how Xprint even gets pulled in - I don't see any reference in the Imakefile. Does anybody care enough to look into this? Otherwise I suggest to go with the before mentioned lame method to rip out Xprint :) Please note that commits related to the Xprint removal should go on opt's 2.4 branch, which doesn't exist yet. Feel free to poke me to get it branched off when the need arises :) Thanks, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
On Thu, Sep 06, 2007 at 09:52:10PM +0200, Tilman Sauerbeck wrote:
Hi,
Hi Tilman,
I've ripped out Xprint from the xorg ports on the 2.4 branch.
There's (at least) one port that depends on libXp though, which is Xaw3d.
The following stupid patch makes it work (ie, Xaw3d doesn't actually need libXp. I confirmed it using opt/gv)
xmkmf + sed -i -e 's/^EXTRAXAWREQS =.*/EXTRAXAWREQS=/' Makefile make -j1
However, I have no idea how Xprint even gets pulled in - I don't see any reference in the Imakefile.
So this is triggered by some wrong X configuration stuff? IMHO we should find the reason, because other progs might break as well.
Does anybody care enough to look into this? Otherwise I suggest to go with the before mentioned lame method to rip out Xprint :)
changing the make call to make -j1 XPLIB='' should do the job as well, at least libXaw3d is no longer linked against LibXp here. But that's with CRUX 2.3, because I havn't had the time to build X for 2.4. I guess it works with 2.4 too? Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
Juergen Daubert [2007-09-07 13:06]:
On Thu, Sep 06, 2007 at 09:52:10PM +0200, Tilman Sauerbeck wrote:
I've ripped out Xprint from the xorg ports on the 2.4 branch.
There's (at least) one port that depends on libXp though, which is Xaw3d.
The following stupid patch makes it work (ie, Xaw3d doesn't actually need libXp. I confirmed it using opt/gv)
xmkmf + sed -i -e 's/^EXTRAXAWREQS =.*/EXTRAXAWREQS=/' Makefile make -j1
However, I have no idea how Xprint even gets pulled in - I don't see any reference in the Imakefile.
So this is triggered by some wrong X configuration stuff? IMHO we should find the reason, because other progs might break as well.
It's probably some file from xorg-cf-files that pulls it in. So far I've only found out that defining "BuildXprint" to NO in /usr/lib/X11/config/X11.tmpl doesn't help ;) Yes, other packages that rely on imake may break, too. IIRC KDE still uses imake...
Does anybody care enough to look into this? Otherwise I suggest to go with the before mentioned lame method to rip out Xprint :)
changing the make call to
make -j1 XPLIB=''
should do the job as well, at least libXaw3d is no longer linked against LibXp here. But that's with CRUX 2.3, because I havn't had the time to build X for 2.4. I guess it works with 2.4 too?
Hehe. Yes, overriding XPLIB will work as well. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
participants (2)
-
Juergen Daubert -
Tilman Sauerbeck