execution of aclocal fails - linux

upon executing autoreconf -i the following error returns
/usr/local/bin/aclocal: 14: /usr/local/bin/aclocal: Syntax error: word unexpected (expecting ")")
autoreconf: aclocal failed with exit status: 2
and execution of aclocal fails e.g aclocal --version returns error:
/usr/local/bin/aclocal: line 14: syntax error near unexpected token `[AC_CONFIG_MACRO_DIRS],'
/usr/local/bin/aclocal: line 14: `m4_ifndef([AC_CONFIG_MACRO_DIRS], [m4_defun([_AM_CONFIG_MACRO_DIRS], [])m4_defun([AC_CONFIG_MACRO_DIRS], [_AM_CONFIG_MACRO_DIRS($#)])])'
on machine 4.10.0-38-generic #42-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
removing automake, autoconf, and re-installing doesn't solve the problem, and i have no time to debug, any idea?

removal of /usr/local/bin/aclocal on linux/GNU ubuntu and re-installation solved the problem, but the reason is unknown to me.

Related

I've got this error message from strip: [.gnu.build.attributes]: corrupt GNU build attribute note: wrong note type: bad value

I'm creating an rpm package for my c++ program on Fedora 31. I've already created a .deb package on Debian 10 without issues, but on Fedora 31, when I use the shell command:
strip --strip-unneeded --remove-section=.comment --remove-section=.note ttxtgm
I get this error message:
strip:ttxtgm[.gnu.build.attributes]: corrupt GNU build attribute note:
wrong note type: bad value
I can't understand what is the problem with this executable.
I use g++ to build my program.
The same command shell executed on Debian 10 works fine.
I couldn't find any information about this error message from strip.
This is a binutils bug that was recently introduced into Fedora 31:
strip:testprog[.gnu.build.attributes]: corrupt GNU build attribute note: wrong note type: bad value
It is being fixed in binutils-2.32-29.fc31, with this binutils update. Once it hits the Fedora mirrors, you can install it using:
dnf update --enablerepo=updates-testing binutils
Before that, you can install the build directly from Koji, from the binutils-2.32-29.fc31 build:
dnf install https://kojipkgs.fedoraproject.org//packages/binutils/2.32/29.fc31/x86_64/binutils-2.32-29.fc31.x86_64.rpm

Installing Perl DBI in SUN Solaries

I am trying to install perl DBI on SUN solaries 11 but I always got the following error:
sh: line 1: cc: not found
*** Error code 127
make: Fatal error: Command failed for target `Perl.o'
I did the following steps:
Downloaded and extracted DBI-1.628 then in the shell command:
cd DBI-1.628
make realclean
perl Perlfile.PL
meke
This means it cannot find a compiler on your machine. You should add the path to the compiler to your PATH variable. gcc and cc are not the same thing. You should install cc.

Error Installing caret on AWS Red Hat Linux

I'm trying to install the R package caret
R -e "install.packages('caret', repos='http://cran.rstudio.com/')"
on an Amazon Linux AMI but the dependancies RcppEigen,lme4, BradleyTerry2 fail.
Warning messages:
1: In install.packages("caret", repos = "http://cran.rstudio.com/") : installation of package ‘RcppEigen’ had non-zero exit status
2: In install.packages("caret", repos = "http://cran.rstudio.com/") : installation of package ‘lme4’ had non-zero exit status
3: In install.packages("caret", repos = "http://cran.rstudio.com/") : installation of package ‘BradleyTerry2’ had non-zero exit status
4: In install.packages("caret", repos = "http://cran.rstudio.com/") : installation of package ‘caret’ had non-zero exit status
When I try to install RcppEigen I get (among other verbose massages):
/usr/bin/ld: cannot find -lRlapack
/usr/bin/ld: cannot find -lRblas
collect2: ld returned 1 exit status
make: *** [RcppEigen.so] Error 1
ERROR: compilation failed for package ‘RcppEigen’
* removing ‘/usr/lib64/R/library/RcppEigen’
My environment
Amazon Linux version 2015.03
Linux version 3.4.37-40.44.amzn1.x86_64 (mockbuild#gobi-build-31005) (gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC) ) #1 SMP Thu Mar 21 01:17:08 UTC 2013
It seems if it has to do with Red Hat vs. Ubuntu, but I can't find any answers here or elsewhere.
You need to enable the Extra Packages for Enterprise Linux (EPEL) repository.
To do this:
Modify /etc/yum.repos.d/epel.repo. Under the section marked [epel], change enabled=0 to enabled=1.
To temporarily enable the EPEL 6 repository, use the yum command line option --enablerepo=epel.
For more info see the official documentation

./ssh-keygen: 1: ./ssh-keygen: Syntax error: word unexpected (expecting ")")

I am using openssh-6.4p1 for ssh and sftp support and sdk is ipnc_rdk_dm36x_5.1 and compiler is arm-arago-linux-gnueabi-
when i am configuring openssh with below command
./configure --prefix=$(TARGET_FS)/usr --with-libs
--with-zlib=$(TARGET_FS)/usr --with-ssl-dir=$(TARGET_FS)/usr
--disable-strip --disable-etc-default-login CC=$(BUILD_TOOL_PREFIX)gcc
AR=$(BUILD_TOOL_PREFIX)ar LD=$(BUILD_TOOL_PREFIX)gcc RANLIB=$(BUILD_TOOL_PREFIX)ranlib --host=arm-linux-gnueabi
and then compiling and Installing
when i am installing, i am getting below error
./ssh-keygen: 1: ./ssh-keygen: Syntax error: word unexpected (expecting ")")
./ssh-keygen: 1: ./ssh-keygen: Syntax error: word unexpected (expecting ")")
can any one help me please...
thanks in advance
The file is cross compiled, so it can be executed on the build machine.
When you do "make install", it will run "./ssh-keygen -A".
However, the ssh-keygen can only run on ARM platform.
file ssh-keygen
ssh-keygen: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=1e23ab3c8a712b5a26a8d79ad02edcd33502202a, not stripped

lfs 7.2 compilation of glibc 2.16.0

I am making an linux system following the procedure in lfs. But while i was following the fifth step(i.e. the one before make) on this page, i get an error at the last.
configure: error: linker with -z relro support required
Now after this if i call make i get an error
make: *** No targets specified and no makefile found. Stop.
I am running this on a ubuntu 12.04 machine.
How to fix this error?
Do the following:-
sudo apt-get install gawk
and then retry. This worked for me.

Resources