diff options
author | Ulrich Drepper <drepper@redhat.com> | 2007-10-28 08:24:07 +0000 |
---|---|---|
committer | Ulrich Drepper <drepper@redhat.com> | 2007-10-28 08:24:07 +0000 |
commit | 88197030d5805d95d3e71d0aab71f44c6895b3b2 (patch) | |
tree | f25d4b4cc3579b52338c90b598b3daf8f82ceed3 /FAQ.in | |
parent | 94833f118b7b78a89595427c9d1a27f38084dbb9 (diff) | |
download | glibc-88197030d5805d95d3e71d0aab71f44c6895b3b2.zip glibc-88197030d5805d95d3e71d0aab71f44c6895b3b2.tar.gz glibc-88197030d5805d95d3e71d0aab71f44c6895b3b2.tar.bz2 |
[BZ #5222]
2007-10-28 Ulrich Drepper <drepper@redhat.com>
[BZ #5222]
* elf/dl-load.c (_dl_rtld_di_serinfo): Correct handling of short
path elements in counting mode.
Diffstat (limited to 'FAQ.in')
-rw-r--r-- | FAQ.in | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -287,12 +287,12 @@ down the build process and need more disk space. failure should be looked into. Depending on the failures, you probably should not install the library at all. -You should consider using the `glibcbug' script to report the failure, -providing as much detail as possible. If you run a test directly, please -remember to set up the environment correctly. You want to test the compiled -library - and not your installed one. The best way is to copy the exact -command line which failed and run the test from the subdirectory for this -test in the sources. +You should consider reporting it in bugzilla +<http://sourceware.org/bugzilla/> providing as much detail as possible. +If you run a test directly, please remember to set up the environment +correctly. You want to test the compiled library - and not your installed +one. The best way is to copy the exact command line which failed and run +the test from the subdirectory for this test in the sources. There are some failures which are not directly related to the GNU libc: - Some compilers produce buggy code. No compiler gets single precision |