[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Wed, 28 Jan 2004 13:03:59 +0000 (UTC) 
Subject:bug report [was] Re: help: POPLINK: CAN'T OPEN FILE 
From:Aaron Sloman 
Volume-ID: 


someanon@yahoo.com (someone) writes:

> Date: 27 Jan 2004 21:44:53 -0800
> Organization: http://groups.google.com
>
> > > Date: 26 Jan 2004 23:50:46 -0800
> > >
> > > A clean install.  Can anyone tell me what's the problem?
> > > ...
> > > $ poplog popc hello.p
> > >
> > > ;;; MISHAP - POPLINK: CAN'T OPEN FILE (Invalid directory)
> > > ;;; INVOLVING:  '$usepop/pop/src/src.wlb'
>
> Thanks for your info.
>
> Finally I found the problem:
>
> 1) for a clean install, src.wlb is locate at: $usepop/pop/obj/src.wlb
>
> I have to create a symbolic link manually:
>
> ls -l $usepop/pop/src/src.wlb
> lrwxrwxrwx    1 root     root           14 2004-01-27 20:37
> /usr/local/poplog/current.poplog/pop/src/src.wlb -> ../obj/src.wlb
>
> Can you modify the installation script to do this automatically?

I could but I am not sure that's the right solution and it
could cause other problems.

Following the documented ways of using popc should work without
this unless there's a bug in the documentation, or in the system.

Perhaps you should post a description of what you are trying to
achieve, and then people who have used popc may be able to explain
how they would do that.

When I have time I'll try to have a look at the code that builds

    $popsys/popc.psv
    $popsys/poplibr.psv
    $popsys/poplink.psv

(which is all located in $popsrc/syscomp/*). There may be a bug
there somewhere that leads to the wrong default directory being used
when poplink is invoked.

> 2)  this one is more hard to find:
>
> I'm using
>
> $ echo $SHELL
> /bin/bash
>
> It seems inside popc/ or poplink, the env var ($usepop) is not
> expanded, it use it literally as:
>
> readlink("$usepop/pop/src/src.wlb", 0xbfff8028, 760) = -1 ENOENT (No
> such file or directory)
> open("$usepop/pop/src/src.wlb", O_RDONLY) = -1 ENOENT (No such file or
> directory)

Is that pop11 ???

>
> so I create another funny symlink in the current dir:
>
> $ ln -s /usr/local/poplog/current.poplog \$usepop
>
> Now everything works.

Again, if you describe at a high level what you are
trying to achieve, it may be that there's a simpler solution
to these problems.

E.g. Why can't the first problem be solved by usig 'popc -c'
instead of 'popc'?

It's possible that a bug was introduced as a result of the
changes I made to three files in $popsrc/syscomp, trying to get
the linking script

    $popsys/poplink_cmnd

to have unexpanded environment variables so that it is
location-independent (not yet working for the olb files)

The three changed files are files.p, os_comms.p,
poplink_main.p

If that has broken something, that's where it should be fixed.

Aaron
====
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
School of Computer Science, The University of Birmingham, B15 2TT, UK
EMAIL A.Sloman AT cs.bham.ac.uk   (ReadATas@please !)
PAPERS: http://www.cs.bham.ac.uk/research/cogaff/ (And free book on Philosophy of AI)
FREE TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html