Ticket #99 (closed defect: invalid)

Opened 6 years ago

Last modified 5 years ago

make install for 0.6.2 release failing on python scripts

Reported by: bhilburn Owned by: cdietric
Priority: blocker Milestone:
Component: ossiecf Version: 0.6.2
Keywords: Cc:

Description

During the make install for 0.6.2, it is failing with the following output:

Making install in python
make[2]: Entering directory `/home/bhilburn/working/scripts/release-0.6.2/src/system/ossie/idl/python'
python setup.py install
running install
running build
running build_py
error: package directory 'ossie' does not exist
make[2]: *** [install] Error 1
make[2]: Leaving directory `/home/bhilburn/working/scripts/release-0.6.2/src/system/ossie/idl/python'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/bhilburn/working/scripts/release-0.6.2/src/system/ossie/idl'
make: *** [install-recursive] Error 1
FAILED: sudo make install


ERROR building src/system/ossie

This is clearly due to the python scripts added to the make file to install the python bindings. Is it possible that it is because the necessary package hasn't been installed yet? Perhaps this should all be run after everything is installed instead of concurrently.

Change History

  Changed 6 years ago by bhilburn

  • status changed from new to closed
  • resolution set to invalid

The original error was an omniORBpy problem - the error message just wasn't very descriptive.

The installation completes successfully using the build.py script.

follow-up: ↓ 3   Changed 6 years ago by balister

Can you document the omniPy problem, just in case this comes up again?

in reply to: ↑ 2   Changed 6 years ago by jgaeddert

Replying to balister:

Can you document the omniPy problem, just in case this comes up again?

Build failed because omniORBpy was not installed. The output listed above is from make install while make actually failed to build the python bindings. Because the makefile actually just runs a python script to generate the bindings, make didn't return an error, but make install did because the resulting directory, ossie, was not present.

follow-up: ↓ 5   Changed 6 years ago by balister

It sounds like the python script should add error checking ....

in reply to: ↑ 4   Changed 6 years ago by jgaeddert

Yeah, probably...

  Changed 5 years ago by anonymous

  • milestone 0.6.2 deleted

Milestone 0.6.2 deleted

Note: See TracTickets for help on using tickets.