bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] DragonFly BSD support


From: Bruno Haible
Subject: Re: [PATCH] DragonFly BSD support
Date: Sat, 31 May 2008 23:57:35 +0200
User-agent: KMail/1.5.4

Hi,

Hasso Tepper wrote:
> The attached patch fixes DragonFly BSD support in gnulib. The patch is 
> written by Matthew Dillon and is tested by many users as part of GNU m4 
> pkgsrc package.

Thank you for reporting this to us. We don't have the habit of checking the
various "ports collections" regularly.

Now, the first two hunks of your patch are nops: there are already
#ifdef __DragonFly__ tests further up in the two files.

About the third hunk, Eric Blake asked a for a rationale in
<http://lists.gnu.org/archive/html/bug-gnulib/2008-04/msg00269.html>
and got no reply.

If you want to help getting gnulib work on DragonFly:

You find in   http://www.haible.de/bruno/gnu/testdir-stdioext.tar.gz
the documentation and implementation for all systems so far (from BSD
systems to QNX), and a test suite. The documentation/specification is
in the .h files.

To port this package:

  - Unpack the package, configure it. Try "make" and fix the problems.
  - Run "make check" to see the test results.
  - The recommended order of porting (from easy to harder) is:
    fbufmode, fseterr, freadable, fwritable, freading, fwriting,
    fpending, fpurge, freadptr, freadseek, freadahead.

If you want to have the complete liberty to shuffle around fields in the
FILE struct, without risking crashes of programs that use gnulib, and you
add such primitive functions to DragonFly, gnulib will use these primitives
(provided they pass the testsuite).

Bruno





reply via email to

[Prev in Thread] Current Thread [Next in Thread]