mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Peter Jansen <hpj@urpla.net>
To: trond.myklebust@fys.uio.no
Cc: linux-kernel@vger.kernel.org
Subject: Re: [NFS] some strangeness (at least) with linux-2.4.18-NFS_ALL patch
Date: Sat, 12 Jan 2002 23:40:44 +0100	[thread overview]
Message-ID: <20020112224046.4205F1433@shrek.lisa.de> (raw)
In-Reply-To: <20020111131528.44F8613E6@shrek.lisa.de> <20020112170111.12E601431@shrek.lisa.de> <15424.33959.99237.666877@charged.uio.no>
In-Reply-To: <15424.33959.99237.666877@charged.uio.no>

On Saturday, 12. January 2002 19:47, Trond Myklebust wrote:
> >>>>> " " == Hans-Peter Jansen <hpj@urpla.net> writes:
>      > Somehow, gcc managed it to create an invalid link in the above
>      > sequence.  Really bad is, you cannot get around this within the
>      > client. After rm'ing lib/libsensors.so.1 on the server, make
>      > install succeeds on the client.
>
> <snip>
>
>      > I can reproduce this now. Do you?
>
> Nope.
>
> gcc -shared -Wl,-soname,libsensors.so.1 -o lib/libsensors.so.1.2.0
> lib/data.lo lib/general.lo lib/error.lo lib/chips.lo lib/proc.lo
> lib/access.lo lib/init.lo lib/conf-parse.lo lib/conf-lex.lo -lc
> rm -f lib/libsensors.so.1
> ln -sfn libsensors.so.1.2.0 lib/libsensors.so.1
> rm -f lib/libsensors.so
> ln -sfn libsensors.so.1.2.0 lib/libsensors.so
>
> Could you try just plain 2.4.18-pre3 + 2.4.18-NFS_ALL? That is what I
> am running (on both client + server).

Ok, done. Sad news, problem persist:
On compile:
gcc -shared -Wl,-soname,libsensors.so.1 -o lib/libsensors.so.1.2.0 
lib/data.lo lib/general.lo lib/error.lo lib/chips.lo lib/proc.lo 
lib/access.lo lib/init.lo lib/conf-parse.lo lib/conf-lex.lo -lc
rm -f lib/libsensors.so.1
ln -sfn libsensors.so.1.2.0 lib/libsensors.so.1
make: stat:lib/libsensors.so.1: Eingabe-/Ausgabefehler
rm -f lib/libsensors.so 
ln -sfn libsensors.so.1.2.0 lib/libsensors.so

On install:
make: stat:lib/libsensors.so.1: Eingabe-/Ausgabefehler
rm -f lib/libsensors.so.1
rm: Entfernen von »lib/libsensors.so.1« nicht möglich: Eingabe-/Ausgabefehler
make: *** [lib/libsensors.so.1] Error 1

Some system parameter:
server:
Dual Pentium 3/500, Asus P2B DS, 512 MB 
Linux version 2.4.18-pre3 (hp@shrek) (gcc version 2.95.3 20010315 (SuSE)) #2 
SMP Sam Jan 12 21:00:36 CET 2002
knfsd, reiserfs partition

client:
Athlon 1.2, Asus Via KT133, 768 MB
Linux version 2.4.18-pre3 (hp@elfe) (gcc version 2.95.3 20010315 (SuSE)) #3
Sam Jan 12 21:26:40 CET 2002
mount opt:
rw,nodev,v3,rsize=4096,wsize=4096,soft,intr,udp,lock,addr=shrek

Any more ideas? What's wrong with my setup?

Cheers,
Hans-Peter

  reply	other threads:[~2002-01-12 22:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 13:15 [NFS] some strangeness (at least) with linux-2.4.17-NFS_ALL patch Hans-Peter Jansen
2002-01-11 15:07 ` Trond Myklebust
2002-01-11 19:17   ` Hans-Peter Jansen
2002-01-12  2:24     ` Trond Myklebust
2002-01-12 17:01       ` [NFS] some strangeness (at least) with linux-2.4.18-NFS_ALL patch Hans-Peter Jansen
2002-01-12 18:47       ` Trond Myklebust
2002-01-12 22:40         ` Hans-Peter Jansen [this message]
2002-01-13 12:37         ` Trond Myklebust
2002-01-12  2:04   ` [NFS] some strangeness (at least) with linux-2.4.17-NFS_ALL patch Trond Myklebust

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=20020112224046.4205F1433@shrek.lisa.de \
    --to=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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

all inboxes | Powered by JetHome®