public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ushakov, Sergey N." <ushakov@baltbank.ru>
To: <help-gcc@gnu.org>
Subject: object files portability issues
Date: Tue, 01 Feb 2000 00:17:00 -0000	[thread overview]
Message-ID: <000001bf6c8c$a5f06680$b632bac2@ushakov.ccd.baltbank.ru> (raw)

Hello,

can anyone tell what precautions should be taken when an
application-specific library is compiled with gcc on one machine, and an
application is linked and run on another machine?

Our exact problem is:

- an application-specific library is compiled on a linux machine
- a complete application being linked with this library on this machine runs
ok
- the object library and the application source are transferred to another
linux machine
- both machines are Intel, linux versions slightly differ
- the application prepared on the first machine and linked as static runs on
the second machine ok
- 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? Are object codes really portable? What should one
take into consideration to achieve portability?

Thanks,
Sergey Ushakov

WARNING: multiple messages have this Message-ID

From: "Ushakov, Sergey N." <ushakov@baltbank.ru>
To: <help-gcc@gnu.org>
Subject: object files portability issues
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <000001bf6c8c$a5f06680$b632bac2@ushakov.ccd.baltbank.ru> (raw)
Message-ID: <20000401000000.-NdF6MVDj3qF0mQ7J0v7WsgoM42DANXFPbDnunqbWbc@z> (raw)

Hello,

can anyone tell what precautions should be taken when an
application-specific library is compiled with gcc on one machine, and an
application is linked and run on another machine?

Our exact problem is:

- an application-specific library is compiled on a linux machine
- a complete application being linked with this library on this machine runs
ok
- the object library and the application source are transferred to another
linux machine
- both machines are Intel, linux versions slightly differ
- the application prepared on the first machine and linked as static runs on
the second machine ok
- 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? Are object codes really portable? What should one
take into consideration to achieve portability?

Thanks,
Sergey Ushakov

             reply	other threads:[~2000-02-01  0:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-01  0:17 Ushakov, Sergey N. [this message]
2000-02-01 18:04 ` Alexandre Oliva
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='000001bf6c8c$a5f06680$b632bac2@ushakov.ccd.baltbank.ru' \
    --to=ushakov@baltbank.ru \
    --cc=help-gcc@gnu.org \
    /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).