How to disable Ctrl+Alt+Backspace in tinyx

2003-12-10 Thread Gal Yahel
Hello,

do you know how to disable the Ctrl+Alt+Backspace in tinyx.
I know that in full x server I have to change the XF86Config file but
the tinyx (Xfbdev) does not need the XF86Config file.

How Can disable Ctrl+Alt+Backspace in tinyx without the config file?

thanks in advance.

Gal Yahel

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


Re: s3 trio64, color depth problem (see also bug #465)

2003-12-10 Thread steven mestdagh
i have already tried that, but it doesn't help (still the blank screen).

steven.


 maybe try depth 15 rather than 16... as I recall some old cards could
 only do one or the other.  I'm no expert though.
 
 Alex
 
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


State of radeon driver

2003-12-10 Thread tacorner
I have installed xfree86 4.4.0 rc1 on my laptop (an acer 1455LMi_ATI, with an
AMD 600+cou, 512MB ram, and rdeon 9200 graphics).  I am getting about 1000FPS
on glxgears.  I would expect more.  Also there are some glitches( hesitations,
and uneven display).  What is the state of the driver?  Is there a common
source of patches/future versions of it available.  I would like to be able to
track progress on the driver and install new versions without redoing all of
xfree86 which is a minor pain.

Thanks,

Tom Corner

---
|\/\/\___/\/\/| Carol Anne Corner 
\ o o / Thomas Corner [EMAIL PROTECTED]
 )   ( 10-Dec-2003 12:15:44  Vienna,  Austria
( * * )   mailer: xfmail
 \___/ Web Page: www.corner.chello.at
---
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: State of radeon driver

2003-12-10 Thread wim delvaux
Any idea whether what support 4.4.0 will have from the Radeo 9600 Pro ? 

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


Re: State of radeon driver

2003-12-10 Thread wim delvaux
On Wednesday 10 December 2003 12:48, wim delvaux wrote:
 Any idea whether what support 4.4.0 will have from the Radeo 9600 Pro ?

And now in English ;-(

Any idea what support 4.4.0 will have for the Radeo 9600 Pro ?


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

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


Re: State of radeon driver

2003-12-10 Thread Torgeir Veimo
On Wed, 2003-12-10 at 11:55, wim delvaux wrote:
 On Wednesday 10 December 2003 12:48, wim delvaux wrote:
  Any idea whether what support 4.4.0 will have from the Radeo 9600 Pro ?
 
   And now in English ;-(
 
   Any idea what support 4.4.0 will have for the Radeo 9600 Pro ?

ATI haven't released any databooks about newer GPUs like R300  R350, so
there's currently no 3D acceleration for these cards (9600, 9800 etc)
yet.






To the administrator; could the separator above the Devel mailing list
be changed to be only -- , so that quoting when replying automatically
removes that signature, when using compliant mailers.

  ___
  Devel mailing list

-- 
Torgeir Veimo [EMAIL PROTECTED]

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


RE: State of radeon driver

2003-12-10 Thread Alexander Stohr
the _ is the mailmain default but can be canged.

only the fglrx closed source drivers from ATI 
for the i386/Linux platform do have 3D.

Databooks are no longer state of the art 
in the information technologies age.

  On Wednesday 10 December 2003 12:48, wim delvaux wrote:
   Any idea whether what support 4.4.0 will have from the 
 Radeo 9600 Pro ?
  
  And now in English ;-(
  
  Any idea what support 4.4.0 will have for the Radeo 9600 Pro ?
 
 ATI haven't released any databooks about newer GPUs like R300 
  R350, so
 there's currently no 3D acceleration for these cards (9600, 9800 etc)
 yet.
 
 To the administrator; could the separator above the Devel 
 mailing list
 be changed to be only -- , so that quoting when replying 
 automatically
 removes that signature, when using compliant mailers.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


of manpages and names

2003-12-10 Thread Warren Turkal
I was wondering if it is possible to get manpages to be named slightly
different than default without major surgery. I will illustrate what I want
with an example.

Say I have a manpage xterm.man.

It gets generated as xterm.1 stored in the $(INSTALL_DIR)/man/man1.

I want to change the generated file to be xterm.1x instead.

How would one accomplish this? Is there some Imake #define that can be set?

Thanks a lot, wt
-- 
Warren Turkal
President, GOLUM, Inc.
http://www.golum.org

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


Re: State of radeon driver

2003-12-10 Thread wim delvaux
On Wednesday 10 December 2003 13:09, Alexander Stohr wrote:
 the _ is the mailmain default but can be canged.

 only the fglrx closed source drivers from ATI
 for the i386/Linux platform do have 3D.

 Databooks are no longer state of the art
 in the information technologies age.

I have tried these drivers but refuse to work.
They think I have an (unsupported) OEM card (=powered by ATI)
while according to the identity check programs
run under XP it 'should' be an ATI one (=Built by ATI)

(phoned to medion - who makes the card - and they claimed
 that ATI built the card for them ???)

Any idea when the data-e-book will be available ;-)

W


   On Wednesday 10 December 2003 12:48, wim delvaux wrote:
Any idea whether what support 4.4.0 will have from the
 
  Radeo 9600 Pro ?
 
 And now in English ;-(
  
 Any idea what support 4.4.0 will have for the Radeo 9600 Pro ?
 
  ATI haven't released any databooks about newer GPUs like R300
   R350, so
  there's currently no 3D acceleration for these cards (9600, 9800 etc)
  yet.
 
  To the administrator; could the separator above the Devel
  mailing list
  be changed to be only -- , so that quoting when replying
  automatically
  removes that signature, when using compliant mailers.

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

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


RE: State of radeon driver

2003-12-10 Thread Alexander Stohr
   I have tried these drivers but refuse to work.
   They think I have an (unsupported) OEM card (=powered by ATI)
   while according to the identity check programs
   run under XP it 'should' be an ATI one (=Built by ATI)

There is no general OEM barrier anymore. 
It only was it was in early days where no one was sure 
if drivers would work well on those boards.

It would be kind if you can you retry this test
with latest fglrx drivers and mail me the results
in private or public, just as you want.

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


Re: State of radeon driver

2003-12-10 Thread Torgeir Veimo
On Wed, 2003-12-10 at 12:26, wim delvaux wrote:
 On Wednesday 10 December 2003 13:09, Alexander Stohr wrote:
  the _ is the mailmain default but can be canged.
 
  only the fglrx closed source drivers from ATI
  for the i386/Linux platform do have 3D.
 
  Databooks are no longer state of the art
  in the information technologies age.
 
   I have tried these drivers but refuse to work.
   They think I have an (unsupported) OEM card (=powered by ATI)
   while according to the identity check programs
   run under XP it 'should' be an ATI one (=Built by ATI)
   
   (phoned to medion - who makes the card - and they claimed
  that ATI built the card for them ???)
 
   Any idea when the data-e-book will be available ;-)

Well, probably not until a certain place in norway freezes over..

-- 
Torgeir Veimo [EMAIL PROTECTED]

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


Re: State of radeon driver

2003-12-10 Thread wim delvaux
On Wednesday 10 December 2003 13:44, Alexander Stohr wrote:
  I have tried these drivers but refuse to work.
  They think I have an (unsupported) OEM card (=powered by ATI)
  while according to the identity check programs
  run under XP it 'should' be an ATI one (=Built by ATI)

 There is no general OEM barrier anymore.
 It only was it was in early days where no one was sure
 if drivers would work well on those boards.

 It would be kind if you can you retry this test
 with latest fglrx drivers and mail me the results
 in private or public, just as you want.

Sure with pleasure ... where can I download the 'lastest' drivers ?

W

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

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


Re: External FreeType build problem

2003-12-10 Thread Grzegorz Nieweglowski
David Dawes wrote:
 The patch is necessary for building against freetype 2.1.7, because
 changes in header file names were hidden behind these macros.

BTW, what is this freetype-2.1.7 I keep reading about?

Isn't freetype hosted on SourceForge anymore? The latest version I see
there is 2.1.5. The freetype project moved somewhere else?

 My first question is, do you have a clean 4.3.99.901 tree?

Yup.

 The next question is, is '-I/usr/include -I/usr/include/freetype2' on
 the gcc command lines as it should be?

Yes it is.

 Can you send the actual build log extract for the failing part?

Sure:

#v+
rm -f ftfuncs.o unshared/ftfuncs.o
gcc -c -I/usr/include -I/usr/include/freetype2 -I. -I../../../include/fonts 
-I../include -I../../../exports/include/X11 -I../../../programs/Xserver/include 
-I../../../extras/freetype2/src/truetype -I../../../exports/include -I../../.. 
-I../../../exports/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L 
-D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE 
-DFUNCPROTO=15 -DNARROWPROTO -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH 
-DXvExtension -DXFree86Server -DXF86VIDMODE -DSMART_SCHEDULE 
-DX_BYTE_ORDER=X_LITTLE_ENDIAN -DXFREE86_FT2 -march=pentium2 -Os -fomit-frame-pointer 
-s -pipe -DNDEBUG -DG_DISABLE_ASSERT -s -z combreloc ftfuncs.c
ftfuncs.c:46:10: #include expects FILENAME or FILENAME
ftfuncs.c:47:10: #include expects FILENAME or FILENAME

[... CUT! Nearly 600 lines ...]

make: *** [ftfuncs.o] Bd 1
#v-

 Also, check the depend stuff in the Makefile that gets created to
 see which ft2build.h file it thinks is getting used.

After grep ft2build Makefile:

ftfuncs.o: ../include/fontutil.h /usr/include/ft2build.h
ftenc.o: ../include/fontutil.h ../include/fontenc.h /usr/include/ft2build.h
fttools.o: /usr/include/ft2build.h

If I replace the '#include ft2build.h' in ftfuncs.c with

#include /usr/include/ft2build.h

then it builds well. But if I leave the default '#include ft2build.h'
it fails.

But I think I know what's wrong. The gcc manual says:

Directories named by -I are searched before the standard system include
directories.

So system directories, like /usr/include, have *lowest* priorities.
Anything blessed with -I will be checked first. It gets even worse:

(...) If the directory dir is a standard system include directory, the
option (this means -I) is ignored

So you can't do anything about it. The *only* way of solving this
would be rearranging xc's includes. If you want gcc to use
/usr/include/ft2build.h you need to make sure that gcc gets absolutely
no -I pointing to a directory with a second ft2build.h in it.

This isn't good, is it? It's not only freetype, it can probably happen
to expat, fontconfig etc.

Oh, and the troublemaking ft2build.h is, in this case, located in the
xc/lib/font/FreeType directory (-I .) Once you remove it, it all works.
And now I understand why. Well, this means that to ensure gcc3
compatibility the included external parts, like expat or freetype, would
need to be completely isolated from the build process. gcc should not be
allowed to learn about those includes unless they are really needed.
'cause if gcc finds them, it will use them instead of /usr/include.

 If you can figure out what the problem is and send a patch for it,
 that would be most welcome.  It has to work with older versions of
 flex, as well as lex too.

Someone with flexperience would be needed...

On my config this does nicely:

--- xc/programs/twm/lex.c   2003-12-10 17:10:27.0 +0100
+++ xc/programs/twm/lex.c.new   2003-12-10 17:10:47.0 +0100
@@ -25,6 +25,8 @@
 
 /* flex integer type definitions */
 
+int yy_prev_more_offset;
+
 #ifndef FLEXINT_H
 #define FLEXINT_H

But it's just a quickdirty hack if someone (like me) is just interested
in getting a XFree86 release to compile.

I looked a bit at it, and it seems that flex, at least my flex-2.5.31,
uses a /usr/include/FlexLexer.h header. I guess this header needs to be
included in every flexed C source. However, greping twm for FlexLexer
yields no results.

But twm/lex.c already includes many, many definitions from FlexLexer.h
(some are still missing, like yy_prev_more_offset). I don't know the
history of flex - this /usr/include/FlexLexer.h is either something
really new, or someone embedded an older FlexLexer.h file in twm sources
long ago (which would explain why there are so many parts of FlexLexer.h
in it).

A good fix would be to kick redundand definitions out of twm/lex.c and
put a #include FlexLexer.h there instead. But I don't know if it
wouldn't break compatibility with older versions of flex or lex. I never
used flex, so I don't know how to solve this.


Argh, I don't like it. Two problems and I can't fix even a single one.
Oh well, maybe someone else will.

-- 
\hoppke
(Grzegorz Grayna Niewgowski)
http://lubuska.zapto.org/~hoppke/
___
Devel mailing list
[EMAIL PROTECTED]

Re: External FreeType build problem

2003-12-10 Thread Alan Coopersmith
Grzegorz Nieweglowski wrote:
David Dawes wrote:

The patch is necessary for building against freetype 2.1.7, because
changes in header file names were hidden behind these macros.


BTW, what is this freetype-2.1.7 I keep reading about?

Isn't freetype hosted on SourceForge anymore? The latest version I see
there is 2.1.5. The freetype project moved somewhere else?
For some reason they've put 2.1.7 on their ftp site, but not on the
sourceforge download page.  You can find it at 
ftp://ftp.freetype.org/freetype/freetype2/

--
-Alan Coopersmith- [EMAIL PROTECTED]
 Sun Microsystems, Inc.- Sun Software Group
 User Experience Engineering: G11N: X Window System
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: XFree86 4.4.0 RC1

2003-12-10 Thread David Dawes
On Wed, Dec 10, 2003 at 02:04:47PM +1000, [EMAIL PROTECTED] wrote:

Further to my previous email,  the results of a build with Glx give the
following errors:

rm -f mmx_blend.i
/usr/ccs/lib/cpp -Dsun -Di386 -DSVR4 -D__EXTENSIONS__ -D__i386
-DMALLOC_0_RETURNS_NULL -DGLXEXT  -DGLX_USE_MESA  -DUSE_X86_ASM
-DUSE_MMX_ASM   -I../../../../../exports/include
-I../../../../../include/extensions -I../../../../../extras/Mesa/src
-I../../../../../extras/Mesa/src/X86-I../../../include
mmx_blend.S | \
grep -v '^\#'  mmx_blend.i
rm -f mmx_blend.o
gcc -c -x assembler -o mmx_blend.o mmx_blend.i
Assembler:
aline 1403  : Illegal mnemonic
aline 1403  : syntax error
aline 1403  : Illegal register
aline 1403  : Illegal register
aline 1414  : Illegal mnemonic
aline 1414  : syntax error
aline 1414  : Illegal register
aline 1414  : Illegal mnemonic
aline 1414  : syntax error
aline 1414  : Illegal register
aline 1414  : Illegal mnemonic
aline 1414  : syntax error
aline 1414  : Illegal register
aline 1414  : Illegal register
aline 1414  : Illegal mnemonic
aline 1414  : syntax error
aline 1414  : Illegal register
aline 1414  : Illegal register
aline 1414  : Illegal mnemonic
aline 1414  : syntax error
aline 1414  : Illegal register
aline 1414  : Illegal register
aline 1414  : Illegal mnemonic
aline 1414  : syntax error
aline 1414  : Illegal register
aline 1414  : Illegal register
aline 1414  : Illegal mnemonic
aline 1414  : syntax error
aline 1414  : Illegal register
aline 1414  : Illegal register
aline 1414  : Illegal mnemonic
Too many errors - Goodbye
*** Error code 1
make: Fatal error: Command failed for target `mmx_blend.o'
Current working directory
/proj3/ere/work/lindsayh/XFree86/xc/lib/GL/mesa/src/X86

The assembler in 2.5.1 probably doesn't support the MMX instructions.
The solution is to make sure HasMMXSupport is set to NO for versions older
than 2.6 in sun.cf.

The entire file is attached.  Maybe it is something to do with the use of
/usr/ccs/lib/cpp??  David, what did your test builds on 2.6 - 8 use to
generate mmx_blend.i?

The mmx_blend.i I get looks like yours.  The difference is that the
assembler on 2.6 (and later) understands these instructions.

David
-- 
David Dawes
developer/release engineer  The XFree86 Project
www.XFree86.org/~dawes
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: External FreeType build problem

2003-12-10 Thread David Dawes
On Wed, Dec 10, 2003 at 06:06:31PM +0100, Grzegorz Nieweglowski wrote:
David Dawes wrote:
 The patch is necessary for building against freetype 2.1.7, because
 changes in header file names were hidden behind these macros.

BTW, what is this freetype-2.1.7 I keep reading about?

Isn't freetype hosted on SourceForge anymore? The latest version I see
there is 2.1.5. The freetype project moved somewhere else?

You can find it if you go to the freetype.org ftp site in France.  I
didn't see tarballs on the SourceForge site either.

 My first question is, do you have a clean 4.3.99.901 tree?

Yup.

 The next question is, is '-I/usr/include -I/usr/include/freetype2' on
 the gcc command lines as it should be?

Yes it is.

 Can you send the actual build log extract for the failing part?

Sure:

#v+
rm -f ftfuncs.o unshared/ftfuncs.o
gcc -c -I/usr/include -I/usr/include/freetype2 -I. -I../../../include/fonts 
-I../include -I../../../exports/include/X11 -I../../../programs/Xserver/include 
-I../../../extras/freetype2/src/truetype -I../../../exports/include -I../../.. 
-I../../../exports/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L 
-D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE 
-DFUNCPROTO=15 -DNARROWPROTO -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH 
-DXvExtension -DXFree86Server -DXF86VIDMODE -DSMART_SCHEDULE 
-DX_BYTE_ORDER=X_LITTLE_ENDIAN -DXFREE86_FT2 -march=pentium2 -Os -fomit-frame-pointer 
-s -pipe -DNDEBUG -DG_DISABLE_ASSERT -s -z combreloc ftfuncs.c
ftfuncs.c:46:10: #include expects FILENAME or FILENAME
ftfuncs.c:47:10: #include expects FILENAME or FILENAME

   [... CUT! Nearly 600 lines ...]

make: *** [ftfuncs.o] Blad 1
#v-

 Also, check the depend stuff in the Makefile that gets created to
 see which ft2build.h file it thinks is getting used.

After grep ft2build Makefile:

ftfuncs.o: ../include/fontutil.h /usr/include/ft2build.h
ftenc.o: ../include/fontutil.h ../include/fontenc.h /usr/include/ft2build.h
fttools.o: /usr/include/ft2build.h

If I replace the '#include ft2build.h' in ftfuncs.c with

#include /usr/include/ft2build.h

then it builds well. But if I leave the default '#include ft2build.h'
it fails.

But I think I know what's wrong. The gcc manual says:

Directories named by -I are searched before the standard system include
directories.

So system directories, like /usr/include, have *lowest* priorities.
Anything blessed with -I will be checked first. It gets even worse:

(...) If the directory dir is a standard system include directory, the
option (this means -I) is ignored

Do the gcc people give a reason for not allowing a system directory to
be blessed with -I?  Maybe adding -nostdinc would help, but that would
probably have unwanted side-effects.

So you can't do anything about it. The *only* way of solving this
would be rearranging xc's includes. If you want gcc to use
/usr/include/ft2build.h you need to make sure that gcc gets absolutely
no -I pointing to a directory with a second ft2build.h in it.

This isn't good, is it? It's not only freetype, it can probably happen
to expat, fontconfig etc.

Oh, and the troublemaking ft2build.h is, in this case, located in the
xc/lib/font/FreeType directory (-I .) Once you remove it, it all works.
And now I understand why. Well, this means that to ensure gcc3
compatibility the included external parts, like expat or freetype, would
need to be completely isolated from the build process. gcc should not be
allowed to learn about those includes unless they are really needed.
'cause if gcc finds them, it will use them instead of /usr/include.

There is no ft2build.h in the xc/lib/font/FreeType directory in 4.3.99.901
(it got moved to the only place that uses it: xc/lib/font/FreeType/module).
That's why I asked if your 4.3.99.901 source was clean :-)  I did see this
problem myself before moving it.

 If you can figure out what the problem is and send a patch for it,
 that would be most welcome.  It has to work with older versions of
 flex, as well as lex too.

Someone with flexperience would be needed...

On my config this does nicely:

--- xc/programs/twm/lex.c  2003-12-10 17:10:27.0 +0100
+++ xc/programs/twm/lex.c.new  2003-12-10 17:10:47.0 +0100
@@ -25,6 +25,8 @@
 
 /* flex integer type definitions */
 
+int yy_prev_more_offset;
+
 #ifndef FLEXINT_H
 #define FLEXINT_H

But it's just a quickdirty hack if someone (like me) is just interested
in getting a XFree86 release to compile.

I looked a bit at it, and it seems that flex, at least my flex-2.5.31,
uses a /usr/include/FlexLexer.h header. I guess this header needs to be
included in every flexed C source. However, greping twm for FlexLexer
yields no results.

On the FreeBSD 4.x system I'm using right now (which has flex 2.5.4),
the only place on the system that FlexLexer.h is installed is
/usr/include/g++/ !

But twm/lex.c already includes many, many definitions from FlexLexer.h
(some are still missing, like yy_prev_more_offset). I 

Re: External FreeType build problem

2003-12-10 Thread Grzegorz Nieweglowski
David Dawes nawypisowywa(a):
 You can find it if you go to the freetype.org ftp site in France.
 I didn't see tarballs on the SourceForge site either.

Oh, thanks! But that's strange, SourceForge doesn't know about the
newest release, even official freetype mirrors are very out of date...
it's like they're hiding it from the public...

(...) If the directory dir is a standard system include directory, the
option (this means -I) is ignored
 
 Do the gcc people give a reason for not allowing a system directory to
 be blessed with -I?

I wouldn't call it a reason, but the manual puts it like this:

(...) the option is ignored to ensure that the default search order for
system directories and the special treatment of system headers are not
defeated.

 There is no ft2build.h in the xc/lib/font/FreeType directory in
 4.3.99.901 (it got moved to the only place that uses it:
 xc/lib/font/FreeType/module).  That's why I asked if your 4.3.99.901
 source was clean :-)  I did see this problem myself before moving
 it.

But... but my tree is clean. It just isn't a pure 4.3.99.901 tarball,
because some time ago I've downloaded 4.3.99.14 and then gradually
patched it up. But all I did was unpack the archive, apply the newest
patch and repack it. I tried not to break anything, really :)

I know that not all changes can be registered by diff (and reproduced by
patch) but I expected it only to affect non-textual files, like
some images or maybe binary fonts. Diffpatch are pretty reliable when
it comes to creating/removing text files, at least that's my impression.

But I guess you'd need to use the '-N' diff option to get that behavior
(at least with GNU diff), and the official patches don't do that, they
only use -u. Is the -N something available only with some special
versions of diff? Or would it be possible to generate future patches
with -uN ?

 If there's a reliable way of knowing when to include FlexLexer.h,
 then we probably should include it.

I've just noticed that my FlexLexer.h requires iostream and maybe some
more C++ parts. Maybe that was the reason for merging parts of it into
twm - to avoid the dependencies on a C++ compiler? If you would include
this header, you would probably need something like g++ to compile twm.
Not very nice, is it now. So maybe it would be easier to just play along
and keep it the way it is now... just patch twm up a bit so that it
compiles with older and newer flex releases... Would my, ekhm, patch
cause trouble with older flex versions?

-- 
\hoppke
(Grzegorz Grayna Niewgowski)
http://lubuska.zapto.org/~hoppke/
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: of manpages and names

2003-12-10 Thread Thomas Dickey
On Wed, 10 Dec 2003, Warren Turkal wrote:

 I was wondering if it is possible to get manpages to be named slightly
 different than default without major surgery. I will illustrate what I want
 with an example.

 Say I have a manpage xterm.man.

 It gets generated as xterm.1 stored in the $(INSTALL_DIR)/man/man1.

 I want to change the generated file to be xterm.1x instead.

 How would one accomplish this? Is there some Imake #define that can be set?

That's ManSuffix, which is set in several files under config/cf

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: of manpages and names

2003-12-10 Thread Raymond Jennings
X11 manpages are stored in /usr/X11R6/man/manx/whatever, not 
/usr/share/man/..., so filename clashes are not likely.

If you change a filename, be sure to change the whatis database (or whatever 
it is that man uses to determine the manpage for a given command) too.




From: Thomas Dickey [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: of manpages and names
Date: Wed, 10 Dec 2003 15:15:29 -0500 (EST)
On Wed, 10 Dec 2003, Warren Turkal wrote:

 I was wondering if it is possible to get manpages to be named slightly
 different than default without major surgery. I will illustrate what I 
want
 with an example.

 Say I have a manpage xterm.man.

 It gets generated as xterm.1 stored in the $(INSTALL_DIR)/man/man1.

 I want to change the generated file to be xterm.1x instead.

 How would one accomplish this? Is there some Imake #define that can be 
set?

That's ManSuffix, which is set in several files under config/cf

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
_
Winterize your home with tips from MSN House  Home. 
http://special.msn.com/home/warmhome.armx

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


Re: hi

2003-12-10 Thread Raymond Jennings
Foreign messages have come to me at least 4 times in the last month or so, 
definitely more than a couple a year.

You say that foreign language posts are off topic and shouldn't be made at 
all, while someone else said they can't be helped due to XFree86's 
international nature, but should in fact be welcomed...go figure.

I guess the foreign posts should be ignored by the english sector, and let 
the foreign guys worry about it.

I recently got a warning from the post master for relaying a volunteer 
request by X.org, and it definitely let me know I was in the wrong...perhaps 
the postmaster could contact other spammers and give them the same one-two 
that I got.  IMHO, this would put a stop to the advertisements.
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: hi Date: Mon, 08 Dec 2003 14:12:14 -0800
 I speak spanish and that seems to say something about your mother, big 
cow

 I hope I'm mistaken because that sounds rather rude.

 By the way, this is the 3rd foreign message I've received in the last 
week.
 I made a post about an automatic translation filter that checks the 
country
 domain; I'd really like to see it implemented.  I've heard of babelfish.

What would be the point?  Almost all of the foreign language messages to
this list are SPAM.  In fact, this one would conflict with your recent
request to limit profanity.  The foreign language messages are OFF-TOPIC
and don't belong at all.
It would be alot of work to install such a filter, even if one did exist,
just for one or two messages a year.  When those very rare messages do
occur, there are enough people on the list who speak other languages that
can either respond or provide a translation if needed.  If you see a non-
English message on this list, you can safely assume it is SPAM, unless
proven otherwise.
BTW, this message does reference your mother, but according to it,
the big cow is your wife (she's also a whore among other things).
I won't go into what it tells you to do to yourself.


 From: luca bettati [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Re: hi
 Date: Fri, 05 Dec 2003 18:39:42 +0100
 
 hai rotto il cazzo: tè, tua madre e quella gran vacca, zoccola, puttana 
e
 troia di tua moglie!
 vatti a farti fottere figlio di PUTTANA
 
 
 ___
 Devel mailing list
 [EMAIL PROTECTED]
 http://XFree86.Org/mailman/listinfo/devel

 _
 Get holiday tips for festive fun.
 http://special.msn.com/network/happyholidays.armx

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


___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
_
Shop online for kids’ toys by age group, price range, and toy category at 
MSN Shopping. No waiting for a clerk to help you! http://shopping.msn.com

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


Re: GeForce 4 Ti 4200 on Dell Inspiron 8500 (Filter no 20311056)

2003-12-10 Thread Raymond Jennings
So this bug is in recent versions too? not just stoneware?

In that case, I shall be posting to bugzilla.
From: Mark Vojkovich [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: GeForce 4 Ti 4200 on Dell Inspiron 8500
Date: Mon, 8 Dec 2003 14:39:02 -0800 (PST)
On Mon, 8 Dec 2003, Raymond Jennings wrote:

 That's funny, I had the same problem, only I have a Diamond Stealth II 
S220
 and use the generic SVGA server.  Whenever I switch to text mode and
 ESPECIALLY if I had a virtual resolution, it seems as if the video card
 isn't beginning the text scans at the right place, it's as if someone
 scrolled the text display over to the right by a character, and this 
is
 confusing because the cursor is correctly placed.  If I type a few
 characters the text mode display jumps back to where it should have been 
in
 the first place.

 Whatever code is responsible for restoring text mode is messing up big 
time.
   Is this the kernel, or does the X server handle switches back to text
 mode?

 Similar problems on different architectures suggest that this fault is 
in
 global code.

   The driver is responsible for restoring the text mode.  It is
the XFree86 driver's fault alone when the text mode is not properly
restored.
			Mark.



 From: Mark Vojkovich [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 To: Christophe Jacquet [EMAIL PROTECTED]
 CC: [EMAIL PROTECTED]
 Subject: Re: GeForce 4 Ti 4200 on Dell Inspiron 8500
 Date: Sun, 7 Dec 2003 13:07:32 -0800 (PST)
 
 On Sun, 7 Dec 2003, Christophe Jacquet wrote:
  
  
3) When I switch back from graphics mode to text mode, the text 
display
   is messed up: the display is not correctly centered, one pixel out 
of
   two remains off, and horizontal lines appear when some text is 
printed
   on the last line.
  
 
 Did it used to work?  I've never had one of these laptops myself
 so I've never tested on one.
 
 Does hitting the Font key fix it up again?
 
 
 			Mark.
 

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
_
Get holiday tips for festive fun. 
http://special.msn.com/network/happyholidays.armx

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


Re: State of radeon driver

2003-12-10 Thread Gerhard W. Gruber
On Wed, 10 Dec 2003 14:47:27 +0100, wim delvaux
[EMAIL PROTECTED] wrote:

I haven't seen this posting. ???

 There is no general OEM barrier anymore.
 It only was it was in early days where no one was sure
 if drivers would work well on those boards.

 It would be kind if you can you retry this test
 with latest fglrx drivers and mail me the results
 in private or public, just as you want.

   Sure with pleasure ... where can I download the 'lastest' drivers ?

Which drivers are we talking about here? I have also the problem that I can't
get my 3D acceleration not to work with an ASUS 9800XT, but I have XFree86
4.3.0.


-- 
Gerhard Gruber
Maintainer of
SoftICE for Linux - http://sourceforge.net/projects/pice
Fast application launcher - http://sourceforge.net/projects/launchmenu

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


Re: XServer kills console

2003-12-10 Thread David Gmez
Hi,

On Dec 10 at 08:59:20, Raymond Jennings wrote:
 If you're using xinit, the xterm is the session, killing it causes the X 
 server to exit.

I know, but i'm launching X with /usr/X11R6/bin/X, not xinit.

 If your console dies, then something screwy is going on.  Try the VT 
 switching keys.

No vt keys, no ctrl-alt-backspace, the console keyboard is definetely dead.

I tried to repeat this bug with XFree86 4.2, but it seems it only happens
with 4.3.0.

cheers

-- 
David Gómez

The question of whether computers can think is just like the question of
whether submarines can swim. -- Edsger W. Dijkstra
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: of manpages and names

2003-12-10 Thread Warren Turkal
Thomas Dickey wrote:
 That's ManSuffix, which is set in several files under config/cf

Thanks very much.

wt
-- 
Warren Turkal
President, GOLUM, Inc.
http://www.golum.org

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


Re: State of radeon driver

2003-12-10 Thread wim delvaux
On Wednesday 10 December 2003 22:47, Gerhard W. Gruber wrote:
 On Wed, 10 Dec 2003 14:47:27 +0100, wim delvaux
 [EMAIL PROTECTED] wrote:

 I haven't seen this posting. ???

  There is no general OEM barrier anymore.
  It only was it was in early days where no one was sure
  if drivers would work well on those boards.
 
  It would be kind if you can you retry this test
  with latest fglrx drivers and mail me the results
  in private or public, just as you want.
 
  Sure with pleasure ... where can I download the 'lastest' drivers ?

 Which drivers are we talking about here? I have also the problem that I
 can't get my 3D acceleration not to work with an ASUS 9800XT, but I have
 XFree86 4.3.0.

The closed source drivers on the ATI website

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


Re: State of radeon driver

2003-12-10 Thread Gerhard W. Gruber
On Thu, 11 Dec 2003 00:39:57 +0100, wim delvaux
[EMAIL PROTECTED] wrote:

The closed source drivers on the ATI website

I tried them, but no success. But I think the problem is with KDE/OpenGL
because I managed to get at least the Desktop with Mesa working. Only when I
try to activate the ATI provided OpenGL lib I can't start X/KDE anymore.

-- 
Gerhard Gruber
Maintainer of
SoftICE for Linux - http://sourceforge.net/projects/pice
Fast application launcher - http://sourceforge.net/projects/launchmenu

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


[PATCH] documentation fix addition for config/cf/README

2003-12-10 Thread Warren Turkal
I moved the GzipCmd to get it in alphabetical order. I also added
documentation for DriverManSuffix.

wt

--- README.old  2003-12-10 20:33:23.0 -0600
+++ README  2003-12-10 20:35:31.0 -0600
@@ -25,7 +25,6 @@
CURDIR  current directory relative to top of sources
CcCmd   command to run C compiler
CompressCmd command to run compress program
-   GzipCmd command to run gzip program
ConstructMFLAGS System V option to set MFLAGS make variable
CpCmd   command to copy one file to another
CplusplusCmdcommand to run C++ compiler
@@ -50,6 +49,7 @@
FortranCmd  command to run Fortran compiler
FortranDebugFlags   flags for Fortran debug info
FortranFlagsFortran compiler flags
+   GzipCmd command to run gzip program
HasBSD44Sockets boolean for system has BSD4.4 sockets
HasBsdMake  use the 4.4BSD variant of the make program?
HasBsearch  boolean for libc has bsearch()
@@ -218,6 +218,7 @@
DefaultUserPath default user xdm PATH environment variable
DependCmd   command to run makedepend
DependDir   build directory containing makedepend program
+   DriverManSuffix man suffix for driver pages
ExtensionDefines-D's for universal extensions
ExtensionOSDefines  -D's for additional extensions
FontCompilerFlags   flags for bdftosnf


-- 
Warren Turkal
President, GOLUM, Inc.
http://www.golum.org

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


Happyness with Radeon 9200 SE

2003-12-10 Thread rdavenpo
Just as a word of thanks,  I was able to successfully use
the recent 4.4 snapshot to drive my dual head Radeon 9200SE.  The 
MonitorLayout Option always failed to initiate the DVI port correctly.  This 
is also a problem on the ATI provided drivers recommended for the board. 

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


Re: [PATCH] documentation fix addition for config/cf/README

2003-12-10 Thread Warren Turkal
Warren Turkal wrote:
 I moved the GzipCmd to get it in alphabetical order. I also added
 documentation for DriverManSuffix.

This is an update of the previous. In addition to what is done in the last
patch (this patch includes it), I also documented DriverManDir and
MiscManDir.

wt

--- ../../../xc-old/config/cf/README2003-04-25 06:00:03.0 -0500
+++ README  2003-12-10 22:47:32.0 -0600
@@ -25,7 +25,6 @@
CURDIR  current directory relative to top of sources
CcCmd   command to run C compiler
CompressCmd command to run compress program
-   GzipCmd command to run gzip program
ConstructMFLAGS System V option to set MFLAGS make variable
CpCmd   command to copy one file to another
CplusplusCmdcommand to run C++ compiler
@@ -50,6 +49,7 @@
FortranCmd  command to run Fortran compiler
FortranDebugFlags   flags for Fortran debug info
FortranFlagsFortran compiler flags
+   GzipCmd command to run gzip program
HasBSD44Sockets boolean for system has BSD4.4 sockets
HasBsdMake  use the 4.4BSD variant of the make program?
HasBsearch  boolean for libc has bsearch()
@@ -218,6 +218,8 @@
DefaultUserPath default user xdm PATH environment variable
DependCmd   command to run makedepend
DependDir   build directory containing makedepend program
+   DriverManDirdirectory in which to install driver man pages
+   DriverManSuffix man suffix for driver pages
ExtensionDefines-D's for universal extensions
ExtensionOSDefines  -D's for additional extensions
FontCompilerFlags   flags for bdftosnf
@@ -246,6 +248,7 @@
ManSourcePath   common prefix of man page directories
ManSuffix   man suffix for programs
MiscManSuffix   man suffix for miscellaneous pages
+   MiscManDir  directory in which to install misc man pages
NeedDefaultDepLibs  boolean for enabling default DEPLIBS
NlsDir  directory in which to install nls files
NormalLibFS build libFS.a

-- 
Warren Turkal
President, GOLUM, Inc.
http://www.golum.org

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