public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: Taw <tau_xxx@yahoo.com>
Cc: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: Glibc 2.12.0 and 2.12.1 compatiblity
Date: Sun, 27 Aug 2023 14:05:47 +0200	[thread overview]
Message-ID: <cc7f7962-a541-25d9-b272-a662383083a7@starynkevitch.net> (raw)
In-Reply-To: <46297152.997095.1693136296744@mail.yahoo.com>


On 8/27/23 13:38, Taw via Libc-help wrote:
> Hello,I have a short question: If I build something with glibc 2.12.1 (using crosstool-ng), will it work on computers which have glibc 2.12.0 installed?
> I chechked the diff between the sources but I am not that knowledgeable about glibc so a more advisable opinion with be more helpful.


Yes in most of the cases. You didn't explain what your program is doing, 
and how critical it is, and what is your computer hardware.


The rare differences would be if your program depend (implicitly) on 
some buggy behavior of Glibc 2.12.0 which has been improved in Glibc 2.12.1

There could also be operating system differences. For example, if your 
program uses popen to run a program available on one computer, but not 
on the other.

Or if your program fopen-s a file which is present on one computer and 
not on the other.

Regards from near Paris in France


NB my pet open source project is the RefPerSys inference engine on 
https://github.com/RefPerSys/RefPerSys/ - contributors are welcome.

-- 
Basile Starynkevitch                  <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/


      reply	other threads:[~2023-08-27 12:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46297152.997095.1693136296744.ref@mail.yahoo.com>
2023-08-27 11:38 ` Taw
2023-08-27 12:05   ` Basile Starynkevitch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc7f7962-a541-25d9-b272-a662383083a7@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=libc-help@sourceware.org \
    --cc=tau_xxx@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).