Re: Install errors with 4.3.0 on RH7.3?

[Kendall Bennett]

Andrew C Aitchison <[EMAIL PROTECTED]> wrote:

> It looks to me as if your make World failed (but kept going as it
> usually does) so install tried again and failed.
> 
> I have
>   xc/programs/rstart/contexts/@Aliases
>   xc/programs/rstart/samples/contexts.odt1/@Aliases
>   xc/programs/rstart/samples/contexts.sun/@Aliases
> all with matching ,v files, so it may be a problem with your check out,
> or another case of one broken platform in 12.

Well I found my problem. We build all our versions of XFree86 using 
source code stored in Perforce (a branch to our devel tree that allows 
easy merging back/forth). As it turns out, Perforce does not seem to like 
filenames with an '@' symbol in them, and then never got checked into 
Perforce!! I will have to see if I can manually check those files into 
the machine, otherwise we will have a problem ;-(.

What exactly are these files for? Is there any reason why they using the 
@ symbol in file names specifically? 

Regards,

---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com

~ SciTech SNAP - The future of device driver technology! ~

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

_XAllocTemp and _XFreeTemp in Xrender on X11R5

[Albert Chin]

I tried building Xrender from XFree86-4.3.0 on Solaris 2.5.1 (X11R5).
It has neither _XAllocTemp or _XFreeTemp. Any way to work around this
in Xrender/Picture.c?

-- 
albert chin ([EMAIL PROTECTED])
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: xfig crashes XFree86 server (4.3.0) with trident driver

[Gary E. RAFE, Ph.D.]

!   If it's reproducible and you can get a gdb backtrace, that would
!be useful.   Baring that, seeing it if goes away with Option "NoAccel"
!would at least narrow things down.  

I gave this another go with a newly-built debug server,
XAA and trident driver modules, and got the following
backtrace information:

(gdb) bt
#0  0x28389b78 in kill () from /usr/lib/libc.so.4
#1  0x283ca742 in abort () from /usr/lib/libc.so.4
#2  0x80bc73a in goodbye (abortflag=1) at w_cmdpanel.c:538
#3  0x809c275 in emergency_quit (abortflag=1) at u_error.c:98
#4  0x809c0a8 in error_handler (err_sig=1) at u_error.c:52
#5  0xbfbfffac in ?? ()
#6  0x282b1d49 in XrmGetFileDatabase () from /usr/X11R6/lib/libX11.so.6
#7  0x28294053 in XGetErrorDatabaseText () from /usr/X11R6/lib/libX11.so.6
#8  0x809c149 in X_error_handler (d=0x81d5800, err_ev=0xbfbff27c)
at u_error.c:70
#9  0x282af8a0 in _XIOError () from /usr/X11R6/lib/libX11.so.6
#10 0x282ad2fa in _XRead () from /usr/X11R6/lib/libX11.so.6
#11 0x282add30 in _XReply () from /usr/X11R6/lib/libX11.so.6
#12 0x282a99dc in XSync () from /usr/X11R6/lib/libX11.so.6
#13 0x810b07a in app_flush () at w_util.c:170
#14 0x810e405 in process_pending () at w_util.c:1122
#15 0x808a802 in main (argc=1, argv=0xbfbff8e0) at main.c:1256
#16 0x804d859 in _start ()

No mention of trident_drv.o or libxaa.a here.
Do I need more of the XFree86-4.3.0 source tree built (all?) as debug ?
--
Gary E. RAFE, Ph.D.
[EMAIL PROTECTED]
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: xfig crashes XFree86 server (4.3.0) with trident driver

[Mark Vojkovich]

   Sorry, I meant a backtrace of XFree86, not of xfig.


Mark.

On Fri, 21 Mar 2003, Gary E. RAFE, Ph.D. wrote:

> !   If it's reproducible and you can get a gdb backtrace, that would
> !be useful.   Baring that, seeing it if goes away with Option "NoAccel"
> !would at least narrow things down.  
> 
> I gave this another go with a newly-built debug server,
> XAA and trident driver modules, and got the following
> backtrace information:
> 
> (gdb) bt
> #0  0x28389b78 in kill () from /usr/lib/libc.so.4
> #1  0x283ca742 in abort () from /usr/lib/libc.so.4
> #2  0x80bc73a in goodbye (abortflag=1) at w_cmdpanel.c:538
> #3  0x809c275 in emergency_quit (abortflag=1) at u_error.c:98
> #4  0x809c0a8 in error_handler (err_sig=1) at u_error.c:52
> #5  0xbfbfffac in ?? ()
> #6  0x282b1d49 in XrmGetFileDatabase () from /usr/X11R6/lib/libX11.so.6
> #7  0x28294053 in XGetErrorDatabaseText () from /usr/X11R6/lib/libX11.so.6
> #8  0x809c149 in X_error_handler (d=0x81d5800, err_ev=0xbfbff27c)
> at u_error.c:70
> #9  0x282af8a0 in _XIOError () from /usr/X11R6/lib/libX11.so.6
> #10 0x282ad2fa in _XRead () from /usr/X11R6/lib/libX11.so.6
> #11 0x282add30 in _XReply () from /usr/X11R6/lib/libX11.so.6
> #12 0x282a99dc in XSync () from /usr/X11R6/lib/libX11.so.6
> #13 0x810b07a in app_flush () at w_util.c:170
> #14 0x810e405 in process_pending () at w_util.c:1122
> #15 0x808a802 in main (argc=1, argv=0xbfbff8e0) at main.c:1256
> #16 0x804d859 in _start ()
> 
> No mention of trident_drv.o or libxaa.a here.
> Do I need more of the XFree86-4.3.0 source tree built (all?) as debug ?
> --
> Gary E. RAFE, Ph.D.
> [EMAIL PROTECTED]
> 

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

Re: [Dri-devel] Re: XFree86 bugzilla available

[José Fonseca]

No DRI developer expressed his interest or opposition, probably because
there isn't opposition, or simply no interest. In either case I see no
reasons why not proceed, so I'll open a bug to address this. I'll ask
that [EMAIL PROTECTED] (the same addressed used on SF BT
system) is set as the default owner for DRI bugs.

Also, what's the general mailing list one can subscribe to receive
notifications everytime a bug is open?

José Fonseca


On Wed, Mar 19, 2003 at 12:07:56PM +, José Fonseca wrote:
> On Tue, Mar 18, 2003 at 08:04:22PM -0500, David Dawes wrote:
> > An XFree86 bugzilla is now available at .
> > Many thanks to Hewlett-Packard for supplying the hardware, netSweng for
> > hosting, and the many developers who helped configure and test it.
> 
> I know that the current policy on DRI is to post bugs on dri-users or
> dri-devel, but with XFree86 having a bug database is inevitable that
> people will eventually post bugs there too. Therefore what's the
> possibility of:
>  - Setting up a general "owner" for DRI bugs, which probably would be
>[EMAIL PROTECTED]
>  - automatically set the owner of DRI bugs, e.g., by the users adding a
>"DRI" keyword, or associating the "XFree86 Server"->"DRI" extension
>component.
>  - Add the possibility to add comments to bugs via e-mail.
> 
> Basically I would like to be possible that:
>  - An user adds a bug concerning DRI
>  - The owner is (either manually or automatically) set to
>[EMAIL PROTECTED], which receives the bug
>  - Any developer on the dri-devel list which has an account on
>XFree86 Bugzilla can reply and that comment is added to the bug
>database.
>  - Certain maintainence tasks (such as closing the bug, read an
>attachment) will require to use Bugzilla web interface, but bugzilla
>can be configured to remember our login, so it's straightforward.
> 
> I would appreciate if the XFree86 and DRI developers considered this.

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

Re: [Dri-devel] Re: XFree86 bugzilla available

[Keith Whitwell]

José Fonseca wrote:
No DRI developer expressed his interest or opposition, probably because
there isn't opposition, or simply no interest. In either case I see no
reasons why not proceed, so I'll open a bug to address this. I'll ask
that [EMAIL PROTECTED] (the same addressed used on SF BT
system) is set as the default owner for DRI bugs.
Also, what's the general mailing list one can subscribe to receive
notifications everytime a bug is open?
Sorry...  I think it's a good idea as proposed.

Keith




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

Re: [Dri-devel] Re: XFree86 bugzilla available

[Michel Dänzer]

On Fre, 2003-03-21 at 21:07, José Fonseca wrote:
> No DRI developer expressed his interest or opposition, probably because
> there isn't opposition, or simply no interest. In either case I see no
> reasons why not proceed, so I'll open a bug to address this. I'll ask
> that [EMAIL PROTECTED] (the same addressed used on SF BT
> system) is set as the default owner for DRI bugs.

I think it's a good idea but that dri-devel makes more sense than
dri-patches.

> Also, what's the general mailing list one can subscribe to receive
> notifications everytime a bug is open?

Currently [EMAIL PROTECTED] gets them all.


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

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