Bug#191915: xfree86 crashes the system with S3 ProSavage PM133

2003-05-04 Thread Frederic Roussel
Package: xserver-xfree86
Version: 4.2.1-6

After `apt-get dist-upgrade' from xserver-xfree86 4.2.1-3 to
server-xfree86 4.2.1-6 the system freezes totally at boot up time when
`gdm' gets started. I had to revert back to 4.2.1-3 to keep the system
useable.

Thanks for the incredible amount of work you guys put in Debian!

ii  gdm2.2.5.5-2 GNOME Display Manager
Versions of the packages xserver-xfree86 depends on:
ii  debconf1.2.35Debian configuration management system
ii  libc6  2.3.1-16  GNU C Library: Shared libraries and Timezon
ii  xserver-common 4.2.1-6   files and utilities common to all X servers
ii  zlib1g 1.1.4-11  compression library - runtime

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux shuttle 2.4.20-w4l #1 Wed Jan 1 20:11:13 PST 2003
i686 unknown unknown GNU/Linux

### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf,
the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# If you want your changes to this file preserved by dexconf, only make
changes
# before the "### BEGIN DEBCONF SECTION" line above, and/or after the
# "### END DEBCONF SECTION" line below.
#
# To change things within the debconf section, run the command:
#   dpkg-reconfigure xserver-xfree86
# as root.  Also see "How do I add custom sections to a
dexconf-generated
# XF86Config or XF86Config-4 file?" in
/usr/share/doc/xfree86-common/FAQ.gz.

Section "Files"
FontPath"unix/:7100"# local font
server
# if the local font server has problems, we can fall back on
these
FontPath"/usr/lib/X11/fonts/Type1"
FontPath"/usr/lib/X11/fonts/CID"
FontPath"/usr/lib/X11/fonts/Speedo"
FontPath"/usr/lib/X11/fonts/misc"
FontPath"/usr/lib/X11/fonts/cyrillic"
FontPath"/usr/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/75dpi"
EndSection

Section "Module"
Load"GLcore"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
Load"speedo"
Load"type1"
Load"vbe"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "keyboard"
Option  "CoreKeyboard"
Option  "XkbRules"  "xfree86"
Option  "XkbModel"  "macintosh"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/misc/psaux"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "InputDevice"
Identifier  "Generic Mouse"
Driver  "mouse"
Option  "SendCoreEvents""true"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "Device"
Identifier  "Generic Video Card"
Driver  "savage"
BusID   "PCI:01:00:00"
EndSection

Section "Monitor"
Identifier  "Generic Monitor"
HorizSync   30-60
VertRefresh 50-75
Option  "DPMS"
EndSection

Section "Screen"
Identifier  "Default Screen"
Device  "Generic Video Card"
Monitor "Generic Monitor"
DefaultDepth24
SubSection "Display"
Depth   1
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   4
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   8
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   15
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   16
Modes   "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   24
Modes   "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier  "Default Layout"
Screen  "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Confi

[hetz@witch.dyndns.org: Fwd: RFT: prelinkable libGL.so (with a couple of optimizations)]

2003-05-04 Thread Daniel Stone
- Forwarded message from Hetz Ben Hamo <[EMAIL PROTECTED]> -

From: Hetz Ben Hamo <[EMAIL PROTECTED]>
Date: Sun, 4 May 2003 20:21:01 +
To: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Subject: Fwd: RFT: prelinkable libGL.so (with a couple of optimizations)
List-Id: For developer's disussion about the KDE core libraries


Hi,

I'm pretty sure that this might interest few people here. 

Here's what Jakub posted to redhat's list. The patch itself is also available 
(Against XFree 4.3).

--  Forwarded Message  --

Subject: RFT: prelinkable libGL.so (with a couple of optimizations)
Date: Saturday 03 May 2003 16:44 pm
From: Jakub Jelinek <[EMAIL PROTECTED]>

Hi!

ftp://people.redhat.com/jakub/XFree86/
contains patched XFree86 which contain a prelinkable libGL.so with a bunch
of optimizations.
I'd appreciate if you could test it out, both whether DRI etc. still works
for you, if you see any differences in GL benchmarks and how well prelinked
KDE and other programs which could not be prelinked because of libGL.so
works.

Jakub



- End forwarded message -

-- 
Daniel Stone <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
KDE: Konquering a desktop near you - http://www.kde.org


pgpoZ2bgcmmug.pgp
Description: PGP signature


Bug#191885: Corrupted fonts for S3 (Trio32) video card

