This is the mail archive of the glibc-bugs@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/226] New: [RFC] d_type is always set to "0"


Hi, 
 
I know that modern linux kernel+glibc can provide useful d_type member in 
dirent structure. But on my freshly built glibc d_type is always "0". 
 
glibc - from cvs 20040617 
Linux - 2.6.7 
binutils - 2.15.91.0.1 
gcc - 3.3.3 
 
glibc was built by: 
../libc/configure --with-headers=/usr/src/linux-2.6.7/include \ 
--enable-add-ons=nptl \ 
--enable-kernel=current \ 
--with-__thread \ 
--with-tls \ 
--without-gd \ 
--without-cvs 
 
On another GNU/Linux box (with glibc from distro) d_type works fine. Where am I 
wrong? 
 
	Thanks. 
 
p.s. sorry if it is FAQ or something like this, but google found nothing useful 
for my case.

-- 
           Summary: [RFC] d_type is always set to "0"
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: cbou at mail dot ru
                CC: glibc-bugs at sources dot redhat dot com


http://sources.redhat.com/bugzilla/show_bug.cgi?id=226

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]