Skip to content

add python3 mummi, maestrowf#5

Merged
bhatiaharsh merged 5 commits intobhatiaharsh:bhatia-mummifrom
jmoon1506:bhatia-mummi
Oct 10, 2019
Merged

add python3 mummi, maestrowf#5
bhatiaharsh merged 5 commits intobhatiaharsh:bhatia-mummifrom
jmoon1506:bhatia-mummi

Conversation

@jmoon1506
Copy link
Copy Markdown

added all changes for python3

Copy link
Copy Markdown

@FrankD412 FrankD412 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, this looks fine to me. I just left a comment about Maestro's package.

version('develop', branch='develop')
version('1.1.4', tag='v1.1.4')
version('1.1.2', tag='v1.1.2')
version('flux-sched', branch='bugfix/flux_broker')
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one points to the same branch as flux-dev, so it's redundant.


homepage = "https://github.com/LLNL/maestrowf/"
url = "https://github.com/LLNL/maestrowf/archive/v1.1.2.tar.gz"
git = "https://github.com/LLNL/maestrowf.git"
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, so after having thought about it, i think i am sure this is not a good idea. by changing the default download method to git, we're forcing all users to set up proper ssh keys. whereas, by leaving it as path to tar gets around the problem, and makes the tool completely public!

here and below, we should have sha hash of all the downloadable releases. use git only for the branches and bug-fixes, like @FrankD412 had before.

@jmoon1506
Copy link
Copy Markdown
Author

Okay ready for merge

@bhatiaharsh bhatiaharsh merged commit 58925a0 into bhatiaharsh:bhatia-mummi Oct 10, 2019
bhatiaharsh pushed a commit that referenced this pull request Jun 20, 2020
Whenever attempting to use any ncurses functionality within cscope, a
page fault would result within the ncurses library.

    Program received signal SIGSEGV, Segmentation fault.
    0x00007ffff7fad3cf in termattrs_sp () from .../lib/libncursesw.so.6
    (gdb) bt
    #0  0x00007ffff7fad3cf in termattrs_sp () from .../lib/libncursesw.so.6
    #1  0x00007ffff7faa794 in _nc_setupscreen_sp () from .../lib/libncursesw.so.6
    #2  0x00007ffff7fa614c in newterm_sp () from .../lib/libncursesw.so.6
    #3  0x00007ffff7fa65b9 in newterm () from .../lib/libncursesw.so.6
    #4  0x00007ffff7fa2970 in initscr () from .../lib/libncursesw.so.6
    #5  0x0000000000403dc2 in main (argc=<optimized out>, argv=0x7fffffffcea8) at main.c:574

This is due to a conflict between libtinfo.so and libtinfow.so. Both are
linked into cscope:

    $ ldd $(which cscope)
    /bin/bash: .../lib/libtinfo.so.6: no version information available (required by /bin/bash)
        linux-vdso.so.1 (0x00007fff5dbcb000)
        libncursesw.so.6 => .../lib/libncursesw.so.6 (0x00007f435cc69000)
        libtinfo.so.6 => .../lib/libtinfo.so.6 (0x00007f435cc2c000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f435ca29000)
        libtinfow.so.6 => .../lib/libtinfow.so.6 (0x00007f435c9e8000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f435cca7000)

Specifically linking libtinfow.so instead of libtinfo.so resolves the
issue.

All instances of '...' above represent the path to the installed ncurses
for Spack.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants