LinuxQuestions.org - GNU ccRTP installation error(bad interpreter ??)

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - GNU ccRTP installation error(bad interpreter ??) (https://www.linuxquestions.org/questions/linux-newbie-8/gnu-ccrtp-installation-error-bad-interpreter-748636/)

GNU ccRTP installation error(bad interpreter ??)

Hi All,
I am using OpenSuSE 11.0. Today I downloaded GNU ccRTP software and tried to install it. I went inside the directory and typed ./configure to start the installation process as told in the "readme" and "install" file. Bur I got the following error :

bash: ./configure: /bin/sh^M: bad interpreter: No such file or directory

Then I looked again in the "install" file and it was written that for older machines use " sh ./configure". Although my computer is new, I decided to use it and got the following error:

sh ./configure
: command not found1: (lol funny ! see the "1" at the end of "found")

./configure: line 19: Syntax error near unexpected token `elif'
./configure: line 19: `elif test -n "${BASH_VERSION+set}" && (set -o posix) >/de'/null 2>&1; then

Please tell me how can I install it

Can you post the first 30 or so lines of the configure script, ideally in CODE tags so it looks pretty? CODE tags are available in Advanced post editing via the # icon.

Code:

#! /bin/sh

# Guess values for system-dependent variables and create Makefiles.

# Generated by GNU Autoconf 2.59.

#

# Copyright (C) 2003 Free Software Foundation, Inc.

# This configure script is free software; the Free Software Foundation

# gives unlimited permission to copy, distribute and modify it.

## --------------------- ##

## M4sh Initialization.  ##

## --------------------- ##



# Be Bourne compatible

if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then

  emulate sh

  NULLCMD=:

  # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which

  # is contrary to our usage.  Disable this feature.

  alias -g '${1+"$@"}'='"$@"'

elif test -n "${BASH_VERSION+set}" && (set -o posix) >/dev/null 2>&1; then

  set -o posix

fi

DUALCASE=1; export DUALCASE # for MKS sh



# Support unset when possible.

if ( (MAIL=60; unset MAIL) || exit) >/dev/null 2>&1; then

  as_unset=unset

else

  as_unset=false

fi





# Work around bugs in pre-3.0 UWIN ksh.

$as_unset ENV MAIL MAILPATH

PS1='$ '

PS2='> '

PS4='+ '



# NLS nuisances.

for as_var in \

  LANG LANGUAGE LC_ADDRESS LC_ALL LC_COLLATE LC_CTYPE LC_IDENTIFICATION \

  LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER \

  LC_TELEPHONE LC_TIME

do

  if (set +x; test -z "`(eval $as_var=C; export $as_var) 2>&1`"); then

    eval $as_var=C; export $as_var

  else

    $as_unset $as_var

  fi

done



# Required to use basename.

if expr a : '\(a\)' >/dev/null 2>&1; then

  as_expr=expr

else

  as_expr=false

fi



if (basename /) >/dev/null 2>&1 && test "X`basename / 2>&1`" = "X/"; then

  as_basename=basename

else

  as_basename=false

fi





# Name of the executable.

as_me=`$as_basename "$0" ||

$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \

        X"$0" : 'X\(//\)$' \| \

        X"$0" : 'X\(/\)$' \| \

        .    : '\(.\)' 2>/dev/null ||

echo X/"$0" |

    sed '/^.*\/\([^/][^/]*\)\/*$/{ s//\1/; q; }

            /^X\/\(\/\/\)$/{ s//\1/; q; }

            /^X\/\(\/\).*/{ s//\1/; q; }

            s/.*/./; q'`





# PATH needs CR, and LINENO needs CR and PATH.

# Avoid depending upon Character Ranges.

as_cr_letters='abcdefghijklmnopqrstuvwxyz'

as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'

as_cr_Letters=$as_cr_letters$as_cr_LETTERS

as_cr_digits='0123456789'

as_cr_alnum=$as_cr_Letters$as_cr_digits



# The user is always right.

if test "${PATH_SEPARATOR+set}" != set; then

  echo "#! /bin/sh" >conf$$.sh

  echo  "exit 0"  >>conf$$.sh

  chmod +x conf$$.sh

  if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then

    PATH_SEPARATOR=';'

  else

    PATH_SEPARATOR=:

  fi

  rm -f conf$$.sh

fi

Hi ! I got some small help by searching, but that does not solve the problem. I think, it will help you in suggesting something to me. Somewhere this was writen:

"Apparently if a shell script gets opened and saved in notepad it will not run anymore.
A simple dos2unix fixed the problem."

Since I downloaded it from internet, it may be possible that it was infected with the "notepad" problem somewhere. So, I did "dos2unix configure" and then I run " ./configure". It worked for a while and then stopped, giving some errors. I looked at the errors and undertood that some other file was also corrupted in the same way. I did dos2unix on some files and again run ./config. this time, it worked for a longer time, but it stopped at last giving errors. Like this, I converted several files and tried.
But how long can I do like this? It is still giving errors.Is there a way to make the whole folder compatible by directly doing "dos2unix" or any other way?

Is written to run under lots of shells (smart coding!) but your /bin/sh is gagging on it.

What is your /bin/sh and sh? Please post output from

Code:

type sh

file /bin/sh

You could try changing the first line to

Code:

#!/bin/bash

Quote:

Originally Posted by LinuxNewman (Post 3649123)

Nice detective work! That's where the ^M came from in bash: ./configure: /bin/sh^M: bad interpreter: No such file or directory came from. Try

Code:

find . -type f -exec dos2unix {} \;

but make sure you have a backup first in case it changes some files that don't need changing. If it's only the .sh files that need changing then safer to use

Code:

find . -type f -iname '*.sh' -exec dos2unix {} \;

Or you could try to download from somewhere else.

Hi ! I downloaded from other site. But here is an explanation how it was corrupted. I downloaded the tar file and uncompresses in the Windows computer(because only that is connected to the internet !) and then transfered to Linux pc.That introduced the corruption. This time, I uncompressed in the Linux.So, there was no problem. But now something serious happened. Here is the error.

Code:

linux-904e:/home/linux3/RTP/ccrtp-1.5.1 # ./configure

checking build system type... i686-pc-linux-gnu

checking host system type... i686-pc-linux-gnu

checking target system type... i686-pc-linux-gnu

checking for gcc... gcc

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 gcc accepts -g... yes

checking for gcc option to accept ANSI C... none needed

checking how to run the C preprocessor... gcc -E

checking for g++... g++

checking whether we are using the GNU C++ compiler... yes

checking whether g++ accepts -g... yes

checking how to run the C++ preprocessor... g++ -E

checking whether we are using the GNU C++ compiler... (cached) yes

checking whether g++ accepts -g... (cached) yes

checking for a sed that does not truncate output... /usr/bin/sed

checking for egrep... grep -E

checking for ld used by gcc... /usr/i586-suse-linux/bin/ld

checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes

checking for /usr/i586-suse-linux/bin/ld option to reload object files... -r

checking for BSD-compatible nm... /usr/bin/nm -B

checking whether ln -s works... yes

checking how to recognise dependent libraries... pass_all

checking for ANSI C header files... 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 dlfcn.h usability... yes

checking dlfcn.h presence... yes

checking for dlfcn.h... yes

checking how to run the C++ preprocessor... g++ -E

checking for g77... no

checking for f77... no

checking for xlf... no

checking for frt... no

checking for pgf77... no

checking for fort77... no

checking for fl32... no

checking for af77... no

checking for f90... no

checking for xlf90... no

checking for pgf90... no

checking for epcf90... no

checking for f95... no

checking for fort... no

checking for xlf95... no

checking for ifc... no

checking for efc... no

checking for pgf95... no

checking for lf95... no

checking for gfortran... no

checking whether we are using the GNU Fortran 77 compiler... no

checking whether  accepts -g... no

checking the maximum length of command line arguments... 32768

checking command to parse /usr/bin/nm -B output from gcc object... ok

checking for objdir... .libs

checking for ar... ar

checking for ranlib... ranlib

checking for strip... strip

checking if gcc supports -fno-rtti -fno-exceptions... no

checking for gcc option to produce PIC... -fPIC

checking if gcc PIC flag -fPIC works... yes

checking if gcc static flag -static works... yes

checking if gcc supports -c -o file.o... yes

checking whether the gcc linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes

checking whether -lc should be explicitly linked in... no

checking dynamic linker characteristics... GNU/Linux ld.so

checking how to hardcode library paths into programs... immediate

checking whether stripping libraries is possible... yes

checking if libtool supports shared libraries... yes

checking whether to build shared libraries... yes

checking whether to build static libraries... yes

configure: creating libtool

appending configuration tag "CXX" to libtool

checking for ld used by g++... /usr/i586-suse-linux/bin/ld

checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes

checking whether the g++ linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes

checking for g++ option to produce PIC... -fPIC

checking if g++ PIC flag -fPIC works... yes

checking if g++ static flag -static works... yes

checking if g++ supports -c -o file.o... yes

checking whether the g++ linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes

checking dynamic linker characteristics... GNU/Linux ld.so

checking how to hardcode library paths into programs... immediate

appending configuration tag "F77" to libtool

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking for style of include used by make... GNU

checking dependency style of gcc... none

checking dependency style of g++... none

checking for gcry_cipher_open in -lgcrypt... yes

checking for ranlib... (cached) ranlib

checking for genorated automake files... found

checking whether to enable maintainer-specific portions of Makefiles... no

checking for pkg-config... /usr/bin/pkg-config

checking pkg-config is at least version 0.9.0... yes

checking for COMMON... configure: error: Package requirements (libccgnu2 >= 1.3.0) were not met:



No package 'libccgnu2' found



Consider adjusting the PKG_CONFIG_PATH environment variable if you

installed software in a non-standard prefix.



Alternatively, you may set the environment variables COMMON_CFLAGS

and COMMON_LIBS to avoid the need to call pkg-config.

See the pkg-config man page for more details.

I dont know what should I write in those environment variables :(

Hi ! I dowloaded and installed libcommoncpp2 as a remedy for the error "No package 'libccgnu2' found" . But still the error remains same. Even though I saw that libccgnu2-1.7.so.0 is present in the /usr/lib. Why is it not detecting it?