[LinuxBIOS] compile problems s2881

[Ward Vandewege]

Hi all,

I just checked out a clean s2881 tree (2254), and built it.

Along the way, I had to make a few changes to make it compile.

1. in targets/tyan/s2881/s2881/config.py, my machine required:
- a '#!/usr/bin/env python' line at the start of the file
- the file to be executable

2. compilation then failed as follows:
# make
...
Traceback (most recent call last):
  File "tyan/s2881/s2881/config.py", line 1541, in ?
    from yappsrt import *
ImportError: No module named yappsrt
make: *** [Makefile.settings] Error 1

I had to copy the yappsrt.py file from util/newconfig to the tyan/s2881/s2881
directory, and then everything worked fine.

Note that I only saw those problems with a freshly checked out tree. Once
I compiled successfully just once, I could erase tyan/s2881/s2881, redo the
buildtarget step, and make would work just fine in tyan/2881/s2881 without
these modifications.

Not sure what's causing this - my solution is clearly just a workaround. Any
ideas for a fix? I've observed these issues on a Debian testing/unstable
system, as well as an Ubuntu Breezy one.

Thanks,
Ward.

[Stefan Reinauer]

* Ward Vandewege  [060414 23:57]:
> I just checked out a clean s2881 tree (2254), and built it.
>
> Along the way, I had to make a few changes to make it compile.
> in targets/tyan/s2881/s2881/config.py, my machine required:
> a '#!/usr/bin/env python' line at the start of the file
> the file to be executable
> compilation then failed as follows:
>
> # make
> ...
> Traceback (most recent call last):
>   File "tyan/s2881/s2881/config.py", line 1541, in ?
>     from yappsrt import *
> ImportError: No module named yappsrt
> make: *** [Makefile.settings] Error 1
>
> I had to copy the yappsrt.py file from util/newconfig to the tyan/s2881/s2881
> directory, and then everything worked fine.

Sounds like either you have a broken or a brand new or a really old 
python version.  What python version are you using?

This kind of stuff happens all the time with python based software.

Stefan

[Richard Smith]

> > I had to copy the yappsrt.py file from util/newconfig to the tyan/s2881/s2881
> > directory, and then everything worked fine.
>
> Sounds like either you have a broken or a brand new or a really old
> python version.  What python version are you using?

Sounds more to me like the PYTHONPATH is not setup correctly.  The
reason it works the 2nd time is that python has compiled the module
into a .pyc in the current directory and now doesn't have to go look
though PYTHONPATH to find the module.

Modules either need to be in the current directory, have the proper
path to them specified, be in PYTHONPATH or be placed in the default
locations under the python tree.
> This kind of stuff happens all the time with python based software.

I don't see any difference between this and having your include or
library paths set properly in "C".  I don't know of any language that
will go searching your entire hard drive looking for files when it
can't find them where it expects them.

[Ward Vandewege]

On Sat, Apr 15, 2006 at 01:39:30AM +0200, Stefan Reinauer wrote:
> Ward Vandewege  [060414 23:57]:
> > I just checked out a clean s2881 tree (2254), and built it.
> >
> > Along the way, I had to make a few changes to make it compile.
> > in targets/tyan/s2881/s2881/config.py, my machine required:
> > a '#!/usr/bin/env python' line at the start of the file
> > the file to be executable
> > compilation then failed as follows:
> >
> > # make
> > ...
> > Traceback (most recent call last):
> >   File "tyan/s2881/s2881/config.py", line 1541, in ?
> >     from yappsrt import *
> > ImportError: No module named yappsrt
> > make: *** [Makefile.settings] Error 1
> >
> > I had to copy the yappsrt.py file from util/newconfig to the tyan/s2881/s2881
> > directory, and then everything worked fine.
>
> Sounds like either you have a broken or a brand new or a really old 
> python version.  What python version are you using?

I've tried with Python 2.3.5 on Debian testing/unstable, and Python 2.4.2 on
Ubuntu Breezy. Both exhibit the same problem.

Ward.

[Ronald G Minnich]

Ward Vandewege wrote:
> I had to copy the yappsrt.py file from util/newconfig to the tyan/s2881/s2881
> directory, and then everything worked fine.

we definitely don't want this? This has not been needed for anything 
else. Wonder what's wrong?

Not sure what is going on here, have not seen this on FCx

ron