public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/10251] New: Glibc should be back and forward compatible
@ 2009-06-07 19:47 dandart at googlemail dot com
2009-06-08 0:17 ` [Bug libc/10251] " pasky at suse dot cz
0 siblings, 1 reply; 3+ messages in thread
From: dandart at googlemail dot com @ 2009-06-07 19:47 UTC (permalink / raw)
To: glibc-bugs
It is a known fact that Windows XP can run applications from Windows 95 or even
earlier. That is 6 years earlier, or greater.
Linux should have a mechanism in which it can run native apps compiled for the
same architecture but with earlier or later Glibc versions, therefore enabling
binary distribution to work indefinitely. Earlier may be a challenge, seeing as
major code blocks that may be required in 2.11 to run programs may not be
present in 2.2, but at least running older programs on a newer libc would not be
impossible.
This will have the effect of either having a medium to large code change, or
stabilising the system. Stability is a good thing and will ensure things won't
break. If someone made a package 5 years ago only in binary form and it doesn't
run or cannot compile today, that is a major blow for compatibility. It may be
that other apps besides glibc are affected, and they should be similarly adapted.
I cannot unfortunately code this well, I would help if I could, but I will
spread this if this bug is accepted.
Assigned Critical as new versions break things. Sorry if it bugs you.
Thanks
--
Summary: Glibc should be back and forward compatible
Product: glibc
Version: unspecified
Status: NEW
Severity: critical
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: dandart at googlemail dot com
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10251
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/10251] Glibc should be back and forward compatible
2009-06-07 19:47 [Bug libc/10251] New: Glibc should be back and forward compatible dandart at googlemail dot com
@ 2009-06-08 0:17 ` pasky at suse dot cz
0 siblings, 0 replies; 3+ messages in thread
From: pasky at suse dot cz @ 2009-06-08 0:17 UTC (permalink / raw)
To: glibc-bugs
------- Additional Comments From pasky at suse dot cz 2009-06-08 00:17 -------
glibc is fully backwards-compatible between minor versions. If something
particular does not work for you, please open a concrete bug. Thank you.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
http://sourceware.org/bugzilla/show_bug.cgi?id=10251
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/10251] Glibc should be back and forward compatible
[not found] <bug-10251-131@http.sourceware.org/bugzilla/>
@ 2014-07-01 16:39 ` fweimer at redhat dot com
0 siblings, 0 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2014-07-01 16:39 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=10251
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-07-01 16:39 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-06-07 19:47 [Bug libc/10251] New: Glibc should be back and forward compatible dandart at googlemail dot com
2009-06-08 0:17 ` [Bug libc/10251] " pasky at suse dot cz
[not found] <bug-10251-131@http.sourceware.org/bugzilla/>
2014-07-01 16:39 ` fweimer at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).