Re: Make install blows away startup files?

2003-03-30 Thread Kevin Brosius
Kendall Bennett wrote:
 
 
 Hi Guys,
 
 I have been mass compiling and installing multiple versions of XFree86
 onto a machine for compatibility testing (Red Hat 7.3 based, so I can use
 the GDB hacked up debugger ;-). However whenever I do a 'make install'
 from a freshly built 4.2.0, 4.2.1 or 4.3.0 (haven't done any ealier
 versions yet ;-), it always blows away something in the startup files so
 when I do a 'startx', all I get is a desktop with three console windows
 open (seems to be using twm as the window manager). If I copy all the
 files from the original Red Hat 7.3 /etc/X11 directory across, it starts
 up just fine using the GNOME desktop.
 
 Firstly, I don't know what file is being destroyed or replaced. Does
 anyone know what file is getting replaced? Secondly it seems to me that a
 'make install' should be non-destructive and should not be changing this
 file. I have not changed any of the defaults in the host.def file, so it
 seems to me that it is bug that after a make install over the top of an
 existing XFree86 install, XFree86 no longer functions the way it did
 before.
 
 Is there an option to fix this in the host.def file? If so, perhaps this
 should be the default option when doing a make install??
 
 BTW, I am using a script to symlink /usr/X11R6 and /etc/X11 for each
 version so I can switch between all versions with a simple command ;-)


Depends somewhat on how RH does X init.  You can look through startx and
xinit setup and see what's being changed.  I know on SuSE that 'make
install' breaks the KDM/xdm startup, and that they use a WINDOWMANAGER
environment variable in their X init pieces.  If you don't have that
variable set, then you'll get either no wm or twm.  But doing a source
install over your distro's install tree is really up to you to resolve.

-- 
Kevin
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


XML_SetDoctypeDeclHandler not found

2003-03-30 Thread Frank Liu
Apparently the libexpat that is included with my OS doesn't
have the function XML_SetDoctypeDeclHandler and I've got
errors like:

../../../exports/lib/libfontconfig.so: undefined reference to
`XML_SetDoctypeDeclHandler'

Can I simply comment out the `XML_SetDoctypeDeclHandler' line in
xc/lib/fontconfig/src/fcxml.c ?
Any side effects?

Thanks!
Frank

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: XFree86 host.def file questions

2003-03-30 Thread Kurt Wall
An unnamed Administration source, Kendall Bennett, wrote:
% David Dawes [EMAIL PROTECTED] wrote:
% 
%  I guess you must have read something to even know about the existence
%  of a host.def file.  I presume that it was misleading, and so should
%  be fixed.
% 
% Yes, I have the file that I printed out sitting on my desk! As it turns 
% out, it appears to be rather outdated and antiquated and I am not sure 
% exactly where I found it now. 
% 
%  I think that http://www.xfree86.org/current/BUILD.html is a
%  reasonable introduction to building XFree86, but suggestions for
%  improving that document are most welcome.  

[...]

% To solve this problem it would be great if someone added a new section to 
% the primary XFree86 web site titled something like 'Building XFree86 for 
% the first time'. It could have a paragraph describing how easy it is to 
% build XFree86, and then have a link to the BUILD.html file. If that was 
% available when I started building it again a few months back I think it 
% would have saved me a lot of time ;-)

How about: Special Edition Building XFree86 for the First Time for 
Compleat Morons in 24 Hours by Example Unleashed. ;-)

Kurt
-- 
If you push the extra ice button on the soft drink vending machine,
you won't get any ice.  If you push the no ice button, you'll get
ice, but no cup.

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: XML_SetDoctypeDeclHandler not found

2003-03-30 Thread Matthias Scheler
On Sun, Mar 30, 2003 at 03:19:14PM -0800, Frank Liu wrote:
 Apparently the libexpat that is included with my OS ...

That's your problem. XFree86 should use the bundled libexpat. Try to
find out why that doesn't work instead of patching XFree86 sources.

Kind regards

-- 
Matthias Scheler  http://scheler.de/~matthias/
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel