Re: Using lex in a shared library

2010-07-05 Thread Peter Jeremy
On 2010-Jul-02 23:53:17 +0100, Philip Herron redbr...@gcc.gnu.org wrote: Although maybe not helpful but have you considered using automake/libtool instead makes it so much simpler in my opinion. ... Automake will auto-handle Lex and Yacc files too. And is extremely portable. You are joking,

Re: Using lex in a shared library

2010-07-05 Thread dhruva
On Mon, Jul 5, 2010 at 11:57 AM, Peter Jeremy peterjer...@acm.org wrote: On 2010-Jul-02 23:53:17 +0100, Philip Herron redbr...@gcc.gnu.org wrote: Although maybe not helpful but have you considered using automake/libtool instead makes it so much simpler in my opinion. ... Automake will

Re: Extended attributes for NFSv3 - possible Linux interop

2010-07-05 Thread James Morris
On Fri, 2 Jul 2010, Robert N. M. Watson wrote: Something that's always worried me about the Mac OS X and Linux EA APIs is the namespace issue: in FreeBSD, we have an explicit enumeration of namespaces reflected in an argument to the system calls -- in our case, an int, but you could

Re: Extended attributes for NFSv3 - possible Linux interop

2010-07-05 Thread Robert N. M. Watson
On 5 Jul 2010, at 10:25, James Morris wrote: I'm happy to help contribute to the writing on an Internet Draft and/or RFC -- the lack of NFS support for EAs (and the EA vs. file fork confusion) have long caused me frustration, and with systems like SELinux, our various MAC policies, and

Re: Using lex in a shared library

2010-07-05 Thread Dag-Erling Smørgrav
Not related to your problem, but related to $SUBJECT: make sure to use -Psomething in LFLAGS so your lex-generated symbols don't conflict with those present in applications that use your library, or in other libraries those applications may use. DES -- Dag-Erling Smørgrav - d...@des.no

Do we still need libc_r and libkse in /usr/src/lib?

2010-07-05 Thread Dmitry Krivenok
Hi Hackers, I've just started learning implementation of threads in FreeBSD-CURRENT. exctags found three different implementations of pthread_create function - libc_r, libkse and libthr: # pri kind tag file 1 F f_pthread_create lib/libc_r/uthread/uthread_create.c

Re: elf obj load: skip zero-sized sections early

2010-07-05 Thread Andriy Gapon
on 02/07/2010 11:29 Bjoern A. Zeeb said the following: On Fri, 25 Jun 2010, Andriy Gapon wrote: Hey, Proposed patch skips zero sized sections without going into trouble of allocating section entry (progtab), doing zero-sized memory allocs and copies. I observe that sometimes zero-sized

Re: elf obj load: skip zero-sized sections early

2010-07-05 Thread Bjoern A. Zeeb
On Mon, 5 Jul 2010, Andriy Gapon wrote: on 02/07/2010 11:29 Bjoern A. Zeeb said the following: On Fri, 25 Jun 2010, Andriy Gapon wrote: Hey, Proposed patch skips zero sized sections without going into trouble of allocating section entry (progtab), doing zero-sized memory allocs and copies.

Re: elf obj load: skip zero-sized sections early

2010-07-05 Thread Andriy Gapon
on 05/07/2010 20:12 Bjoern A. Zeeb said the following: On Mon, 5 Jul 2010, Andriy Gapon wrote: on 02/07/2010 11:29 Bjoern A. Zeeb said the following: On Fri, 25 Jun 2010, Andriy Gapon wrote: Hey, Proposed patch skips zero sized sections without going into trouble of allocating section

Re: elf obj load: skip zero-sized sections early

2010-07-05 Thread Julian Elischer
On 7/5/10 10:12 AM, Bjoern A. Zeeb wrote: On Mon, 5 Jul 2010, Andriy Gapon wrote: [...] The same applies to VIMAGE btw. Same technique. or the proposed per-vimage AND per-CPU zone (to allow pcpu stats in a vimage..).. which degenerates to just more pcpu stuff if vimage is not enabled.

Re: Non-POSIX compliant pmake with secondary expansion?

2010-07-05 Thread Harti Brandt
Hi Garret, On Wed, 30 Jun 2010, Garrett Cooper wrote: GCI currently set: GC GC.POSIX= I think this should be actually a target (the first one in the Makefile): .POSIX: GC GCIn a Makefile thinking that it would enable only POSIX GCfunctionality, and was fidgeting around with the

Re: PCI Express and drivers

2010-07-05 Thread Daniel O'Connor
On 06/07/2010, at 5:32, Christopher Bowman wrote: If I could, let me ask another question. My device could potential have up to 6 BARs, that would be mapped into user space. Should I simply bundle them together in my driver into one contiguous space or should I make the user perform

Re: PCI Express and drivers

2010-07-05 Thread Christopher Bowman
If I could, let me ask another question. My device could potential have up to 6 BARs, that would be mapped into user space. Should I simply bundle them together in my driver into one contiguous space or should I make the user perform multiple mmap calls? If I go the multiple mmap route, how do