linux-kernel - Re: New filesystem for Linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0611032250550.23669@yvahk01.tjqt.qr>
Date:	Fri, 3 Nov 2006 22:51:47 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
cc:	Gabriel C <nix.or.die@...glemail.com>, linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux

>> > > > So anyway, why do you need _llseek? Can't you just use lseek()
>> > > > like
>> > > > everyone else?
>> > > 
>> > > Because I want it to work with glibc 2.0 that I still use on one
>> > > machine.
>> > 
>> > BTW. is it some interaction with symbols defined elsewhere or were
>> > _syscall
>> > macros dropped altogether? Which glibc symbol should I use in #ifdef
>> > to tell if
>> > glibc has 64-bit support?
>> 
>> -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES -D_FILE_OFFSET_BITS=64
>> 
>> I think the second is not needed.
>
> I see, but the question is how do I test in C preprocessor that glibc is
> sufficiently new to react on them?

__GLIBC_MAJOR__ and __GLIBC_MINOR__


	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/