This is the mail archive of the libc-alpha@sourceware.org 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]

Re: Started moving FAQ to the wiki - please review!


On Fri, 27 Apr 2012, Andreas Jaeger wrote:

> I started with moving the FAQ from git to the wiki, it is now at:
> 
> http://sourceware.org/glibc/wiki/FAQ

I suggest removing the attempts to attribute individual items to 
particular authors (the {AB} at the start of entries).

> 1.13 When compiling GNU libc I get lots of errors saying functions in glibc
> are duplicated in libgcc.

Yes, remove.  Not a current issue.

> 1.19 `make' complains about a missing dlfcn/libdl.so when building
> 	malloc/libmemprof.so.  How can I fix this?

Yes, remove.  Not a current issue.

> I did some minor edits where I noticed things where wrong - but the FAQ needs
> a review by all of us.

My views of these items.

"What systems does the GNU C Library run on?" - actually README is much 
closer to current than FAQ.  I think just delete this item and update 
README as needed.

"What compiler do I need to build GNU libc?" - point to the main 
installation documentation which discusses prerequisites and their 
versions.

"When I try to compile glibc I get only error messages. What's wrong?" - I 
don't think this is useful to have as a separate item.

"Do I need a special linker or assembler?" - again, just point to 
installation docs.  I'd be inclined to combine all these entries into 
"What tools do I need to build GNU libc?" and give a general overview 
(GCC, GNU binutils, GNU make, various other tools) without version 
numbers, pointing to the main install docs for more details.

"Do I need some more things to compile the GNU C Library?" - likewise, but 
check all the information is already present in the main install docs.  
The information about disk space and time is very old and can just be 
removed now.

"What version of the Linux kernel headers should be used?" - likewise, 
main install docs.

"When I run `nm -u libc.so' on the produced library I still find 
unresolved symbols. Can this be ok?" - keep.

"What are these `add-ons'?" - in principle keep, but "export rules" (old 
crypt add-on) are irrelevant, remove bits about linuxthreads, crypt and 
localedata as very old.

"My XXX kernel emulates a floating-point coprocessor for me. Should I 
enable --with-fp?" - rewrite (choice of --without-fp is really about 
matching the compiler's ABI, and only relevant for certain platforms such 
as powerpc or mips).

"Why do I get messages about missing thread functions when I use librt? I 
don't even use threads." - probably keep.

"I get failures during `make check'. What should I do?" - keep, but remove 
all the references to specific old versions.  (The bit about possible 
kernel bugs should be changed to give the details for tst-cpuclock2 only, 
as in <http://sourceware.org/ml/libc-alpha/2012-02/msg00468.html> - that's 
the only case I know of of a current issue traced to a known kernel bug.)

"What is symbol versioning good for? Do I need it?" - probably shorten not 
to discuss much about disabling it or specific versions (2.1).

"How can I compile on my fast ix86 machine a working libc for my slow 
i386? After installing libc, programs abort with "Illegal Instruction"." - 
remove, you can't build -march=i386 now at least with NPTL (glibc requires 
atomics only available on i486 and later).

"Which tools should I use for MIPS?" - remove, see general point about 
tools.

"Which compiler should I use for powerpc64?" - likewise.

"`make' fails when running rpcgen the first time, what is going on? How do 
I fix this?" - keep, but if we can get cross-rpcgen in then it will no 
longer be the case that rpcgen is the first use of the newly compiled 
libc.

"Why do I get:`#error "glibc cannot be compiled without optimization"', 
when trying to compile GNU libc with GNU CC?" - keep.

-- 
Joseph S. Myers
joseph@codesourcery.com


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