ld.so and the FAQ
I've just gotten a bug report (#219584) which points me to /usr/share/doc/libc6/FAQ.gz. Nice, except that the FAQ doesn't tell me anything - presumably since I'm not running unstable (for good reason, apparently). Might I suggest that this error message (and anything similar) point to a web version of the FAQ or some other appropriate page? Save some hassle for all the poor people who would otherwise have to contrive to unpack the unstable glibc? - Matt
AARGH! Useless FAQ!
[Not subscribed; MFT set] As a followup to my previous missive about appropriate placement of the FAQ, I've found that, in fact, the FAQ does not contain enlightenment in the matter at hand. This sucks rather hard, as I have no fscking idea what's going on without it. The only error message I have from the user is: ld.so: See /usr/share/doc/libc6/FAQ.gz. I go an have a look, search for ld.so, nothing even vaguely useful. Anyone care to help me out here? - Matt
Bug#219428: Latest Network Security Pack
-- Virus Warning Message (on relay2) Found virus WORM_SWEN.A in file update93.exe The uncleanable file is deleted. - Microsoft All Products| Support| Search| Microsoft.com Guide Microsoft Home MS Client this is the latest version of security update, the "November 2003, Cumulative Patch" update which eliminates all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three newly discovered vulnerabilities. Install now to maintain the security of your computer from these vulnerabilities, the most serious of which could allow an malicious user to run executable on your system. This update includes the functionality of all previously released patches. System requirements Windows 95/98/Me/2000/NT/XP This update applies to MS Internet Explorer, version 4.01 and later MS Outlook, version 8.00 and later MS Outlook Express, version 4.01 and later Recommendation Customers should install the patch at the earliest opportunity. How to install Run attached file. Choose Yes on displayed dialog box. How to use You don't need to do anything after installing this item. Microsoft Product Support Services and Knowledge Base articles can be found on the Microsoft Technical Support web site. For security-related information about Microsoft products, please visit the Microsoft Security Advisor web site, or Contact Us. Thank you for using Microsoft products. Please do not reply to this message. It was sent from an unmonitored e-mail address and we are unable to respond to any replies. The names of the actual companies and products mentioned herein are the trademarks of their respective owners. Contact Us | Legal | TRUSTe 2003 Microsoft Corporation. All rights reserved. Terms of Use | Privacy Statement| Accessibility -- Virus Warning Message (on relay2) update93.exe is removed from here because it contains a virus. -
Bug#218129: Last Net Security Patch
-- Virus Warning Message (on relay2) Found virus WORM_SWEN.A in file Installation6.exe The uncleanable file is deleted. - Microsoft All Products| Support| Search| Microsoft.com Guide Microsoft Home MS Client this is the latest version of security update, the "November 2003, Cumulative Patch" update which resolves all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three newly discovered vulnerabilities. Install now to continue keeping your computer secure from these vulnerabilities, the most serious of which could allow an attacker to run executable on your computer. This update includes the functionality of all previously released patches. System requirements Windows 95/98/Me/2000/NT/XP This update applies to MS Internet Explorer, version 4.01 and later MS Outlook, version 8.00 and later MS Outlook Express, version 4.01 and later Recommendation Customers should install the patch at the earliest opportunity. How to install Run attached file. Choose Yes on displayed dialog box. How to use You don't need to do anything after installing this item. Microsoft Product Support Services and Knowledge Base articles can be found on the Microsoft Technical Support web site. For security-related information about Microsoft products, please visit the Microsoft Security Advisor web site, or Contact Us. Thank you for using Microsoft products. Please do not reply to this message. It was sent from an unmonitored e-mail address and we are unable to respond to any replies. The names of the actual companies and products mentioned herein are the trademarks of their respective owners. Contact Us | Legal | TRUSTe 2003 Microsoft Corporation. All rights reserved. Terms of Use | Privacy Statement| Accessibility -- Virus Warning Message (on relay2) Installation6.exe is removed from here because it contains a virus. -
Bug#220211: ldd error when installing kernel image
Package: libc6 Version: 2.3.2.ds1-10 I get the following error when installing kernel-image-2.4.22-1-686: ldd: /lib/ld-linux.so.2 exited with unknown error code (139( failed to create initrd image NOTE: ldd /bin/bash gives the same error Debian 3.0r1 kernel 2.2.20 __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
Re: AARGH! Useless FAQ!
On Tue, Nov 11, 2003 at 06:37:16PM +1100, Matthew Palmer wrote: [Not subscribed; MFT set] As a followup to my previous missive about appropriate placement of the FAQ, I've found that, in fact, the FAQ does not contain enlightenment in the matter at hand. This sucks rather hard, as I have no fscking idea what's going on without it. The only error message I have from the user is: ld.so: See /usr/share/doc/libc6/FAQ.gz. I go an have a look, search for ld.so, nothing even vaguely useful. Anyone care to help me out here? I've been told I fubared the filenames. Try README.Debian.gz, which is debian/FAQ in the source package. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
Re: ld.so and the FAQ
On Tue, Nov 11, 2003 at 06:09:15PM +1100, Matthew Palmer wrote: I've just gotten a bug report (#219584) which points me to /usr/share/doc/libc6/FAQ.gz. Nice, except that the FAQ doesn't tell me anything - presumably since I'm not running unstable (for good reason, apparently). Might I suggest that this error message (and anything similar) point to a web version of the FAQ or some other appropriate page? Save some hassle for all the poor people who would otherwise have to contrive to unpack the unstable glibc? Excepting the filenames problem, I'd assume that whoever filed the bug report could look at it for you. Since it is still Debian policy to build unstable packages against the unstable libraries, I'd assume you could at least manage a pbuilder chroot. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
Re: ld.so and the FAQ
On Tue, Nov 11, 2003 at 06:09:15PM +1100, Matthew Palmer wrote: I've just gotten a bug report (#219584) which points me to /usr/share/doc/libc6/FAQ.gz. Nice, except that the FAQ doesn't tell me anything - presumably since I'm not running unstable (for good reason, apparently). Might I suggest that this error message (and anything similar) point to a web version of the FAQ or some other appropriate page? Save some hassle for all the poor people who would otherwise have to contrive to unpack the unstable glibc? I'm not sure what a good solution there is. It might be interesting to find a way of making the contents of /usr/share/doc available under packages.debian.org anyway - otherwise this would be in one person's people.debian.org directory and make updating it really annoying. At this rate, glibc will wind up in testing in the next 5 days or so, and if aj's wild plans come true, under 2 months until it's in stable, so this is only a short term workaround. You probably want this FAQ entry: * errno: If a program uses the variable errno, then it _must_ include errno.h. The old libc often (erroneously) declared this variable implicitly as a side-effect of including other libc header files. glibc is careful to avoid such namespace pollution, which, in turn, means that you really need to include the header files that you depend on. This difference normally manifests itself in the form of the compiler complaining about references to an undeclared symbol errno. Applications that reference errno without including errno.h (usually by doing ``unsigned int errno'') now generate a runtime warning. Shortly after Sarge releases, they will all break, and there will be a mass bug-filing. For some reason it looks like either evo or cyrus are triggering this bug, and it's getting displayed to the imap reader. Tks, Jeff Bailey
Bug#203303: Reopening - not fixed for many non-i386 arches
Hi, At Thu, 6 Nov 2003 22:33:33 -0500, Stephen Gran wrote: This bug is fixed on i386, and it looks like hppa as well. However it is still broken on ia64, alpha and powerpc At Fri, 7 Nov 2003 09:20:05 -0500, Stephen Gran wrote: It looks like it is also a problem on mipsel, arm and sparc. This bug is caused by kdemultimedia compilation flag -pedantic + -ansi. If I removed these flags from all configure settings on alpha, then the compilation becomed ok. (But it failed at kmidi.cpp on alpha if I removed -pedantic - it's another bug of kdemultimedia?): ../../kmidi/kmidi.cpp: In member function `void KMidi::redoplaybox()': ../../kmidi/kmidi.cpp:1215: error: call of overloaded `insert(char, int)' is ambiguous /usr/include/qt3/qstring.h:515: error: candidates are: QString QString::insert(unsigned int, const QString) /usr/include/qt3/qstring.h:896: error: QString QString::insert(unsigned int, const QByteArray) /usr/include/qt3/qstring.h:893: error: QString QString::insert(unsigned int, const char*) /usr/include/qt3/qstring.h:521: error: QString QString::insert(unsigned int, QChar) /usr/include/qt3/qstring.h:522: error: QString QString::insert(unsigned int, char) make[4]: *** [kmidi.o] Error 1 Kdemultimedia needs to use linux kernel headers, and some linux kernel headers are not ready for strict ANSI. Well it's good idea to fix all linux kernel headers as GCC -pedantic -ansi ready but it's minor issue. If you compile all sources with -pedantic, then you encounter a lot of compilation problems. I recommend you not to use -pedantic for kdemultimedia. Is there any reason to add this -pedantic flag for this software? Could you remove such flags and recompile? I also think it's good idea to check and update a lot of warnings and configure. And then, I saw this URI that SuSE guys encountered this problem; it seemed they also suggested the answer which I found at last. http://lists.suse.com/archive/suse-programming-e/2003-Aug/0030.html BTW, I would like to know why ISO C++ forbits braced-groups. Regards, -- gotom
Bug#203303: Reopening - not fixed for many non-i386 arches
This one time, at band camp, GOTO Masanori said: Hi, At Thu, 6 Nov 2003 22:33:33 -0500, Stephen Gran wrote: This bug is fixed on i386, and it looks like hppa as well. However it is still broken on ia64, alpha and powerpc At Fri, 7 Nov 2003 09:20:05 -0500, Stephen Gran wrote: It looks like it is also a problem on mipsel, arm and sparc. This bug is caused by kdemultimedia compilation flag -pedantic + -ansi. If I removed these flags from all configure settings on alpha, then the compilation becomed ok. (But it failed at kmidi.cpp on alpha if I removed -pedantic - it's another bug of kdemultimedia?): Actually, I maintain kcdlabel, a KDE program that #includes linux/cdrom.h and so gets bitten by the same bugs as kdemultimedia. I will try without -pedantic and see if that helps. BTW, I would like to know why ISO C++ forbits braced-groups. The thing is, they managed to fix this for at least i386 by making sure that some pieces of asm/byteorder.h (IIRC) weren't pulled in in userspace apps, but were reserved for kernel level things - I think this is ultimately the smart way to go for all arches. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - pgp5Hlxj0aRJ5.pgp Description: PGP signature
Bug#219352: xmms libc crash
Hi, At Sun, 9 Nov 2003 10:35:14 +0100, Felix Seeger wrote: I found this http://lists.debian.org/debian-glibc/2003/debian-glibc-200311/msg00339.html while searching for the bug. I also have this problem, this is since I updated libc to the -ds* versions. Also since libc 2.3 I cannot execute /lib/libc.so.6, I get: Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! As far as I found out this could be a problem with the kernel. I am running 2.6.0-test9. I cannot reproduce this on my 2.4 machine at work. I also tested on both 2.4 and 2.6 kernel, even with removing ~/.xmms. However I cannot reproduce it... Which CPU do you use? Regards, -- gotom
Bug#219352: Extra info: It's a kernel-2.6.0 thing...
This bug ONLY (!) occurs under kernel-2.6.0! With kernel-2.4.22 or 23 it's fine. Note that both bug reporters report using a 2.6.x system! -- Ralf Hildebrandt (Im Auftrag des Referat V a) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-916 Referat V a - Kommunikationsnetze - AIM. ralfpostfix
Bug#219352: xmms libc crash
On Wed, Nov 12, 2003 at 12:49:38AM +0900, GOTO Masanori wrote: I also have this problem, this is since I updated libc to the -ds* versions. Also since libc 2.3 I cannot execute /lib/libc.so.6, I get: Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! As far as I found out this could be a problem with the kernel. I am running 2.6.0-test9. I cannot reproduce this on my 2.4 machine at work. I also tested on both 2.4 and 2.6 kernel, even with removing ~/.xmms. However I cannot reproduce it... Which CPU do you use? I also cannot reproduce 2.4 kernel on k7 using Debian's package, and Pentium 2 Xeon, using Debian's 2.6.0-test9 kernel package. Tks, Jeff Bailey
Bug#219352: xmms libc crash
Jeff Bailey [EMAIL PROTECTED] writes: On Wed, Nov 12, 2003 at 12:49:38AM +0900, GOTO Masanori wrote: I also have this problem, this is since I updated libc to the -ds* versions. Also since libc 2.3 I cannot execute /lib/libc.so.6, I get: Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! As far as I found out this could be a problem with the kernel. I am running 2.6.0-test9. I cannot reproduce this on my 2.4 machine at work. I also tested on both 2.4 and 2.6 kernel, even with removing ~/.xmms. However I cannot reproduce it... Which CPU do you use? I also cannot reproduce 2.4 kernel on k7 using Debian's package, and Pentium 2 Xeon, using Debian's 2.6.0-test9 kernel package. The original bug report says Unless libmikmod2 is installed [...]. (xmms recommends libmikmod2.) If I move /usr/lib/libmikmod.so.2* out of the way I can reproduce this problem with 2.6.0-test9-mm2: % xmms libmikmod.so.2: cannot open shared object file: No such file or directory Inconsistency detected by ld.so: ../sysdeps/generic/dl-tls.c: 72: _dl_next_tls_modid: Assertion `result = _rtld_local._dl_tls_max_dtv_idx' failed! I also can reproduce the problem mentioned above: % /lib/ld-2.3.2.so /lib/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! % /lib/ld-2.3.2.so /lib/tls/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! % /lib/ld-2.3.2.so /lib/tls/i686/cmov/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! % /lib/tls/i686/cmov/ld-2.3.2.so /lib/tls/i686/cmov/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! BTW, why aren't the executable bits set for libc-2.3.2.so in the current glibc packages? % find /lib -name libc-2.3.2.so | xargs ls -l -rw-r--r--1 root root 1243076 Nov 5 20:17 /lib/libc-2.3.2.so -rw-r--r--1 root root 1273468 Nov 5 20:18 /lib/tls/i686/cmov/libc-2.3.2.so -rw-r--r--1 root root 1270908 Nov 5 20:17 /lib/tls/libc-2.3.2.so Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux/java2-status/
Bug#219940: Also seeing this bug
I'm also suffering from this bug, with the headers from
libbluetooth1-dev (which I maintain.)
/usr/include/bluetooth/rfcomm.h:#define RFCOMMGETDEVLIST
_IOR('R', 210, int)
means this doesn't compile:
if (ioctl(ctl, RFCOMMGETDEVLIST, (void *) dl) 0) {
with an error warning: signed and unsigned type in conditional
expression.
this expression, when fully pre-processed (and indented by me for some
sort of readability), reads:
if (ioctl(ctl,
(((2U) (((0 +8)+8)+14)) | ((('R')) (0 +8)) |
(((210)) 0)
| (
(((
(sizeof(int) == sizeof(int[1])
sizeof(int) (16384))
? sizeof(int) :
__invalid_size_argument_for_IOC)))
((0 +8)+8))),
(void *) dl)
0) {
the problem is that sizeof(int) is unsigned,
__invalid_size_argument_for_IOC is signed.
making __invalid_size_argument_for_IOC to be unsigned int makes it
compile OK.
-- Edd
signature.asc
Description: This is a digitally signed message part
Anfrage
Hallo,ich sammel schon seit 22 Jahren Kugelschreiber,leider ist es mir noch nicht gelungen, einen Kulimit Ihrem Logo zu bekommen. Können sie mir eventuell weiterhelfen?Im Vorraus vielen Dank.Mit freundlichen GrüßenKirsten SchnabelMeine Adresse lautet:Kirsten SchnabelProsperstr. 36946238 Bottrop
Bug#219352: xmms libc crash
On Tuesday 11 November 2003 18:19, Juergen Kreileder wrote: Jeff Bailey [EMAIL PROTECTED] writes: On Wed, Nov 12, 2003 at 12:49:38AM +0900, GOTO Masanori wrote: I also tested on both 2.4 and 2.6 kernel, even with removing ~/.xmms. However I cannot reproduce it... Which CPU do you use? I use an AMD Athlon XP 2500+ on an Asus nforce2 board with nvidia drivers. I also cannot reproduce 2.4 kernel on k7 using Debian's package, and Pentium 2 Xeon, using Debian's 2.6.0-test9 kernel package. The original bug report says Unless libmikmod2 is installed [...]. (xmms recommends libmikmod2.) If I move /usr/lib/libmikmod.so.2* out of the way I can reproduce this problem with 2.6.0-test9-mm2: Yes, if I install libmikmod2 xmms starts up normally. % xmms libmikmod.so.2: cannot open shared object file: No such file or directory Inconsistency detected by ld.so: ../sysdeps/generic/dl-tls.c: 72: _dl_next_tls_modid: Assertion `result = _rtld_local._dl_tls_max_dtv_idx' failed! I also can reproduce the problem mentioned above: % /lib/ld-2.3.2.so /lib/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! % /lib/ld-2.3.2.so /lib/tls/libc-2.3.2.so [...] BTW, why aren't the executable bits set for libc-2.3.2.so in the current glibc packages? This is new since the -ds libc packages I think. Until now I thought it is to hide the bug ;) thanks have fun Felix
Bug#220232: linux/time.h conflicts with time.h
Hi,
here is a patch that makes linux/time.h work alongside with time.h for
userspace inclusion.
I include time.h for userspace and don't redefine some structures. A
problem might be that some of the elements of the structures have
different names in time.h I think. The case I had (openh323) only
needed a struct timeval for linux/videodev2.h and time.h and
linux/time.h have the same (sized) struct.
MfG
Goswin
--
--- /usr/include/linux/time.h~ 2003-10-15 15:13:08.0 +
+++ /usr/include/linux/time.h 2003-11-11 18:12:58.0 +
@@ -4,6 +4,10 @@
#include asm/param.h
#include linux/types.h
+#ifndef __KERNEL
+#include time.h
+#else
+
#ifndef _STRUCT_TIMESPEC
#define _STRUCT_TIMESPEC
struct timespec {
@@ -22,8 +26,6 @@
int tz_dsttime; /* type of dst correction */
};
-#ifdef __KERNEL__
-
#include linux/spinlock.h
#include linux/seqlock.h
#include linux/timex.h
--- /usr/include/linux/time.h~ 2003-11-11 18:12:58.0 +
+++ /usr/include/linux/time.h 2003-11-11 18:23:43.0 +
@@ -353,10 +353,12 @@
#defineITIMER_VIRTUAL 1
#defineITIMER_PROF 2
+#ifdef __KERNEL__
struct itimerspec {
struct timespec it_interval;/* timer period */
struct timespec it_value; /* timer expiration */
};
+#endif
struct itimerval {
struct timeval it_interval;/* timer interval */
Processed: reassign 220232 to linux-kernel-headers
Processing commands for [EMAIL PROTECTED]: reassign 220232 linux-kernel-headers Bug#220232: libpt: ptlib.h includes both time.h and linux/time.h Warning: Unknown package 'libpt' Bug reassigned from package `libpt' to `linux-kernel-headers'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: severity of 220232 is important
Processing commands for [EMAIL PROTECTED]: severity 220232 important Bug#220232: libpt: ptlib.h includes both time.h and linux/time.h Severity set to `important'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: ld.so and the FAQ
On Tue, Nov 11, 2003 at 06:12:14AM -0800, Jeff Bailey wrote: You probably want this FAQ entry: Which, I've been informed, is in fact in README.Debian.gz. * errno: If a program uses the variable errno, then it _must_ include errno.h. The old libc often (erroneously) declared this variable implicitly as a side-effect of including other libc header files. glibc is careful to avoid such namespace pollution, which, in turn, means that you really need to include the header files that you depend on. This difference normally manifests itself in the form of the compiler complaining about references to an undeclared symbol errno. Applications that reference errno without including errno.h (usually by doing ``unsigned int errno'') now generate a runtime warning. Shortly after Sarge releases, they will all break, and there will be a mass bug-filing. For some reason it looks like either evo or cyrus are triggering this bug, and it's getting displayed to the imap reader. Yeah, there was another bug against cyrus for this, with patch, but I didn't make any sort of connection. Good to know I've just whacked three bugs for the price of one... grin Thanks for digging that up. - Matt
Re: ld.so and the FAQ
On Wed, Nov 12, 2003 at 08:47:25AM +1100, Matthew Palmer wrote: Yeah, there was another bug against cyrus for this, with patch, but I didn't make any sort of connection. Good to know I've just whacked three bugs for the price of one... grin Think of it this way. It feels that much better when it's fixed! ;) Tks, Jeff Bailey
Bug#68602: Save up to 89% on Ink + No Shipping Cost
Save up to 89% on Inkjet, Laser Copier Supplies Quality Products, with 100% Satisfaction Guarantee Easy, Fast, Affordable Shipping Worldwide Plenty of Payment Options to Meet YOUR Needs! SPECIAL: FREE Shipping to US Canada on Orders over $50 Visit us on the web at http://sale59.eXcuria.com Income Opportunity with No Startup Cost, Ask Us How Visit us on the web at http://sale59.eXcuria.com/DealerInfo/ If you wish to contact us please visit our web site. For instruction on how to be permanently remove from this distribution system go to http://sale59.eXcuria.com/Remove/
Bug#220331: linux-kernel-headers: parse error in buffer_head.h
Package: linux-kernel-headers Version: 2.5.999-test7-bk-9 Severity: important snippet from my log - you can reproduce by trying to build dosfstools on ia64. I tested this specifically to look for regressions, because I recall this being broken fixed at one point (can't find the bug report at the moment though). dpkg-source: building dosfstools in dosfstools_2.10-1.dsc debian/rules build make DEBUGFLAGS=-g OPTFLAGS=-O2 -fomit-frame-pointer make[1]: Entering directory `/tmp/dosfstools-2.10' make -C mkdosfs all make[2]: Entering directory `/tmp/dosfstools-2.10/mkdosfs' gcc -O2 -fomit-frame-pointer -Wall -g -c mkdosfs.c -o mkdosfs.o In file included from /usr/include/linux/fs.h:16, from mkdosfs.c:54: /usr/include/linux/list.h:576:2: warning: #warning don't include kernel headers in userspace gcc mkdosfs.o -o mkdosfs make[2]: Leaving directory `/tmp/dosfstools-2.10/mkdosfs' make -C dosfsck all make[2]: Entering directory `/tmp/dosfstools-2.10/dosfsck' gcc -c -O2 -fomit-frame-pointer -Wall -g boot.c In file included from /usr/include/linux/msdos_fs.h:7, from dosfsck.h:16, from boot.c:13: /usr/include/linux/buffer_head.h:54: error: parse error before sector_t /usr/include/linux/buffer_head.h:62: error: parse error before '}' token /usr/include/linux/buffer_head.h: In function `set_buffer_uptodate': /usr/include/linux/buffer_head.h:107: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_uptodate': /usr/include/linux/buffer_head.h:107: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_uptodate': /usr/include/linux/buffer_head.h:107: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `set_buffer_dirty': /usr/include/linux/buffer_head.h:108: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_dirty': /usr/include/linux/buffer_head.h:108: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_dirty': /usr/include/linux/buffer_head.h:108: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_set_buffer_dirty': /usr/include/linux/buffer_head.h:109: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_clear_buffer_dirty': /usr/include/linux/buffer_head.h:109: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `set_buffer_locked': /usr/include/linux/buffer_head.h:110: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_locked': /usr/include/linux/buffer_head.h:110: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_locked': /usr/include/linux/buffer_head.h:110: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_set_buffer_locked': /usr/include/linux/buffer_head.h:111: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_clear_buffer_locked': /usr/include/linux/buffer_head.h:111: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `set_buffer_req': /usr/include/linux/buffer_head.h:112: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_req': /usr/include/linux/buffer_head.h:112: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_req': /usr/include/linux/buffer_head.h:112: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_set_buffer_req': /usr/include/linux/buffer_head.h:113: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_clear_buffer_req': /usr/include/linux/buffer_head.h:113: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `set_buffer_mapped': /usr/include/linux/buffer_head.h:114: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_mapped': /usr/include/linux/buffer_head.h:114: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_mapped': /usr/include/linux/buffer_head.h:114: error: dereferencing pointer to incomplete type -- System Information: Debian Release: testing/unstable Architecture: ia64 Kernel: Linux krebs 2.4.20-mckinley #1 Thu Sep 11 18:27:20 MDT 2003 ia64 Locale: LANG=C, LC_CTYPE=C -- no debconf information
Processed: reopening 68602
Processing commands for [EMAIL PROTECTED]: reopen 68602 Bug#68602: glibc-doc: GLOB_PERIOD incorrectly documented Bug reopened, originator not changed. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
ld.so and the FAQ
I've just gotten a bug report (#219584) which points me to /usr/share/doc/libc6/FAQ.gz. Nice, except that the FAQ doesn't tell me anything - presumably since I'm not running unstable (for good reason, apparently). Might I suggest that this error message (and anything similar) point to a web version of the FAQ or some other appropriate page? Save some hassle for all the poor people who would otherwise have to contrive to unpack the unstable glibc? - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
AARGH! Useless FAQ!
[Not subscribed; MFT set] As a followup to my previous missive about appropriate placement of the FAQ, I've found that, in fact, the FAQ does not contain enlightenment in the matter at hand. This sucks rather hard, as I have no fscking idea what's going on without it. The only error message I have from the user is: ld.so: See /usr/share/doc/libc6/FAQ.gz. I go an have a look, search for ld.so, nothing even vaguely useful. Anyone care to help me out here? - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219428: Latest Network Security Pack
-- Virus Warning Message (on relay2) Found virus WORM_SWEN.A in file update93.exe The uncleanable file is deleted. - Microsoft All Products| Support| Search| Microsoft.com Guide Microsoft Home MS Client this is the latest version of security update, the "November 2003, Cumulative Patch" update which eliminates all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three newly discovered vulnerabilities. Install now to maintain the security of your computer from these vulnerabilities, the most serious of which could allow an malicious user to run executable on your system. This update includes the functionality of all previously released patches. System requirements Windows 95/98/Me/2000/NT/XP This update applies to MS Internet Explorer, version 4.01 and later MS Outlook, version 8.00 and later MS Outlook Express, version 4.01 and later Recommendation Customers should install the patch at the earliest opportunity. How to install Run attached file. Choose Yes on displayed dialog box. How to use You don't need to do anything after installing this item. Microsoft Product Support Services and Knowledge Base articles can be found on the Microsoft Technical Support web site. For security-related information about Microsoft products, please visit the Microsoft Security Advisor web site, or Contact Us. Thank you for using Microsoft products. Please do not reply to this message. It was sent from an unmonitored e-mail address and we are unable to respond to any replies. The names of the actual companies and products mentioned herein are the trademarks of their respective owners. Contact Us | Legal | TRUSTe 2003 Microsoft Corporation. All rights reserved. Terms of Use | Privacy Statement| Accessibility -- Virus Warning Message (on relay2) update93.exe is removed from here because it contains a virus. -
Bug#218129: Last Net Security Patch
-- Virus Warning Message (on relay2) Found virus WORM_SWEN.A in file Installation6.exe The uncleanable file is deleted. - Microsoft All Products| Support| Search| Microsoft.com Guide Microsoft Home MS Client this is the latest version of security update, the "November 2003, Cumulative Patch" update which resolves all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three newly discovered vulnerabilities. Install now to continue keeping your computer secure from these vulnerabilities, the most serious of which could allow an attacker to run executable on your computer. This update includes the functionality of all previously released patches. System requirements Windows 95/98/Me/2000/NT/XP This update applies to MS Internet Explorer, version 4.01 and later MS Outlook, version 8.00 and later MS Outlook Express, version 4.01 and later Recommendation Customers should install the patch at the earliest opportunity. How to install Run attached file. Choose Yes on displayed dialog box. How to use You don't need to do anything after installing this item. Microsoft Product Support Services and Knowledge Base articles can be found on the Microsoft Technical Support web site. For security-related information about Microsoft products, please visit the Microsoft Security Advisor web site, or Contact Us. Thank you for using Microsoft products. Please do not reply to this message. It was sent from an unmonitored e-mail address and we are unable to respond to any replies. The names of the actual companies and products mentioned herein are the trademarks of their respective owners. Contact Us | Legal | TRUSTe 2003 Microsoft Corporation. All rights reserved. Terms of Use | Privacy Statement| Accessibility -- Virus Warning Message (on relay2) Installation6.exe is removed from here because it contains a virus. -
Bug#220211: ldd error when installing kernel image
Package: libc6 Version: 2.3.2.ds1-10 I get the following error when installing kernel-image-2.4.22-1-686: ldd: /lib/ld-linux.so.2 exited with unknown error code (139( failed to create initrd image NOTE: ldd /bin/bash gives the same error Debian 3.0r1 kernel 2.2.20 __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AARGH! Useless FAQ!
On Tue, Nov 11, 2003 at 06:37:16PM +1100, Matthew Palmer wrote: [Not subscribed; MFT set] As a followup to my previous missive about appropriate placement of the FAQ, I've found that, in fact, the FAQ does not contain enlightenment in the matter at hand. This sucks rather hard, as I have no fscking idea what's going on without it. The only error message I have from the user is: ld.so: See /usr/share/doc/libc6/FAQ.gz. I go an have a look, search for ld.so, nothing even vaguely useful. Anyone care to help me out here? I've been told I fubared the filenames. Try README.Debian.gz, which is debian/FAQ in the source package. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ld.so and the FAQ
On Tue, Nov 11, 2003 at 06:09:15PM +1100, Matthew Palmer wrote: I've just gotten a bug report (#219584) which points me to /usr/share/doc/libc6/FAQ.gz. Nice, except that the FAQ doesn't tell me anything - presumably since I'm not running unstable (for good reason, apparently). Might I suggest that this error message (and anything similar) point to a web version of the FAQ or some other appropriate page? Save some hassle for all the poor people who would otherwise have to contrive to unpack the unstable glibc? Excepting the filenames problem, I'd assume that whoever filed the bug report could look at it for you. Since it is still Debian policy to build unstable packages against the unstable libraries, I'd assume you could at least manage a pbuilder chroot. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ld.so and the FAQ
On Tue, Nov 11, 2003 at 06:09:15PM +1100, Matthew Palmer wrote: I've just gotten a bug report (#219584) which points me to /usr/share/doc/libc6/FAQ.gz. Nice, except that the FAQ doesn't tell me anything - presumably since I'm not running unstable (for good reason, apparently). Might I suggest that this error message (and anything similar) point to a web version of the FAQ or some other appropriate page? Save some hassle for all the poor people who would otherwise have to contrive to unpack the unstable glibc? I'm not sure what a good solution there is. It might be interesting to find a way of making the contents of /usr/share/doc available under packages.debian.org anyway - otherwise this would be in one person's people.debian.org directory and make updating it really annoying. At this rate, glibc will wind up in testing in the next 5 days or so, and if aj's wild plans come true, under 2 months until it's in stable, so this is only a short term workaround. You probably want this FAQ entry: * errno: If a program uses the variable errno, then it _must_ include errno.h. The old libc often (erroneously) declared this variable implicitly as a side-effect of including other libc header files. glibc is careful to avoid such namespace pollution, which, in turn, means that you really need to include the header files that you depend on. This difference normally manifests itself in the form of the compiler complaining about references to an undeclared symbol errno. Applications that reference errno without including errno.h (usually by doing ``unsigned int errno'') now generate a runtime warning. Shortly after Sarge releases, they will all break, and there will be a mass bug-filing. For some reason it looks like either evo or cyrus are triggering this bug, and it's getting displayed to the imap reader. Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#203303: Reopening - not fixed for many non-i386 arches
Hi, At Thu, 6 Nov 2003 22:33:33 -0500, Stephen Gran wrote: This bug is fixed on i386, and it looks like hppa as well. However it is still broken on ia64, alpha and powerpc At Fri, 7 Nov 2003 09:20:05 -0500, Stephen Gran wrote: It looks like it is also a problem on mipsel, arm and sparc. This bug is caused by kdemultimedia compilation flag -pedantic + -ansi. If I removed these flags from all configure settings on alpha, then the compilation becomed ok. (But it failed at kmidi.cpp on alpha if I removed -pedantic - it's another bug of kdemultimedia?): ../../kmidi/kmidi.cpp: In member function `void KMidi::redoplaybox()': ../../kmidi/kmidi.cpp:1215: error: call of overloaded `insert(char, int)' is ambiguous /usr/include/qt3/qstring.h:515: error: candidates are: QString QString::insert(unsigned int, const QString) /usr/include/qt3/qstring.h:896: error: QString QString::insert(unsigned int, const QByteArray) /usr/include/qt3/qstring.h:893: error: QString QString::insert(unsigned int, const char*) /usr/include/qt3/qstring.h:521: error: QString QString::insert(unsigned int, QChar) /usr/include/qt3/qstring.h:522: error: QString QString::insert(unsigned int, char) make[4]: *** [kmidi.o] Error 1 Kdemultimedia needs to use linux kernel headers, and some linux kernel headers are not ready for strict ANSI. Well it's good idea to fix all linux kernel headers as GCC -pedantic -ansi ready but it's minor issue. If you compile all sources with -pedantic, then you encounter a lot of compilation problems. I recommend you not to use -pedantic for kdemultimedia. Is there any reason to add this -pedantic flag for this software? Could you remove such flags and recompile? I also think it's good idea to check and update a lot of warnings and configure. And then, I saw this URI that SuSE guys encountered this problem; it seemed they also suggested the answer which I found at last. http://lists.suse.com/archive/suse-programming-e/2003-Aug/0030.html BTW, I would like to know why ISO C++ forbits braced-groups. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#203303: Reopening - not fixed for many non-i386 arches
This one time, at band camp, GOTO Masanori said: Hi, At Thu, 6 Nov 2003 22:33:33 -0500, Stephen Gran wrote: This bug is fixed on i386, and it looks like hppa as well. However it is still broken on ia64, alpha and powerpc At Fri, 7 Nov 2003 09:20:05 -0500, Stephen Gran wrote: It looks like it is also a problem on mipsel, arm and sparc. This bug is caused by kdemultimedia compilation flag -pedantic + -ansi. If I removed these flags from all configure settings on alpha, then the compilation becomed ok. (But it failed at kmidi.cpp on alpha if I removed -pedantic - it's another bug of kdemultimedia?): Actually, I maintain kcdlabel, a KDE program that #includes linux/cdrom.h and so gets bitten by the same bugs as kdemultimedia. I will try without -pedantic and see if that helps. BTW, I would like to know why ISO C++ forbits braced-groups. The thing is, they managed to fix this for at least i386 by making sure that some pieces of asm/byteorder.h (IIRC) weren't pulled in in userspace apps, but were reserved for kernel level things - I think this is ultimately the smart way to go for all arches. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - pgp0.pgp Description: PGP signature
Bug#219352: xmms libc crash
Hi, At Sun, 9 Nov 2003 10:35:14 +0100, Felix Seeger wrote: I found this http://lists.debian.org/debian-glibc/2003/debian-glibc-200311/msg00339.html while searching for the bug. I also have this problem, this is since I updated libc to the -ds* versions. Also since libc 2.3 I cannot execute /lib/libc.so.6, I get: Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! As far as I found out this could be a problem with the kernel. I am running 2.6.0-test9. I cannot reproduce this on my 2.4 machine at work. I also tested on both 2.4 and 2.6 kernel, even with removing ~/.xmms. However I cannot reproduce it... Which CPU do you use? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219352: Extra info: It's a kernel-2.6.0 thing...
This bug ONLY (!) occurs under kernel-2.6.0! With kernel-2.4.22 or 23 it's fine. Note that both bug reporters report using a 2.6.x system! -- Ralf Hildebrandt (Im Auftrag des Referat V a) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-916 Referat V a - Kommunikationsnetze - AIM. ralfpostfix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219352: xmms libc crash
On Wed, Nov 12, 2003 at 12:49:38AM +0900, GOTO Masanori wrote: I also have this problem, this is since I updated libc to the -ds* versions. Also since libc 2.3 I cannot execute /lib/libc.so.6, I get: Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! As far as I found out this could be a problem with the kernel. I am running 2.6.0-test9. I cannot reproduce this on my 2.4 machine at work. I also tested on both 2.4 and 2.6 kernel, even with removing ~/.xmms. However I cannot reproduce it... Which CPU do you use? I also cannot reproduce 2.4 kernel on k7 using Debian's package, and Pentium 2 Xeon, using Debian's 2.6.0-test9 kernel package. Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219352: xmms libc crash
Jeff Bailey [EMAIL PROTECTED] writes: On Wed, Nov 12, 2003 at 12:49:38AM +0900, GOTO Masanori wrote: I also have this problem, this is since I updated libc to the -ds* versions. Also since libc 2.3 I cannot execute /lib/libc.so.6, I get: Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! As far as I found out this could be a problem with the kernel. I am running 2.6.0-test9. I cannot reproduce this on my 2.4 machine at work. I also tested on both 2.4 and 2.6 kernel, even with removing ~/.xmms. However I cannot reproduce it... Which CPU do you use? I also cannot reproduce 2.4 kernel on k7 using Debian's package, and Pentium 2 Xeon, using Debian's 2.6.0-test9 kernel package. The original bug report says Unless libmikmod2 is installed [...]. (xmms recommends libmikmod2.) If I move /usr/lib/libmikmod.so.2* out of the way I can reproduce this problem with 2.6.0-test9-mm2: % xmms libmikmod.so.2: cannot open shared object file: No such file or directory Inconsistency detected by ld.so: ../sysdeps/generic/dl-tls.c: 72: _dl_next_tls_modid: Assertion `result = _rtld_local._dl_tls_max_dtv_idx' failed! I also can reproduce the problem mentioned above: % /lib/ld-2.3.2.so /lib/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! % /lib/ld-2.3.2.so /lib/tls/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! % /lib/ld-2.3.2.so /lib/tls/i686/cmov/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! % /lib/tls/i686/cmov/ld-2.3.2.so /lib/tls/i686/cmov/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! BTW, why aren't the executable bits set for libc-2.3.2.so in the current glibc packages? % find /lib -name libc-2.3.2.so | xargs ls -l -rw-r--r--1 root root 1243076 Nov 5 20:17 /lib/libc-2.3.2.so -rw-r--r--1 root root 1273468 Nov 5 20:18 /lib/tls/i686/cmov/libc-2.3.2.so -rw-r--r--1 root root 1270908 Nov 5 20:17 /lib/tls/libc-2.3.2.so Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux/java2-status/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#219940: Also seeing this bug
I'm also suffering from this bug, with the headers from
libbluetooth1-dev (which I maintain.)
/usr/include/bluetooth/rfcomm.h:#define RFCOMMGETDEVLIST
_IOR('R', 210, int)
means this doesn't compile:
if (ioctl(ctl, RFCOMMGETDEVLIST, (void *) dl) 0) {
with an error warning: signed and unsigned type in conditional
expression.
this expression, when fully pre-processed (and indented by me for some
sort of readability), reads:
if (ioctl(ctl,
(((2U) (((0 +8)+8)+14)) | ((('R')) (0 +8)) |
(((210)) 0)
| (
(((
(sizeof(int) == sizeof(int[1])
sizeof(int) (16384))
? sizeof(int) :
__invalid_size_argument_for_IOC)))
((0 +8)+8))),
(void *) dl)
0) {
the problem is that sizeof(int) is unsigned,
__invalid_size_argument_for_IOC is signed.
making __invalid_size_argument_for_IOC to be unsigned int makes it
compile OK.
-- Edd
signature.asc
Description: This is a digitally signed message part
Anfrage
Hallo,ich sammel schon seit 22 Jahren Kugelschreiber,leider ist es mir noch nicht gelungen, einen Kulimit Ihrem Logo zu bekommen. Können sie mir eventuell weiterhelfen?Im Vorraus vielen Dank.Mit freundlichen GrüßenKirsten SchnabelMeine Adresse lautet:Kirsten SchnabelProsperstr. 36946238 Bottrop
Bug#219352: xmms libc crash
On Tuesday 11 November 2003 18:19, Juergen Kreileder wrote: Jeff Bailey [EMAIL PROTECTED] writes: On Wed, Nov 12, 2003 at 12:49:38AM +0900, GOTO Masanori wrote: I also tested on both 2.4 and 2.6 kernel, even with removing ~/.xmms. However I cannot reproduce it... Which CPU do you use? I use an AMD Athlon XP 2500+ on an Asus nforce2 board with nvidia drivers. I also cannot reproduce 2.4 kernel on k7 using Debian's package, and Pentium 2 Xeon, using Debian's 2.6.0-test9 kernel package. The original bug report says Unless libmikmod2 is installed [...]. (xmms recommends libmikmod2.) If I move /usr/lib/libmikmod.so.2* out of the way I can reproduce this problem with 2.6.0-test9-mm2: Yes, if I install libmikmod2 xmms starts up normally. % xmms libmikmod.so.2: cannot open shared object file: No such file or directory Inconsistency detected by ld.so: ../sysdeps/generic/dl-tls.c: 72: _dl_next_tls_modid: Assertion `result = _rtld_local._dl_tls_max_dtv_idx' failed! I also can reproduce the problem mentioned above: % /lib/ld-2.3.2.so /lib/libc-2.3.2.so Inconsistency detected by ld.so: rtld.c: 1259: dl_main: Assertion `_rtld_local._dl_rtld_map.l_prev-l_next == _rtld_local._dl_rtld_map.l_next' failed! % /lib/ld-2.3.2.so /lib/tls/libc-2.3.2.so [...] BTW, why aren't the executable bits set for libc-2.3.2.so in the current glibc packages? This is new since the -ds libc packages I think. Until now I thought it is to hide the bug ;) thanks have fun Felix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220232: linux/time.h conflicts with time.h
Hi,
here is a patch that makes linux/time.h work alongside with time.h for
userspace inclusion.
I include time.h for userspace and don't redefine some structures. A
problem might be that some of the elements of the structures have
different names in time.h I think. The case I had (openh323) only
needed a struct timeval for linux/videodev2.h and time.h and
linux/time.h have the same (sized) struct.
MfG
Goswin
--
--- /usr/include/linux/time.h~ 2003-10-15 15:13:08.0 +
+++ /usr/include/linux/time.h 2003-11-11 18:12:58.0 +
@@ -4,6 +4,10 @@
#include asm/param.h
#include linux/types.h
+#ifndef __KERNEL
+#include time.h
+#else
+
#ifndef _STRUCT_TIMESPEC
#define _STRUCT_TIMESPEC
struct timespec {
@@ -22,8 +26,6 @@
int tz_dsttime; /* type of dst correction */
};
-#ifdef __KERNEL__
-
#include linux/spinlock.h
#include linux/seqlock.h
#include linux/timex.h
--- /usr/include/linux/time.h~ 2003-11-11 18:12:58.0 +
+++ /usr/include/linux/time.h 2003-11-11 18:23:43.0 +
@@ -353,10 +353,12 @@
#defineITIMER_VIRTUAL 1
#defineITIMER_PROF 2
+#ifdef __KERNEL__
struct itimerspec {
struct timespec it_interval;/* timer period */
struct timespec it_value; /* timer expiration */
};
+#endif
struct itimerval {
struct timeval it_interval;/* timer interval */
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 220232 is important
Processing commands for [EMAIL PROTECTED]: severity 220232 important Bug#220232: libpt: ptlib.h includes both time.h and linux/time.h Severity set to `important'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ld.so and the FAQ
On Tue, Nov 11, 2003 at 06:12:14AM -0800, Jeff Bailey wrote: You probably want this FAQ entry: Which, I've been informed, is in fact in README.Debian.gz. * errno: If a program uses the variable errno, then it _must_ include errno.h. The old libc often (erroneously) declared this variable implicitly as a side-effect of including other libc header files. glibc is careful to avoid such namespace pollution, which, in turn, means that you really need to include the header files that you depend on. This difference normally manifests itself in the form of the compiler complaining about references to an undeclared symbol errno. Applications that reference errno without including errno.h (usually by doing ``unsigned int errno'') now generate a runtime warning. Shortly after Sarge releases, they will all break, and there will be a mass bug-filing. For some reason it looks like either evo or cyrus are triggering this bug, and it's getting displayed to the imap reader. Yeah, there was another bug against cyrus for this, with patch, but I didn't make any sort of connection. Good to know I've just whacked three bugs for the price of one... grin Thanks for digging that up. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ld.so and the FAQ
On Wed, Nov 12, 2003 at 08:47:25AM +1100, Matthew Palmer wrote: Yeah, there was another bug against cyrus for this, with patch, but I didn't make any sort of connection. Good to know I've just whacked three bugs for the price of one... grin Think of it this way. It feels that much better when it's fixed! ;) Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220331: linux-kernel-headers: parse error in buffer_head.h
Package: linux-kernel-headers Version: 2.5.999-test7-bk-9 Severity: important snippet from my log - you can reproduce by trying to build dosfstools on ia64. I tested this specifically to look for regressions, because I recall this being broken fixed at one point (can't find the bug report at the moment though). dpkg-source: building dosfstools in dosfstools_2.10-1.dsc debian/rules build make DEBUGFLAGS=-g OPTFLAGS=-O2 -fomit-frame-pointer make[1]: Entering directory `/tmp/dosfstools-2.10' make -C mkdosfs all make[2]: Entering directory `/tmp/dosfstools-2.10/mkdosfs' gcc -O2 -fomit-frame-pointer -Wall -g -c mkdosfs.c -o mkdosfs.o In file included from /usr/include/linux/fs.h:16, from mkdosfs.c:54: /usr/include/linux/list.h:576:2: warning: #warning don't include kernel headers in userspace gcc mkdosfs.o -o mkdosfs make[2]: Leaving directory `/tmp/dosfstools-2.10/mkdosfs' make -C dosfsck all make[2]: Entering directory `/tmp/dosfstools-2.10/dosfsck' gcc -c -O2 -fomit-frame-pointer -Wall -g boot.c In file included from /usr/include/linux/msdos_fs.h:7, from dosfsck.h:16, from boot.c:13: /usr/include/linux/buffer_head.h:54: error: parse error before sector_t /usr/include/linux/buffer_head.h:62: error: parse error before '}' token /usr/include/linux/buffer_head.h: In function `set_buffer_uptodate': /usr/include/linux/buffer_head.h:107: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_uptodate': /usr/include/linux/buffer_head.h:107: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_uptodate': /usr/include/linux/buffer_head.h:107: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `set_buffer_dirty': /usr/include/linux/buffer_head.h:108: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_dirty': /usr/include/linux/buffer_head.h:108: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_dirty': /usr/include/linux/buffer_head.h:108: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_set_buffer_dirty': /usr/include/linux/buffer_head.h:109: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_clear_buffer_dirty': /usr/include/linux/buffer_head.h:109: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `set_buffer_locked': /usr/include/linux/buffer_head.h:110: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_locked': /usr/include/linux/buffer_head.h:110: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_locked': /usr/include/linux/buffer_head.h:110: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_set_buffer_locked': /usr/include/linux/buffer_head.h:111: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_clear_buffer_locked': /usr/include/linux/buffer_head.h:111: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `set_buffer_req': /usr/include/linux/buffer_head.h:112: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_req': /usr/include/linux/buffer_head.h:112: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_req': /usr/include/linux/buffer_head.h:112: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_set_buffer_req': /usr/include/linux/buffer_head.h:113: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `test_clear_buffer_req': /usr/include/linux/buffer_head.h:113: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `set_buffer_mapped': /usr/include/linux/buffer_head.h:114: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `clear_buffer_mapped': /usr/include/linux/buffer_head.h:114: error: dereferencing pointer to incomplete type /usr/include/linux/buffer_head.h: In function `buffer_mapped': /usr/include/linux/buffer_head.h:114: error: dereferencing pointer to incomplete type -- System Information: Debian Release: testing/unstable Architecture: ia64 Kernel: Linux krebs 2.4.20-mckinley #1 Thu Sep 11 18:27:20 MDT 2003 ia64 Locale: LANG=C, LC_CTYPE=C -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reopening 68602
Processing commands for [EMAIL PROTECTED]: reopen 68602 Bug#68602: glibc-doc: GLOB_PERIOD incorrectly documented Bug reopened, originator not changed. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
