caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] "No bytecode specified"
Date: Tue, 3 Sep 2002 15:34:21 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.LNX.3.95.1020903152421.560B-100000@first.in-berlin.de> (raw)
In-Reply-To: <20020903151652.B21723@pauillac.inria.fr>



On Tue, 3 Sep 2002, Xavier Leroy wrote:

> > OK, no answers, that has helped,
> > so I now come with more details:
> 
> At last, some technical data in a message of yours.  You're (slowly)
> improving.  If you could just have posted this to caml-bugs@inria.fr
> rather than caml-list, this would have been perfect :-)
> 
> The cause of the problem is here:
> 
> > readlink("/proc/self/exe", "[0303]:2916", 1024) = 11

Yes, I thought, that this was a problem.
Looks very uncommon.

> 
> I.e. /proc/self/exe does not point to the executable name, but to an
> inode number.  That must be a truly ancient Linux kernel that you're
> running.  (Pre 2.0 ?)  

Yes, 2.0.18 on this old machine.
Updating? Hmhhh this old machine itself may be updated by a newer
one (faster hardware). ;-)

> 
> I'll harden the determination of the program name against this
> problem.

I once had used ocamlmktop, and I don' know if it was on my
new computer or on this old machine.
I think it was the old one, where it once worked, but
I think it was Ocaml 3.01, that worked.
Maybe in Ocaml 3.04 there were some changes...

Somewhere in the strace-output I found "ptrace".
I don't know a "ptrace" on linux-machines, but if
I remember correctly, there is a ptrace on Solaris-
machines.

Maybe it's only a problem of the  configure-script,
which thinks to use tools, not available on common
linux-distributions?


>  In the meantime, do yourself a favor and upgrade to a more
> recent Linux kernel (and distribution?).

Well, maybe this is a good idea.
I may try it with a debian.

But I'm not shure if new linux-distributions will work
well on this old machine. It works. Not very fast,
but still good enough for a lot of tasks.
So, when updating the software means to have necessity
of buying new hardware this is not, what I want...
(not enough money this times, hope it will change soon).


But I may try the new debian. :)

Ciao,
   Oliver

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2002-09-03 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 20:50 Oliver Bandel
2002-08-25 23:39 ` Stefano Zacchiroli
2002-08-26  7:32 ` malc
2002-08-26  8:38   ` Sven LUTHER
2002-08-26 10:00     ` Xavier Leroy
2002-08-26 12:53       ` Sven LUTHER
2002-08-26 11:03     ` malc
2002-08-26 12:32   ` Oliver Bandel
2002-08-26 12:36   ` Oliver Bandel
     [not found]   ` <Pine.LNX.3.95.1020826143546.418B-100000@first.in-berlin.de >
2002-08-27  1:52     ` Chris Hecker
2002-09-03 12:32 ` Oliver Bandel
2002-09-03 13:16   ` Xavier Leroy
2002-09-03 13:34     ` Oliver Bandel [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=Pine.LNX.3.95.1020903152421.560B-100000@first.in-berlin.de \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.fr \
    --cc=xavier.leroy@inria.fr \
    /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).