I second this (rather old) wish.
I've been bitten by it today when installing udev on my laptop and
bind-mounting /udev (which is itself a tmpfs mount) over /dev. To get around
it, I renamed /etc/rcS.d/S35devpts.sh to .../S38devpts.sh (and did a few
other things which aren't relevant here).
(libc
I second this (rather old) wish.
I've been bitten by it today when installing udev on my laptop and
bind-mounting /udev (which is itself a tmpfs mount) over /dev. To get around
it, I renamed /etc/rcS.d/S35devpts.sh to .../S38devpts.sh (and did a few
other things which aren't relevant here).
(libc
Your message dated Fri, 16 Jan 2004 14:40:15 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#222709: */time.h: Some one is not using _STRUCT_TIMEVAL.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Fri, 16 Jan 2004 14:38:02 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221156: libc6: segfault in dlerror (on sparc)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Fri, 16 Jan 2004 14:40:15 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#222709: */time.h: Some one is not using _STRUCT_TIMEVAL.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Fri, 16 Jan 2004 14:38:02 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221156: libc6: segfault in dlerror (on sparc)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Repository: linux-kernel-headers/debian
who:dan
time: Fri Jan 16 11:32:21 MST 2004
Log Message:
Add sparc patch.
Files:
changed:changelog
Repository: linux-kernel-headers/debian/patches
who:dan
time: Fri Jan 16 11:32:21 MST 2004
Log Message:
Add sparc patch.
Files:
added: sparc-asm-elf.patch
Repository: linux-kernel-headers/debian
who:dan
time: Fri Jan 16 11:32:21 MST 2004
Log Message:
Add sparc patch.
Files:
changed:changelog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Repository: linux-kernel-headers/debian/patches
who:dan
time: Fri Jan 16 11:32:21 MST 2004
Log Message:
Add sparc patch.
Files:
added: sparc-asm-elf.patch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Jan 16, 2004 at 09:47:02AM +0300, Vladimir Prus wrote:
> Daniel Jacobowitz
>
> > > Vladimir Prus wrote:
> > > > Hello,
> > > > I have a small example where use of -static-libgcc and -Wl,-Bstatic
> > > > flags cause ld.so do assert.
> > > >
> > > > I have file app.cpp containing
> > > >
> >
On Fri, Jan 16, 2004 at 01:13:09PM +0900, GOTO Masanori wrote:
>
> Please test with the latest mozilla.
Works now.
On Fri, Jan 16, 2004 at 09:47:02AM +0300, Vladimir Prus wrote:
> Daniel Jacobowitz
>
> > > Vladimir Prus wrote:
> > > > Hello,
> > > > I have a small example where use of -static-libgcc and -Wl,-Bstatic
> > > > flags cause ld.so do assert.
> > > >
> > > > I have file app.cpp containing
> > > >
> >
On Fri, Jan 16, 2004 at 01:13:09PM +0900, GOTO Masanori wrote:
>
> Please test with the latest mozilla.
Works now.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--- GOTO Masanori <[EMAIL PROTECTED]> wrote:
> At Tue, 02 Dec 2003 07:31:03 -0600,
> Mike Mestnik wrote:
> > This is what I get from...
> > #include
> > #include
>
> Please provide us the complete test program to show your bug report.
HEHE, that was the test program!
It's the pre-compiler that
Greetings, and thanks for your reply! OK consider the following
sequence of commands, on woody (works) and on sid (broken):
=
woody
=
intech19:/mn
--- GOTO Masanori <[EMAIL PROTECTED]> wrote:
> At Tue, 02 Dec 2003 07:31:03 -0600,
> Mike Mestnik wrote:
> > This is what I get from...
> > #include
> > #include
>
> Please provide us the complete test program to show your bug report.
HEHE, that was the test program!
It's the pre-compiler that
Greetings, and thanks for your reply! OK consider the following
sequence of commands, on woody (works) and on sid (broken):
=
woody
=
intech19:/mn
Your message dated Fri, 16 Jan 2004 13:52:53 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#224135: libc6: suggests non-existant package
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Fri, 16 Jan 2004 13:45:43 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#202835: /lib/libc-2.3.1.so: Want i686 optimized build
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Fri, 16 Jan 2004 13:26:45 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218508: libc6: mprotect does not work any more on
lic6-2.3.2.ds8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Repository: glibc-package/debian
who:gotom
time: Thu Jan 15 21:38:26 MST 2004
Log Message:
- debian/po/nl.po: Update nl debconf template translation.
Patched by cobaco <[EMAIL PROTECTED]>. (Closes: #220693)
Files:
changed:changelog
Repository: glibc-package/debian/po
who:gotom
time: Thu Jan 15 21:38:26 MST 2004
Log Message:
- debian/po/nl.po: Update nl debconf template translation.
Patched by cobaco <[EMAIL PROTECTED]>. (Closes: #220693)
Files:
changed:nl.po
Your message dated Fri, 16 Jan 2004 13:15:59 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219705: Sendmail problems
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your resp
Your message dated Fri, 16 Jan 2004 13:52:53 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#224135: libc6: suggests non-existant package
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Processing commands for [EMAIL PROTECTED]:
> reassign 228002 libc6
Bug#228002: too many symlinks
Bug reassigned from package `atlas2-3dnow' to `libc6'.
> severity 228002 important
Bug#228002: too many symlinks
Severity set to `important'.
> merge 228002 225397
Bug#225397: ldconfig installs link
Your message dated Fri, 16 Jan 2004 13:45:43 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#202835: /lib/libc-2.3.1.so: Want i686 optimized build
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Fri, 16 Jan 2004 13:26:45 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#218508: libc6: mprotect does not work any more on lic6-2.3.2.ds8
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Repository: glibc-package/debian
who:gotom
time: Thu Jan 15 21:38:26 MST 2004
Log Message:
- debian/po/nl.po: Update nl debconf template translation.
Patched by cobaco <[EMAIL PROTECTED]>. (Closes: #220693)
Files:
changed:changelog
--
To UNSUBSCRIBE, email to
Repository: glibc-package/debian/po
who:gotom
time: Thu Jan 15 21:38:26 MST 2004
Log Message:
- debian/po/nl.po: Update nl debconf template translation.
Patched by cobaco <[EMAIL PROTECTED]>. (Closes: #220693)
Files:
changed:nl.po
--
To UNSUBSCRIBE, email to
Your message dated Fri, 16 Jan 2004 13:15:59 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#219705: Sendmail problems
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your resp
Processing commands for [EMAIL PROTECTED]:
> reassign 228002 libc6
Bug#228002: too many symlinks
Bug reassigned from package `atlas2-3dnow' to `libc6'.
> severity 228002 important
Bug#228002: too many symlinks
Severity set to `important'.
> merge 228002 225397
Bug#225397: ldconfig installs link
Daniel Jacobowitz
> > Vladimir Prus wrote:
> > > Hello,
> > > I have a small example where use of -static-libgcc and -Wl,-Bstatic
> > > flags cause ld.so do assert.
> > >
> > > I have file app.cpp containing
> > >
> > >int main() { return 0; }
> > >
> > > and lib.cpp, which is empty. I compile
GOTO Masanori wrote:
> > and lib.cpp, which is empty. I compile them with
> >
> >g++ -o lib.so -shared -static-libgcc lib.cpp -Wl,-Bstatic
> >g++ -o app app.cpp lib.so -static-libgcc -Wl,-Bstatic
> >
> > and when I run "./app", I get:
> >
> > Inconsistency detected by ld.so: dl-fini.c:
Daniel Jacobowitz
> > Vladimir Prus wrote:
> > > Hello,
> > > I have a small example where use of -static-libgcc and -Wl,-Bstatic
> > > flags cause ld.so do assert.
> > >
> > > I have file app.cpp containing
> > >
> > >int main() { return 0; }
> > >
> > > and lib.cpp, which is empty. I compile
GOTO Masanori wrote:
> > and lib.cpp, which is empty. I compile them with
> >
> >g++ -o lib.so -shared -static-libgcc lib.cpp -Wl,-Bstatic
> >g++ -o app app.cpp lib.so -static-libgcc -Wl,-Bstatic
> >
> > and when I run "./app", I get:
> >
> > Inconsistency detected by ld.so: dl-fini.c:
36 matches
Mail list logo
