Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Dave-bo_Baggins
    Member
    • May 2013
    • 14

    #76
    I was troubleshooting and looking into the error messages and I thoughts Id share some progress, well I hope progress

    Looking at the error statement again

    g++ -Wall -Wno-strict-aliasing -g -gdwarf-2 -Wunused -Wuninitialized -march=i686 -O3 -DNDEBUG -pthread -I/usr/local/boost_1_53_0/include -I/usr/local/include/bam/include -I/usr/local/include/Eigen/include -o cufflinks -L/usr/local/lib -L/usr/local/include/bam/lib cufflinks.o libcufflinks.a libgc.a -lboost_thread -lboost_system -lbam -lz
    /usr/local/lib/libboost_thread.a(thread.o): In function `__gnu_cxx::__exchange_and_add_dispatch(int*, int) [clone .constprop.241]':
    thread.cpp.text.unlikely+0x22): undefined reference to `__atomic_fetch_add_4'


    I noticed:
    -I/usr/local/boost_1_53_0/include
    -I/usr/local/include/bam/include


    I noticed that while there is an include subdirectory for Eigen there was none for /boost_1_53_0 or /bam. What I did for the bam subdirectory was to copy my header files to the /usr/local/include/bam directory. I went back to the cufflinks gettign started manual
    and read "Copy the samtools binary to some directory in your PATH." Would I be correct in assuming that I should copy the contents of Desktop/samtools-0.1.19 to the /usr/local/ folder ? Would it make sense to create an include folder in the /boost_1_53_0 and /bam directories and fill it with the appropriate files ?

    The line that Im still trying to decipher is the

    thread.cpp.text.unlikely+0x22): undefined reference to `__atomic_fetch_add_4'

    I figure it has something to do with not being able to find the thread.cpp in the library directory which in the connfigure statement I defined as : --with-boost-libdir=/usr/local/lib. did a locate *read.cpp and found the following locations:
    /usr/local/boost_1_53_0/libs/thread/example/thread.cpp
    /usr/local/boost_1_53_0/libs/thread/src/pthread/thread.cpp
    /usr/local/boost_1_53_0/libs/thread/src/win32/thread.cpp

    Comment

    • GenoMax
      Senior Member
      • Feb 2008
      • 7142

      #77
      Dave,

      Now my head is starting to hurt

      I feel that all these problems are because of additional directive in red:

      --with-boost=/usr/local/boost_1_53_0 --with-boost-libdir=/usr/local/lib

      Can you try the compile removing the second option?

      Everything related to your boost libraries should be under the original location where you had compiled boost.

      Can you tell me where exactly did you initially compile the boost libraries? In /usr/local/boost_1_53_0 or in /usr/local.

      The reason I had asked you to create the "boost" top level directory was that way both "include" and "lib" from boost would be nicely segregated under that directory. Then when you compile cufflinks all you will need to include would be "--with-boost=path_to_top_level_boost" directory. No other boost related directives should be needed as long as your library had compiled correctly.
      Last edited by GenoMax; 05-15-2013, 03:48 PM.

      Comment

      • twotwo
        Member
        • May 2012
        • 40

        #78
        Originally posted by Tiger123 View Post
        Some additional information about the results got when I build the boost using:

        bjam --prefix=\usr\local --toolset=gcc architecture=x86 address_model=32 link=static runtime-link=static stage install

        /home/tiger123/boost/boost_1_47_0/tools/build/v2/build/property.jam:328: in validate1 from module property
        error: Invalid property '<address_model>32': unknown feature 'address_model'.
        /home/tiger123/boost/boost_1_47_0/tools/build/v2/build/property.jam:337: in property.validate from module property
        /home/tiger123/boost/boost_1_47_0/tools/build/v2/build/build-request.jam:216: in convert-command-line-element from module build-request
        /home/tiger123/boost/boost_1_47_0/tools/build/v2/build/build-request.jam:153: in build-request.from-command-line from module build-request
        /home/tiger123/boost/boost_1_47_0/tools/build/v2/build-system.jam:612: in load from module build-system
        /home/tiger123/boost/boost_1_47_0/tools/build/v2/kernel/modules.jam:283: in import from module modules
        /home/tiger123/boost/boost_1_47_0/tools/build/v2/kernel/bootstrap.jam:142: in boost-build from module
        /home/tiger123/boost/boost_1_47_0/boost-build.jam:17: in module scope from module


        Any thoughts?
        I have the same problem. Any comments???

        Comment

        • GenoMax
          Senior Member
          • Feb 2008
          • 7142

          #79
          Originally posted by twotwo View Post
          I have the same problem. Any comments???
          Can you provide additional details?

          What OS? What version of boost are you trying to compile? What is the exact command line you are using? Even if the error appears to be the same it may help us diagnose the problem if you can post it here.

          Comment

          • twotwo
            Member
            • May 2012
            • 40

            #80
            Originally posted by GenoMax View Post
            Can you provide additional details?

            What OS? What version of boost are you trying to compile? What is the exact command line you are using? Even if the error appears to be the same it may help us diagnose the problem if you can post it here.
            Thanks for replying so quick!
            bjam --prefix=/home/twotwo/software/boost153 --toolset=gcc architecture=x86 address_model=64 link=static runtime-link=static stage install


            And I got the following error:
            /home/twotwo/software/boost_1_53_0/tools/build/v2/build/property.jam:328: in validate1 from module property
            error: Invalid property '<address_model>64': unknown feature 'address_model'.
            /home/twotwo/software/boost_1_53_0/tools/build/v2/build/property.jam:337: in property.validate from module property
            /home/twotwo/software/boost_1_53_0/tools/build/v2/build/build-request.jam:216: in convert-command-line-element from module build-request
            /home/twotwo/software/boost_1_53_0/tools/build/v2/build/build-request.jam:154: in build-request.from-command-line from module build-request
            /home/twotwo/software/boost_1_53_0/tools/build/v2/build-system.jam:613: in load from module build-system
            /home/twotwo/software/boost_1_53_0/tools/build/v2/kernel/modules.jam:283: in import from module modules
            /home/twotwo/software/boost_1_53_0/tools/build/v2/kernel/bootstrap.jam:142: in boost-build from module
            /home/twotwo/software/boost_1_53_0/boost-build.jam:17: in module scope from module


            In the bjam command, I put the prefix with another folder boost153. However, even I used /home/twotwo/software/boost_1_53_0, I have the same error.

            By the way, I just found the following command:
            ./bootstrap.sh
            ./b2 install --prefix=PREFIX
            from the following web:

            Is this also the way to install boost? Thanks so much!
            However, after I run those two command, I still cannot run bjam command that I showed above...

            Comment

            • GenoMax
              Senior Member
              • Feb 2008
              • 7142

              #81
              It appears that boost has not been compiled correctly. Do you see bjam in /home/twotwo/software/boost153/?

              The link you posted is the way to build boost. You will need to replace PREFIX with the path you want for your boost libraries which would be (--prefix=/home/twotwo/software/boost153).
              Last edited by GenoMax; 06-24-2013, 10:10 AM. Reason: Clarified a file path

              Comment

              • twotwo
                Member
                • May 2012
                • 40

                #82
                Originally posted by GenoMax View Post
                Can you provide additional details?

                What OS? What version of boost are you trying to compile? What is the exact command line you are using? Even if the error appears to be the same it may help us diagnose the problem if you can post it here.
                The OS is the linux. And I removed some of the option:
                bjam --prefix=/home/twotwo/software/boost153/ link=static runtime-link=static stage install
                Then it works. Can I install without the option of:
                --toolset=gcc architecture=x86 address_model=64
                Is there any difference?

                Comment

                • GenoMax
                  Senior Member
                  • Feb 2008
                  • 7142

                  #83
                  Originally posted by twotwo View Post
                  The OS is the linux. And I removed some of the option:
                  bjam --prefix=/home/twotwo/software/boost153/ link=static runtime-link=static stage install
                  Then it works. Can I install without the option of:
                  --toolset=gcc architecture=x86 address_model=64
                  Is there any difference?
                  Are you using the directions for "Getting started" located here: http://tophat.cbcb.umd.edu/tutorial.shtml?

                  Update: TopHat developers have updated that page to take out the reference to "address-model". Based on the current info there you can omit the last three options (--toolset=gcc architecture=x86 address_model=64).

                  See my post #70 this thread. The address-model requires a "-" (hyphen) and not an underscore.
                  Last edited by GenoMax; 06-24-2013, 10:37 AM.

                  Comment

                  • twotwo
                    Member
                    • May 2012
                    • 40

                    #84
                    Originally posted by GenoMax View Post
                    Are you using the directions for "Getting started" located here: http://tophat.cbcb.umd.edu/tutorial.shtml?

                    Update: TopHat developers have updated that page to take out the reference to "address-model". Based on the current info there you can omit the last three options (--toolset=gcc architecture=x86 address_model=64).

                    See my post #70 this thread. The address-model requires a "-" (hyphen) and not an underscore.
                    Thanks for being so helpful! Yes, I did not update my tophat since I already have my SAM files. Should I update the tophat if I only want to run cuffdiff?
                    And if I used
                    1. ./bootstrap.sh
                    2. ./b2 install --prefix=/home/twotwo/software/boost153
                    Did boost install well? Should I still need to run bjam?

                    Thanks so much!

                    Comment

                    • twotwo
                      Member
                      • May 2012
                      • 40

                      #85
                      Originally posted by GenoMax View Post
                      Are you using the directions for "Getting started" located here: http://tophat.cbcb.umd.edu/tutorial.shtml?

                      Update: TopHat developers have updated that page to take out the reference to "address-model". Based on the current info there you can omit the last three options (--toolset=gcc architecture=x86 address_model=64).

                      See my post #70 this thread. The address-model requires a "-" (hyphen) and not an underscore.
                      never mind my other reply. When I changed address-model from underscore to hyphen, the three options worked!!! Thank you so much!!! I felt much better.

                      Comment

                      Latest Articles

                      Collapse

                      • SEQadmin2
                        From Collection to Sequencing: Why Sample Preparation and Preservation Define Sequencing Data
                        by SEQadmin2


                        Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.


                        The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
                        ...
                        06-02-2026, 10:05 AM
                      • SEQadmin2
                        Single-Cell Sequencing at an Inflection Point: Early Impacts of New Platforms and Emerging Trends
                        by SEQadmin2


                        With the launch of new single-cell sequencing platforms in 2026, the field stands at an exciting inflection point. This article surveys the most impactful advances in the field and discusses how they’re reshaping research in cancer, immunology, and beyond.


                        Introduction

                        Single-cell sequencing technologies have undergone remarkable advances over the past decade, transitioning from low-throughput experimental approaches to highly scalable platforms capable of...
                        05-22-2026, 06:42 AM
                      • SEQadmin2
                        Environmental Genomics in the Age of NGS: From Microbes to Conservation Strategies
                        by SEQadmin2

                        Studying ecosystems means dealing with complex, multi-species communities that are hard to observe at scale. This complexity, however, hides many important questions to be answered, from how biogeochemical cycles work and how climate change can affect species distribution to how conservation strategies can work best.


                        Genomics, particularly since the expansion of NGS, has transformed ecosystem ecology. By sequencing environmental DNA, we can now assess biodiversity without direct...
                        05-06-2026, 09:04 AM

                      ad_right_rmr

                      Collapse

                      News

                      Collapse

                      Topics Statistics Last Post
                      Started by SEQadmin2, Today, 08:59 AM
                      0 responses
                      9 views
                      0 reactions
                      Last Post SEQadmin2  
                      Started by SEQadmin2, 06-02-2026, 12:03 PM
                      0 responses
                      21 views
                      0 reactions
                      Last Post SEQadmin2  
                      Started by SEQadmin2, 06-02-2026, 11:40 AM
                      0 responses
                      17 views
                      0 reactions
                      Last Post SEQadmin2  
                      Started by SEQadmin2, 05-28-2026, 11:40 AM
                      0 responses
                      30 views
                      0 reactions
                      Last Post SEQadmin2  
                      Working...