2003-05-04 Thread David Lawyer
Package: xserver-svga
Version: 3.3.6-44

When I start X everything looks fine except for the font.  The font
looks like a few short vertical lines for each character.  Others
have reported a similar problem and the XFree86 FAQ mentions that a bug
exists in some Trio32 cards regarding the font cache (in the memory of
the video card).  Elsewhere, it states that version 3.2 fixed the bug by
providing a workaround if the bug is detected.  Well, it's not fixed for
me.  The video card worked fine with MS Windows, so the card is "OK".

David Lawyer

I'm using a Gateway 2000 with "STB Trio 32" video card.  i586 kernel
2.4.20.

Heres what is printed when I type startx:

hostname 2.08


XFree86 Version 3.3.6a / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: xx November 2000
If the server is older than 6-12 months, or if your card is newer
than the above date, look for a newer version before reporting
problems.  (see http://www.XFree86.Org/FAQ)
Operating System: Linux 2.4.13 i686 [ELF] 
Configured drivers:
  SVGA: server for SVGA graphics adaptors (Patchlevel 1):
  NV1, STG2000, RIVA 128, RIVA TNT, RIVA TNT2, RIVA ULTRA TNT2,
  RIVA VANTA, RIVA ULTRA VANTA, RIVA INTEGRATED, GeForce 256,
  GeForce DDR, Quadro, GeForce2 GTS, GeForce2 GTS (rev1),
  GeForce2 Ultra, Quadro 2 Pro, GeForce2 MX, GeForce2 MX DDR,
  Quadro 2 MXR, ET4000, ET4000W32, ET4000W32i, ET4000W32i_rev_b,
  ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a, ET4000W32p_rev_b,
  ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100, et3000, pvga1,
  wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33, gvga, r128, ati,
  sis86c201, sis86c202, sis86c205, sis86c215, sis86c225, sis5597,
  sis5598, sis6326, sis530, sis620, sis300, sis630, sis540, tvga8200lx,
  tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000,
  tvga9000i, tvga9100b, tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi,
  tgui9430dgi, tgui9440agi, cyber9320, tgui9660, tgui9680, tgui9682,
  tgui9685, cyber9382, cyber9385, cyber9388, cyber9397, cyber9520,
  cyber9525, 3dimage975, 3dimage985, cyber9397dvd, blade3d, cyberblade,
  clgd5420, clgd5422, clgd5424, clgd5426, clgd5428, clgd5429, clgd5430,
  clgd5434, clgd5436, clgd5446, clgd5480, clgd5462, clgd5464, clgd5465,
  clgd6205, clgd6215, clgd6225, clgd6235, clgd7541, clgd7542, clgd7543,
  clgd7548, clgd7555, clgd7556, ncr77c22, ncr77c22e, cpq_avga, mga2064w,
  mga1064sg, mga2164w, mga2164w AGP, mgag200, mgag100, mgag400, oti067,
  oti077, oti087, oti037c, al2101, ali2228, ali2301, ali2302, ali2308,
  ali2401, cl6410, cl6412, cl6420, cl6440, video7, ark1000vl, ark1000pv,
  ark2000pv, ark2000mt, mx, realtek, s3_savage, s3_virge, AP6422, AT24,
  AT3D, s3_svga, NM2070, NM2090, NM2093, NM2097, NM2160, NM2200,
  ct65520, ct65525, ct65530, ct65535, ct65540, ct65545, ct65546,
  ct65548, ct65550, ct65554, ct6, ct68554, ct69000, ct64200,
  ct64300, mediagx, V1000, V2100, V2200, p9100, spc8110, i740, i740_pci,
  Voodoo Banshee, Voodoo3, smi, generic
(using VT number 5)

XF86Config: /etc/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(--) no ModulePath specified using default: /usr/X11R6/lib/modules
PEX extension module for XFree86 3.3.6a 
(**) module pex5.so successfully loaded from /usr/X11R6/lib/modules
XIE extension module for XFree86 3.3.6a 
(**) module xie.so successfully loaded from /usr/X11R6/lib/modules
(**) XKB: rules: "xfree86"
(**) XKB: model: "pc102"
(**) XKB: layout: "us"
(**) Mouse: type: PS/2, device: /dev/psaux, buttons: 5
(**) Mouse: 3 button emulation (timeout: 50ms)
(**) Mouse: zaxismapping: (-)4 (+)5
(**) SVGA: Graphics device ID: "Generic Video Card"
(**) SVGA: Monitor ID: "Generic Monitor"
(--) SVGA: Mode "1024x768" needs hsync freq of 68.68 kHz. Deleted.
(--) SVGA: Mode "1152x864" needs hsync freq of 67.50 kHz. Deleted.
(--) SVGA: Mode "1280x960" needs hsync freq of 85.94 kHz. Deleted.
(--) SVGA: Mode "1280x1024" needs hsync freq of 63.98 kHz. Deleted.
(--) SVGA: Mode "1280x1024" needs hsync freq of 79.98 kHz. Deleted.
(--) SVGA: Mode "1280x1024" needs hsync freq of 91.15 kHz. Deleted.
(--) SVGA: Mode "1600x1200" needs hsync freq of 75.00 kHz. Deleted.
(--) SVGA: Mode "1600x1200" needs hsync freq of 81.25 kHz. Deleted.
(--) SVGA: Mode "1600x1200" needs hsync freq of 87.50 kHz. Deleted.
(--) SVGA: Mode "1600x1200" needs hsync freq of 93.75 kHz. Deleted.
(--) SVGA: Mode "1600x1200" needs hsync freq of 106.25 kHz. Deleted.
(--) SVGA: Mode "1792x1344" needs hsync freq of 83.66 kHz. Deleted.
(--) SVGA: Mode "1792x1344" needs hsync freq of 106.27 kHz. Deleted.
(--) SVGA: Mode "1856x1392" needs hsync freq of 86.35 kHz. Deleted.
(--) SVGA: Mode "1856x1392" needs hsync freq of 112.50 kHz. Deleted.
(--) SVGA: Mode "1920x1440" needs hsync freq of 90.00 kHz. Deleted.
(--) SVGA: Mode "1920x1440"

Re: Radeon 9000

2003-05-04 Thread Michel Dänzer
On Sam, 2003-05-03 at 10:39, Christian Schoenebeck wrote: 
> On 02 May 2003 12:14:18 +0200
> Michel Dänzer <[EMAIL PROTECTED]> wrote:
> 
> > > I tried the driver/chipset trick, but it just doesn't work out with
> > > 4.2.1.1, starting xserver fails with:
> > > 
> > >   (EE) RADEON(0): [agp] AGP not available
> > >   (EE) RADEON(0): [drm] failed to remove DRM signal handler
> > 
> > It doesn't fail due to this, it just means the DRI is disabled. Make
> > sure the kernel agpgart driver is loaded before the radeon DRM.
> 
> Yes, that was it. Thanks a lot!
> 
> I just thought agpgart would be loaded automatically. 

You can automate it by putting

below   radeon  agpgart

in a file in /etc/modutils/ and running update-modules.

> One thing I'm missing is that there's no dependency to xfonts-base, it's 
> only "suggested" by the moment. I guess this is due it can also be 
> provided by a xfonts server. But would a Debian specific patch with a 
> hint to install the xfonts-base package in such cases be a bad idea? 

That's what x-window-system-core is for.


-- 
Earthling Michel Dänzer   \  Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast  \ http://svcs.affero.net/rm.php?r=daenzer



Bug#179647: bug 179647

2003-05-04 Thread Markus H.
hi i am experiencing the same problems, since yesterday.
same packages, crashed 3 times today on me. system is
totally fscked up. cant work. removed wacom drivers and
deactivated them yet the same problem. hangs mostly using
konqueror or mozilla. first crash was in mozilla, second in
konqueror, third using khtml preview in quanta.

hope this will be fixxed soon. 

--
there is no fork()




Bug#191737: upstream bug 236 posted.

2003-05-04 Thread Ken Foskey

FYI...

-- 
Thanks
KenF
OpenOffice.org developer





Processed: the big, bad Xrender bug (Part II)

2003-05-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 186704 xlibs
Bug#186704: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#186758: libxft2: causes mozilla-xft to crash when browsing 
http://xinehq.de/ and http://www.linux.org.uk/diary/
Bug#187187: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#188488: libxft2: mozilla-xft crashes on several websites
Bug#189019: libxft2: Mozilla/Galeon crash when run over VNC link and RENDER 
extension not available; causes BadValue X protocol error
Bug#191071: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#191419: libxft2: mozilla-xft crashes when viewing www.debian.org with 
BadValue X protocol error
Bug#191555: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug reassigned from package `libxft2' to `xlibs'.

> merge 181815 186704
Bug#181815: xlibs: [Xrender] bad length computation in 
XRenderCompositeString16()/XRenderCompositeString32()
Bug#186704: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#182850: xlibs: [Xrender] bad length computation in 
XRenderCompositeString16()/XRenderCompositeString32()
Bug#186758: libxft2: causes mozilla-xft to crash when browsing 
http://xinehq.de/ and http://www.linux.org.uk/diary/
Bug#187187: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#188488: libxft2: mozilla-xft crashes on several websites
Bug#189019: libxft2: Mozilla/Galeon crash when run over VNC link and RENDER 
extension not available; causes BadValue X protocol error
Bug#191071: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#191419: libxft2: mozilla-xft crashes when viewing www.debian.org with 
BadValue X protocol error
Bug#191555: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Merged 181815 182850 186704 186758 187187 188488 189019 191071 191419 191555.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Bug#187365: xlibmesa3-glu: libraries not correctly linked

2003-05-04 Thread Marcelo E. Magallon
>> Michel Dänzer <[EMAIL PROTECTED]> writes:

 > Because the libGL provided by mesag3 doesn't seem to be able to load the
 > DRI drivers (though that might just be a matter of how it's built).

 Brian (?) mentioned something about building that capability on the
 mesa libraries a long time ago.  I don't know if he actually
 implemented it.  Mike was interested on that, too.  I don't see it
 mentioned in the changelog and a quick look at the sources does not
 find anything which could do that.  It might be in the embedded branch.

-- 
Marcelo




Bug#187365: xlibmesa3-glu: libraries not correctly linked

2003-05-04 Thread Marcelo E. Magallon
>> Branden Robinson <[EMAIL PROTECTED]> writes:

 > We could just as well ask why we bother to ship xlibmesa*, then.
 > 
 > I would like to know why the answers to your question and the above
 > should be different.

 The best answer I can come up with?  Because someone is bound to create
 a CD which doesn't include the mesa packages (because it's mesa and
 it's slow and it's software and who in their same mind would want to
 use that and it's not the cool thing of the day) yet he'll need libGLU
 for one reason or another[0].

 Other than that, it's just code duplication.  Modulo some compilation
 flags, both libGLU binaries are likely the same.  "mine" is much easier
 to build, though (it doesn't take 2+ GB of space ;-)

 [0] The one function not provided by libGL but libGLU used by -- dare I
 come up with a statistic on the spot -- 90% of the OpenGL programs out
 there is gluPerspective, which is a small wrapper for gluFrustum.  The
 next in line is probably gluBuild2DMipmaps, which unlike gluPerspective
 is larger two or three lines of code, and is in fact larger than a
 screenful.

 > N.B., I'm not opposed to having the XFree86 packages stop shipping
 > the Mesa libraries, I just want to have a coherent reason for doing
 > so.

 No, not the mesa libraries, just libGLU.  The libGL in the XFree86
 packages is a different beast when you compare it to the libGL
 libraries coming out of the mesa packages.  Same API, binary
 compatible, but totally different behaviour when it comes down to the
 nitty gritty.

 Marcelo




Processed: the big, bad Xrender bug (Part I)

2003-05-04 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> retitle 181815 xlibs: [Xrender] bad length computation in 
> XRenderCompositeString16()/XRenderCompositeString32()
Bug#181815: xlibs: Problem with XRenderCompositeText16 in Render extension
Changed Bug title.

> severity 181815 important
Bug#181815: xlibs: [Xrender] bad length computation in 
XRenderCompositeString16()/XRenderCompositeString32()
Severity set to `important'.

> tag 181815 = patch pending upstream
Bug#181815: xlibs: [Xrender] bad length computation in 
XRenderCompositeString16()/XRenderCompositeString32()
Tags were: pending patch sid upstream
Tags set to: patch, pending, upstream

> merge 181815 182850
Bug#181815: xlibs: [Xrender] bad length computation in 
XRenderCompositeString16()/XRenderCompositeString32()
Bug#182850: xlibs: [Xrender] bad length computation in 
XRenderCompositeString16()/XRenderCompositeString32()
Merged 181815 182850.

> retitle 191419 libxft2: mozilla-xft crashes when viewing www.debian.org with 
> BadValue X protocol error
Bug#191419: Crashes when displaying www.debian.org
Changed Bug title.

> tag 191419 upstream
Bug#191419: libxft2: mozilla-xft crashes when viewing www.debian.org with 
BadValue X protocol error
There were no tags set.
Tags added: upstream

> merge 186704 191419
Bug#186704: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#191419: libxft2: mozilla-xft crashes when viewing www.debian.org with 
BadValue X protocol error
Bug#187187: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#189019: libxft2: Mozilla/Galeon crash when run over VNC link and RENDER 
extension not available; causes BadValue X protocol error
Bug#191071: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#191555: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Merged 186704 187187 189019 191071 191419 191555.

> tag 186758 - moreinfo
Bug#186758: libxft2: causes mozilla-xft to crash when browsing 
http://xinehq.de/ and http://www.linux.org.uk/diary/
Tags were: moreinfo upstream
Tags removed: moreinfo

> merge 186704 186758
Bug#186704: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#186758: libxft2: causes mozilla-xft to crash when browsing 
http://xinehq.de/ and http://www.linux.org.uk/diary/
Bug#187187: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#189019: libxft2: Mozilla/Galeon crash when run over VNC link and RENDER 
extension not available; causes BadValue X protocol error
Bug#191071: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#191419: libxft2: mozilla-xft crashes when viewing www.debian.org with 
BadValue X protocol error
Bug#191555: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Merged 186704 186758 187187 189019 191071 191419 191555.

> tag 188488 - moreinfo
Bug#188488: libxft2: mozilla-xft crashes on several websites
Tags were: moreinfo upstream
Tags removed: moreinfo

> merge 186704 188488
Bug#186704: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#188488: libxft2: mozilla-xft crashes on several websites
Bug#186758: libxft2: causes mozilla-xft to crash when browsing 
http://xinehq.de/ and http://www.linux.org.uk/diary/
Bug#187187: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#189019: libxft2: Mozilla/Galeon crash when run over VNC link and RENDER 
extension not available; causes BadValue X protocol error
Bug#191071: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Bug#191419: libxft2: mozilla-xft crashes when viewing www.debian.org with 
BadValue X protocol error
Bug#191555: libxft2: using anti-aliased fonts with gnome-terminal causes 
BadValue X protocol error
Merged 186704 186758 187187 188488 189019 191071 191419 191555.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)




Bug#191737: acknowledged by developer (Re: Bug#191737: xinerama.h is missing extern C { for C++ compiling)

2003-05-04 Thread Marcelo E. Magallon
>> Daniel Stone <[EMAIL PROTECTED]> writes:

 > Yes, but it's not Xinerama's problem, and I don't see why it should be
 > bending over backwards to support people using it from another language.
 > I certainly won't be including this patch in my tree.

 Because that's the polite way of coding C header files.  You can't be
 so shortsighted to assume that the library is never going to be used by
 C++ programs (or any other languaje that can interface with C for that
 matter), specially when one of the reasons for choosing C over C++ is
 that the former is more interoperable than the later.  Quoting
 Stroustrup:

C programmers typically assume any C header can be used from a C++
program. This assumption has largely been true (after someone adds
suitable extern "C" directives), though headers that use C++
keywords as identifiers have been a constant irritant to C++
programmers (and sometimes a serious practical problem). 

[...]

The ability to share header files is an important aspect of C and
C++ culture and a key to performance of programs using both
languages. If the header files are kept compatible, C and C++
programs can call libraries implemented in "the other language" with
no data conversion overheads and no (or very minimal) call overhead.

 Granted, C++ programmers _are_ snottish in this respect, but there's no
 good reason for C programmers to behave the same way.

 Historically X has been a bad citizen in this general regard (True,
 False, Bool, Status, DirectColor and a lot of others pollute the
 namespace) but it does the right thing when it comes to extern "C".
 You just have to add a simple _XFUNCPROTOBEGIN / _XFUNCPROTOEND to the
 headers.

 Marcelo




Bug#191818: xlibs: Broken /usr/X11R6/lib/X11/app-defaults symlink

2003-05-04 Thread Daniel Schepler
Package: xlibs
Version: 4.2.1-6
Severity: normal

If I install xlibs in a chroot with only essential packages otherwise,
it creates a symlink /usr/X11R6/lib/X11/app-defaults ->
/etc/X11/app-defaults, but the package does not make sure the target
directory exists.

(This is breaking builds of rsxs under pbuilder.)

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux frobnitz 2.4.21-pre5 #1 Sat Mar 1 09:01:10 PST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages xlibs depends on:
ii  libc6 2.3.1-17   GNU C Library: Shared libraries an
ii  libfreetype6  2.1.4-2FreeType 2 font engine, shared lib
ii  xfree86-common4.2.1-6X Window System (XFree86) infrastr

-- no debconf information


-- 
Daniel Schepler  "Please don't disillusion me.  I
[EMAIL PROTECTED]haven't had breakfast yet."
 -- Orson Scott Card