From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: <ushakov@baltbank.ru>
Cc: <help-gcc@gnu.org>
Subject: Re: object files portability issues
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <ord7qgweak.fsf@garnize.lsd.ic.unicamp.br> (raw)
Message-ID: <20000401000000.8UWco6mq6t5lQNyLoOi07l_xgs9FuwnaesNQ54DZL98@z> (raw)
In-Reply-To: <000001bf6c8c$a5f06680$b632bac2@ushakov.ccd.baltbank.ru>
On Feb 1, 2000, "Ushakov, Sergey N." <ushakov@baltbank.ru> wrote:
> - the application being compiled on the second machine and linked there with
> the library prepared on the first machine misbehaves or crashes
> What may be the reason?
Different versions of glibc may be one reason.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-01 0:17 Ushakov, Sergey N.
2000-02-01 18:04 ` Alexandre Oliva [this message]
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Ushakov, Sergey N.
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=ord7qgweak.fsf@garnize.lsd.ic.unicamp.br \
--to=oliva@lsd.ic.unicamp.br \
--cc=help-gcc@gnu.org \
--cc=ushakov@baltbank.ru \
/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).