Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Options used to compile repository packages

  1. #1
    Join Date
    Jul 2008
    Location
    India
    Posts
    182

    Default Options used to compile repository packages

    Hi,

    Is there a method to know the compilation options used for a particular package available in the repositories? For example i'm unable to decide which of the two is the appropriate HYPRE package for me:

    1. hypre-devel
    2. hypre-gnu-openmpi3-hpc-devel


    Thanks.

  2. #2

    Default Re: Options used to compile repository packages

    For comprehensive info provide links to repos.
    You may compile it by yourself.

  3. #3
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,699
    Blog Entries
    15

    Default Re: Options used to compile repository packages

    Quote Originally Posted by Svyatko View Post
    For comprehensive info provide links to repos.
    You may compile it by yourself.
    Hi
    There is only one repo and no standalone devel package.. just the different builds.

    https://build.opensuse.org/package/show/science/hypre

    Check the build log for options (or the spec file);
    https://build.opensuse.org/build/sci...nmpi3-hpc/_log
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #4
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Options used to compile repository packages

    If you're installing a solution that requires hypre,
    It's probably best to just run the install.

    The install will likely do a dependency check for the existence of hypre and then for the specific features hypre is providing.

    If an error is thrown, then the error should be explanatory enough to determine what the problem is.

    If you're running a test,
    You may want to ensure you can erase all traces of any failed tests...
    One way is to do your testing in a virtual machine,
    Another way is to make sure you have a snapshot you can roll back to (Snapper should automatically make a snapshot of your system anyway each time you install any package if you're installed on BTRFS).

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  5. #5

    Default Re: Options used to compile repository packages

    Quote Originally Posted by samrat_rao View Post
    Hi,

    Is there a method to know the compilation options used for a particular package available in the repositories? For example i'm unable to decide which of the two is the appropriate HYPRE package for me:

    1. hypre-devel
    2. hypre-gnu-openmpi3-hpc-devel


    Thanks.
    Use hypre-devel if you know nothing about MPI.

  6. #6
    Join Date
    Jul 2008
    Location
    India
    Posts
    182

    Default Re: Options used to compile repository packages

    Thanks for all your replies.

    Quote Originally Posted by tsu2 View Post
    If you're installing a solution that requires hypre,
    It's probably best to just run the install.

    The install will likely do a dependency check for the existence of hypre and then for the specific features hypre is providing.

    If an error is thrown, then the error should be explanatory enough to determine what the problem is.

    If you're running a test,
    You may want to ensure you can erase all traces of any failed tests...
    One way is to do your testing in a virtual machine,
    Another way is to make sure you have a snapshot you can roll back to (Snapper should automatically make a snapshot of your system anyway each time you install any package if you're installed on BTRFS).

    TSU
    I'm using a parallel CFD code that was developed in-house. HYPRE is required for this code.

    Quote Originally Posted by Svyatko View Post
    Use hypre-devel if you know nothing about MPI.
    The code i am using requires MPI and HYPRE. The problem is that if i use hypre-devel it appears that whenever HYPRE is invoked every process is blurting messages which it should not be doing.

    If i use hypre-gnu-openmpi3-hpc-devel then the same code with the same parameters as with hpre-devel gives a segmentation fault.

    I also compiled openMPI-4 and HYPRE (using this compiled openMPI-4) separately and yet i got the same segmentaton fault.

    I have generated a minimal Fortran 90 code to reproduce this error and asked the HYPRE developers for help. Hope they respond.

    Quote Originally Posted by malcolmlewis View Post
    Hi
    There is only one repo and no standalone devel package.. just the different builds.

    https://build.opensuse.org/package/show/science/hypre

    Check the build log for options (or the spec file);
    https://build.opensuse.org/build/sci...nmpi3-hpc/_log
    If i click the last link then i am directed back to this thread.

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Options used to compile repository packages

    If you're seeing segmentation faults, then you're probably doing the right thing already if you're in touch with the Hypre developers.
    But,
    Your original question was about compilation options, and if an option wasn't compiled, I usually see an error something like "foobar missing" -- Not a segmentation fault which usually is some kind of process crashing.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  8. #8
    Join Date
    Jul 2008
    Location
    India
    Posts
    182

    Default Re: Options used to compile repository packages

    Quote Originally Posted by tsu2 View Post
    If you're seeing segmentation faults, then you're probably doing the right thing already if you're in touch with the Hypre developers.
    But,
    Your original question was about compilation options, and if an option wasn't compiled, I usually see an error something like "foobar missing" -- Not a segmentation fault which usually is some kind of process crashing.

    TSU
    Hi,

    My original question about compilation options was because using hypre-devel led to each process blurting out the same lines which should otherwise only be written by the rank = 0 process.

    Using hypre-devel some of the messages from HYPRE which are directed to STDOUT are only supposed to come from rank = 0 process. So i thought that hypre-devel was compiled using gcc / gfortran and NOT mpicc / mpifort.

    I still don't know the compile-time options used by developers contributing to the repos.

  9. #9
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,699
    Blog Entries
    15

    Default Re: Options used to compile repository packages

    Quote Originally Posted by samrat_rao View Post
    Hi,

    My original question about compilation options was because using hypre-devel led to each process blurting out the same lines which should otherwise only be written by the rank = 0 process.

    Using hypre-devel some of the messages from HYPRE which are directed to STDOUT are only supposed to come from rank = 0 process. So i thought that hypre-devel was compiled using gcc / gfortran and NOT mpicc / mpifort.

    I still don't know the compile-time options used by developers contributing to the repos.
    Hi
    Can you please show information about the hypre packages installed;

    Code:
    zypper if hypre-devel
    zypper se -si hypre
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  10. #10
    Join Date
    Jul 2008
    Location
    India
    Posts
    182

    Default Re: Options used to compile repository packages

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Can you please show information about the hypre packages installed;

    Code:
    zypper if hypre-devel
    zypper se -si hypre
    Code:
    zypper if hypre-devel
    Code:
    Loading repository data... 
    Reading installed packages... 
     
     
    Information for package hypre-devel: 
    ------------------------------------ 
    Repository     : Software for Scientists and Engineers (openSUSE_Leap_15.2) 
    Name           : hypre-devel 
    Version        : 2.20.0-lp152.47.1 
    Arch           : x86_64 
    Vendor         : obs://build.opensuse.org/science 
    Installed Size : 1.2 MiB 
    Installed      : Yes 
    Status         : up-to-date 
    Source package : hypre-2.20.0-lp152.47.1.src 
    Summary        : Headers and library links for libHYPRE2_20_0 
    Description    :  
        HYPRE headers and libraries files needed for development 
        This package contains development files of the serial version of Hypre.
    Code:
    zypper se -si hypre
    Code:
    Loading repository data... 
    Reading installed packages... 
     
    S  | Name                    | Type    | Version           | Arch   | Repository 
    ---+-------------------------+---------+-------------------+--------+----------------------------------------------------------- 
    i+ | hypre-devel             | package | 2.20.0-lp152.47.1 | x86_64 | Software for Scientists and Engineers (openSUSE_Leap_15.2) 
    i+ | hypre-mpich-devel       | package | 2.20.0-lp152.47.1 | x86_64 | Software for Scientists and Engineers (openSUSE_Leap_15.2) 
    i+ | hypre-mvapich2-devel    | package | 2.20.0-lp152.47.1 | x86_64 | Software for Scientists and Engineers (openSUSE_Leap_15.2) 
    i+ | hypre-openmpi3-devel    | package | 2.20.0-lp152.47.1 | x86_64 | Software for Scientists and Engineers (openSUSE_Leap_15.2) 
    i  | libHYPRE2_20_0          | package | 2.20.0-lp152.47.1 | x86_64 | Software for Scientists and Engineers (openSUSE_Leap_15.2) 
    i  | libHYPRE2_20_0-mpich    | package | 2.20.0-lp152.47.1 | x86_64 | Software for Scientists and Engineers (openSUSE_Leap_15.2) 
    i  | libHYPRE2_20_0-mvapich2 | package | 2.20.0-lp152.47.1 | x86_64 | Software for Scientists and Engineers (openSUSE_Leap_15.2) 
    i  | libHYPRE2_20_0-openmpi3 | package | 2.20.0-lp152.47.1 | x86_64 | Software for Scientists and Engineers (openSUSE_Leap_15.2)
    Today i added more HYPRE packages from the repositories, and also compiled more using openMPI-4. The code now runs with MVAPICH2 (from the repositories) but not with openMPI (3 or 4). So the segmentation fault may not be due to errors from my code.

    i've observed such things before also on different desktops / laptops. But i had forgotten about it since it was many years back when i was writing parallel codes using MPI. I got back to it over the past one month.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •