Problems in FAO MailServ Reply command processing

2004-07-15 Thread FAO MailServ Reply
Error in the command: Please have a look at the attached file.
Unrecognized command verb: PLEASE
Subsequent commands ignored because of previous error.
Ignored: Important Notice
Ignored: 
Ignored: File: your_archive.pif has been removed
Ignored: As an anti-virus measure, FAO's Email system has replaced the sender's
Ignored: original attachment with this harmless text attachment. The original
Ignored: attachment was of a type deemed to be dangerous.
Ignored: The sender of this message has NOT been notified that the attachment was
Ignored: deleted.
Ignored: This policy was implemented in agreement with all departments in order to
Ignored: avoid a repeat of the virus outbreak of May 2000 where users were left
Ignored: without network services (Email, file shares, etc) for several days as a
Ignored: result of the "I Love You" virus. Since implementation of this policy,
Ignored: similar outbreaks have not re-occurred.
Ignored: Regards,
Ignored: Messaging Team.
Use the HELP command to get a list of legal MAILSERV commands.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: Continued : Xfree 4.4 make install failure on ppc system - scaled fonts problem with mkfonts

2004-07-15 Thread Ian Romanick
[EMAIL PROTECTED] wrote:
Following to the post  http://www.mail-archive.com/[EMAIL PROTECTED]/msg16132.html
I think I have found where the problem is : line 1024 of mkfontscale.c while calling 
FT_Get_Name_Index.
n parameters value is "space" when it crashed. I didn't checked all values of data in the struct 
face but family name is "Utopia" when it crash.
I have been able to reproduce this same problem on a G4 running Debian 
(sarge), but *not* on a POWER4 box.  GCC 3.3.4 was used on the G4, and 
GCC 3.3.3 was used on the POWER4.  Both built for 32-bit.  On the G4, I 
tried building with a variety of different optimization settings (-O0, 
-O2, -Os) and architecture settings, but nothing seemed to help.

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


Re: device driver - Kernel X XFree86 - USB - distribution

2004-07-15 Thread Juliusz Chroboczek
> So, are you saying that if I develop a Input Core driver (Serial and
> USB) it is not necessary to develop a XFree86 driver?

It's a little bit more exciting than that ;-)

The good news is that if you develop a Linux input driver, any
userspace application that groks /dev/event will be able to use your
device.  Additionally, if it's a relative device, any application that
can grok the PS/2 mouse protocol will be able to use your device.

The bad news is that as far as I know XFree86 does not yet have an
input driver for /dev/event.  Yes, this is a shame (I gladly take my
part of the blame).

However,

 - I've hacked together a simple /dev/event driver for KDrive (TinyX),
   which is available on 

 http://www.pps.jussieu.fr/~jch/software/files/lxevent.c

   It works for both relative and absolute devices, converting the
   latter to relative in the driver (it was developed for a synaptics
   touchpad, but should work with any device that has three buttons).
   You're welcome to do anything you wish with this code (you don't
   need to credit me, except for keeping my copyright notice in the
   sources).

 - If you develop for the event interface, you will not need to design
   a new interface.  Implementing a well-defined API will doubtless be
   simpler than rolling your own.

 - If you develop for the event interface, anyone with an absolute
   PS/2 or USB device will be able to help you with the XFree86 driver;
   if you use your private protocol, you'll be pretty much on your own.

Good luck,

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


RE: libextmod.a does not resolve symbols in XFree86

2004-07-15 Thread Michael Boccara
Great, this worked !
Thanks a lot, Mark.

Michael

> -Original Message-
> From: Mark Vojkovich [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 14, 2004 11:30 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: libextmod.a does not resolve symbols in XFree86
> 
> 
> 
> 
> On Wed, 14 Jul 2004, Michael Boccara wrote:
> 
> > > > Functions defined in XFree86 are not resolved in libextmod.a
> > > when referenced
> > > > as extern.
> > > > Why ?
> > > > Is there a way to help the symbol resolution ?
> > > >
> > >This is a problem you are seeing with the existing code or only
> > > after you modified something?   XFree86 modules can only resolve
> > > symbols exported by the core server.  XFree86 modules do not link
> > > to external libraries.
> > >
> >
> > Interesting.
> > I did modify something. I am actually developing my own X11 
> extension, in
> > the extmod module. The base XFree86 code doesn't have any issue.
> > The symbol I am trying to resolve is defined in libdix.a
> > (xc/programs/Xserver/dix), which is statically linked to XFree86.
> > How does XFree86 export symbols explicitely ?
> 
>   DIX symbols are exported in 
> xc/programs/Xserver/hw/xfree86/loader/dixsym.c
> 
> 
>   Mark.
> 
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel