Hi Hackers,
why does these function allow seeking beyond the EOF of a file in
O_RDONLY/²rb² mode ?
How does these function then signal the EOF correctly ?
Seeking beyond the EOF makes sense for me in write-mode but not in read-only
mode !
With Regards,
Martin
Hi!
Please consider this small patch to make config(8) buildable on GNU
systems.
Thanks
--
Robert Millan
Index: usr.sbin/config/main.c
===
--- usr.sbin/config/main.c (revision 223721)
+++ usr.sbin/config/main.c (working c
The userland aicasm utility in sys/dev/aic7xxx/aicasm/Makefile is being
built with "-nostdinc -I/usr/include" options. Unfortunately this breaks
building aicasm on systems using the upstream version of GCC, where
"-nostdinc" disables more search directories than are enabled by
"-I/usr/include".
T
Code in sys/dev/aic7xxx/aicasm/ contains a few checks on the __linux__
macro that actually break build on GNU systems (including Linux-based
ones but also GNU/kFreeBSD).
Some of them use __linux__ to include an alternate version of
that would be placed in "../queue.h". However that file
isn't pr
On Sat, 2 Jul 2011, Robert Millan wrote:
The userland aicasm utility in sys/dev/aic7xxx/aicasm/Makefile is being
built with "-nostdinc -I/usr/include" options. Unfortunately this breaks
building aicasm on systems using the upstream version of GCC, where
"-nostdinc" disables more search director
Since their inception, GNU/kFreeBSD systems had defined
"__FreeBSD_kernel__" as builtin macro to indicate this is a system
that uses the kernel of FreeBSD. We couldn't define "__FreeBSD__"
because this implies a full FreeBSD system, and a lot of software
checks for this macro when it is concerned
2011/7/2 Benjamin Kaduk :
> There is a functional difference between '-nostdinc -I/usr/include -I.' even
> when the standard include search path is just /usr/include -- the standard
> include paths are always searched last (unless -nostdinc is given), even if
> they are explicitly listed on the com
On Sat, Jul 2, 2011 at 6:57 AM, Martin Möller
wrote:
> Hi Hackers,
>
> why does these function allow seeking beyond the EOF of a file in
> O_RDONLY/²rb² mode ?
Perhaps because the standard explicitly says that it's allowed:
http://pubs.opengroup.org/onlinepubs/009695399/functions/lseek.html
> Ho
On Sat, 2 Jul 2011, Robert Millan wrote:
My request is that FreeBSD also defines __FreeBSD_kernel__. If this
happens, life would be made a bit easier on both sides, as it'd be
% Index: contrib/gcc/config/freebsd-spec.h
% ===
% --
Am 02.07.2011 17:25, schrieb Benjamin Kaduk:
> On Sat, 2 Jul 2011, Robert Millan wrote:
>
>> The userland aicasm utility in sys/dev/aic7xxx/aicasm/Makefile is being
>> built with "-nostdinc -I/usr/include" options. Unfortunately this breaks
>> building aicasm on systems using the upstream version
On Sat, 2 Jul 2011 17:41:03 +0200
Robert Millan wrote:
> Since their inception, GNU/kFreeBSD systems had defined
> "__FreeBSD_kernel__" as builtin macro to indicate this is a system
> that uses the kernel of FreeBSD. We couldn't define "__FreeBSD__"
> because this implies a full FreeBSD system,
On 2011-Jul-02 17:22:15 +0200, Robert Millan wrote:
>Code in sys/dev/aic7xxx/aicasm/ contains a few checks on the __linux__
>macro that actually break build on GNU systems (including Linux-based
>ones but also GNU/kFreeBSD).
Thanks for all the patches. I wonder if you could use send-pr to
formal
On Sat, Jul 02, 2011 at 07:37:24PM -0400, Alexander Kabaev wrote:
> On Sat, 2 Jul 2011 17:41:03 +0200
> Robert Millan wrote:
>
> > My request is that FreeBSD also defines __FreeBSD_kernel__. If this
> > happens, life would be made a bit easier on both sides, as it'd be
> > more natural for port
On Sat, Jul 2, 2011 at 7:08 PM, Ed Maste wrote:
> On Sat, Jul 02, 2011 at 07:37:24PM -0400, Alexander Kabaev wrote:
>
>> On Sat, 2 Jul 2011 17:41:03 +0200
>> Robert Millan wrote:
>>
>> > My request is that FreeBSD also defines __FreeBSD_kernel__. If this
>> > happens, life would be made a bit ea
14 matches
Mail list logo
