linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rene Pachernegg <rene.pachernegg@apus.co.at>
To: linuxppc-embedded@lists.linuxppc.org
Subject: sys_open fails with shared libs
Date: Thu, 03 Aug 2000 17:07:55 +0200	[thread overview]
Message-ID: <39898ACB.E3CD752D@apus.co.at> (raw)


hi,

We ported  linux (kernel, sysvinit, getty, login, sash ...) to our ppc
740 based system, which worked fine using static linked libs.
We are trying now  to support dynamic linking, which causes login to
fail.

I was tracking down the problem to the following:
static:    sys_open in the kernel gets correct filenames (e.g.:
/etc/passwd from getpwnam in libc)
dynamic:    sys_open gets senseless names and cant open the needed files
(--> login fails without passwd) whenever it is called from a libc
function. Opening files from elsewhere is working fine.

It seems to be a kind of adressing problem so I controlled the adresses
of the filename parameter in sys_open, which is always FFExxxxx (don't
know if that may be an important hint) whenever its called from the
shared libs.

Everything else works with the shared libs. They are properly loaded (as
it seems) and the programs work fine. Calls to library functions work
to. It's seems to be just the system call open, which does not work from
the shared libs.

For cross compiling we use:
    bin-utils 2.9.5.0.22
    gcc 2.95.2
    glibc 2.1.2

Any suggestions?
Thanks,
    Ren


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2000-08-03 15:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=39898ACB.E3CD752D@apus.co.at \
    --to=rene.pachernegg@apus.co.at \
    --cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).