Seqanswers Leaderboard Ad

Collapse

Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • does AllPaths support the ubuntu i686

    I would like to install the AllPaths with ubuntu in a dell-Pe2950. When I compile it, it keep on warning. At last, only three binary, fileBitvectorOp checkLock and MakeDepend were compiled successfully. Who can tell me how i should do?

  • #2
    When I configure the program, it tell me that the system miss some C functions. Whether did it lead me failed?

    checking for gawk... gawk
    checking for a sed that does not truncate output... /bin/sed
    checking for bison... bison -y
    checking for g++... g++
    checking for C++ compiler default output file name... a.out
    checking whether the C++ compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking for gcc... gcc
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking for flex... flex
    checking lex output file root... lex.yy
    checking lex library... -lfl
    checking whether yytext is a pointer... yes
    checking whether ln -s works... yes
    checking whether make sets $(MAKE)... yes
    checking to see if we need to include the Boost libraries... no
    checking to see if we need to include the Xerces libraries... no
    checking to see if we need to include the GMP libraries... no
    checking for dirent.h that defines DIR... yes
    checking for library containing opendir... none required
    checking how to run the C preprocessor... gcc -E
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking for ANSI C header files... yes
    checking for sys/wait.h that is POSIX.1 compatible... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking fcntl.h usability... yes
    checking fcntl.h presence... yes
    checking for fcntl.h... yes
    checking float.h usability... yes
    checking float.h presence... yes
    checking for float.h... yes
    checking limits.h usability... yes
    checking limits.h presence... yes
    checking for limits.h... yes
    checking locale.h usability... yes
    checking locale.h presence... yes
    checking for locale.h... yes
    checking for memory.h... (cached) yes
    checking netinet/in.h usability... yes
    checking netinet/in.h presence... yes
    checking for netinet/in.h... yes
    checking stddef.h usability... yes
    checking stddef.h presence... yes
    checking for stddef.h... yes
    checking for stdlib.h... (cached) yes
    checking for string.h... (cached) yes
    checking for strings.h... (cached) yes
    checking sys/file.h usability... yes
    checking sys/file.h presence... yes
    checking for sys/file.h... yes
    checking sys/param.h usability... yes
    checking sys/param.h presence... yes
    checking for sys/param.h... yes
    checking sys/time.h usability... yes
    checking sys/time.h presence... yes
    checking for sys/time.h... yes
    checking for unistd.h... (cached) yes
    checking wchar.h usability... yes
    checking wchar.h presence... yes
    checking for wchar.h... yes
    configure: VENDOR wasn't set, setting to a default
    checking for getline in -lm... yes
    checking for stdbool.h that conforms to C99... yes
    checking for _Bool... yes
    checking for an ANSI C-conforming const... yes
    checking for inline... inline
    checking for mode_t... yes
    checking for off_t... yes
    checking for pid_t... yes
    checking for C/C++ restrict keyword... __restrict
    checking for size_t... yes
    checking for ssize_t... yes
    checking whether time.h and sys/time.h may both be included... yes
    checking whether struct tm is in sys/time.h or time.h... time.h
    checking for uint16_t... yes
    checking for uint32_t... yes
    checking for uint64_t... yes
    checking for uint8_t... yes
    checking for working volatile... yes
    checking for ptrdiff_t... yes
    checking for ulong... yes
    checking whether closedir returns void... no
    checking for error_at_line... yes
    checking vfork.h usability... no
    checking vfork.h presence... no
    checking for vfork.h... no
    checking for fork... yes
    checking for vfork... yes
    checking for working fork... yes
    checking for working vfork... (cached) yes
    checking whether gcc needs -traditional... no
    checking whether lstat dereferences a symlink specified with a trailing slash... yes
    checking whether lstat accepts an empty string... no
    checking whether lstat dereferences a symlink specified with a trailing slash... (cached) yes
    checking for stdlib.h... (cached) yes
    checking for GNU libc compatible malloc... yes
    checking for working memcmp... yes
    checking for stdlib.h... (cached) yes
    checking for unistd.h... (cached) yes
    checking for getpagesize... yes
    checking for working mmap... yes
    checking for stdlib.h... (cached) yes
    checking for GNU libc compatible realloc... yes
    checking sys/select.h usability... yes
    checking sys/select.h presence... yes
    checking for sys/select.h... yes
    checking sys/socket.h usability... yes
    checking sys/socket.h presence... yes
    checking for sys/socket.h... yes
    checking types of arguments for select... int,fd_set *,struct timeval *
    checking return type of signal handlers... void
    checking whether stat accepts an empty string... no
    checking for strftime... yes
    checking for alarm... yes
    checking for atexit... yes
    checking for bzero... yes
    checking for dup2... yes
    checking for floor... no
    checking for ftruncate... yes
    checking for getcwd... yes
    checking for gethostname... yes
    checking for getpagesize... (cached) yes
    checking for gettimeofday... yes
    checking for memchr... yes
    checking for memmove... yes
    checking for memset... yes
    checking for mkdir... yes
    checking for mkfifo... yes
    checking for munmap... yes
    checking for pow... no
    checking for putenv... yes
    checking for realpath... yes
    checking for regcomp... yes
    checking for rint... no
    checking for rmdir... yes
    checking for select... yes
    checking for setenv... yes
    checking for setlocale... yes
    checking for sqrt... no
    checking for strcasecmp... yes
    checking for strchr... yes
    checking for strdup... yes
    checking for strerror... yes
    checking for strncasecmp... yes
    checking for strrchr... yes
    checking for strstr... yes
    checking for strtol... yes
    checking for strtoul... yes
    checking for uname... yes
    checking to see that gcc is at least version 4.3.2... Yes, gcc version 4.3.2 is fine
    checking whether byte ordering is bigendian... no
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating config.h
    config.status: config.h is unchanged

    Comment

    Latest Articles

    Collapse

    • seqadmin
      Essential Discoveries and Tools in Epitranscriptomics
      by seqadmin




      The field of epigenetics has traditionally concentrated more on DNA and how changes like methylation and phosphorylation of histones impact gene expression and regulation. However, our increased understanding of RNA modifications and their importance in cellular processes has led to a rise in epitranscriptomics research. “Epitranscriptomics brings together the concepts of epigenetics and gene expression,” explained Adrien Leger, PhD, Principal Research Scientist...
      04-22-2024, 07:01 AM
    • seqadmin
      Current Approaches to Protein Sequencing
      by seqadmin


      Proteins are often described as the workhorses of the cell, and identifying their sequences is key to understanding their role in biological processes and disease. Currently, the most common technique used to determine protein sequences is mass spectrometry. While still a valuable tool, mass spectrometry faces several limitations and requires a highly experienced scientist familiar with the equipment to operate it. Additionally, other proteomic methods, like affinity assays, are constrained...
      04-04-2024, 04:25 PM

    ad_right_rmr

    Collapse

    News

    Collapse

    Topics Statistics Last Post
    Started by seqadmin, Yesterday, 11:49 AM
    0 responses
    13 views
    0 likes
    Last Post seqadmin  
    Started by seqadmin, 04-24-2024, 08:47 AM
    0 responses
    16 views
    0 likes
    Last Post seqadmin  
    Started by seqadmin, 04-11-2024, 12:08 PM
    0 responses
    61 views
    0 likes
    Last Post seqadmin  
    Started by seqadmin, 04-10-2024, 10:19 PM
    0 responses
    60 views
    0 likes
    Last Post seqadmin  
    Working...
    X