Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
11-12-2014, 12:20 PM
|
#1
|
Senior Member
Registered: Aug 2005
Location: Brazil
Distribution: Debian
Posts: 1,460
Rep:
|
Error compiling stjerm
I am trying to compile stjerm. Can someone please help:
Code:
# ./autogen.sh
This will do all the autotools stuff so that you can build
stjerm successfully.
When it is finished, take the usual steps to install:
./configure
make
make install
Generating configuration files for stjerm, please wait...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MESSAGES = "en_US.ISO8859-1",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MESSAGES = "en_US.ISO8859-1",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MESSAGES = "en_US.ISO8859-1",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MESSAGES = "en_US.ISO8859-1",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MESSAGES = "en_US.ISO8859-1",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MESSAGES = "en_US.ISO8859-1",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
configure.ac:6: installing `./install-sh'
configure.ac:6: installing `./missing'
src/Makefile.am: installing `./depcomp'
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MESSAGES = "en_US.ISO8859-1",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MESSAGES = "en_US.ISO8859-1",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
6.940u 0.556s 0:08.26 90.6% 0+0k 0+2768io 0pf+0w
# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... no
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/home/luc/Desktop/stjerm-0.16':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details
Exit 1
# cat config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure
## --------- ##
## Platform. ##
## --------- ##
hostname = luc
uname -m = i686
uname -r = 3.2.0-4-686-pae
uname -s = Linux
uname -v = #1 SMP Debian 3.2.63-2+deb7u1
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /bin
PATH: /sbin
PATH: /usr/bin
PATH: /usr/sbin
PATH: /usr/local/bin
PATH: /usr/local/sbin
PATH: /usr/games
PATH: /home/luc/bin
## ----------- ##
## Core tests. ##
## ----------- ##
configure:2182: checking for a BSD-compatible install
configure:2250: result: /usr/bin/install -c
configure:2261: checking whether build environment is sane
configure:2311: result: yes
configure:2452: checking for a thread-safe mkdir -p
configure:2491: result: /bin/mkdir -p
configure:2504: checking for gawk
configure:2534: result: no
configure:2504: checking for mawk
configure:2520: found /usr/bin/mawk
configure:2531: result: mawk
configure:2542: checking whether make sets $(MAKE)
configure:2568: result: no
configure:2689: checking for gcc
configure:2719: result: no
configure:2782: checking for cc
configure:2829: result: no
configure:2885: checking for cl.exe
configure:2915: result: no
configure:2939: error: in `/home/luc/Desktop/stjerm-0.16':
configure:2941: error: no acceptable C compiler found in $PATH
See `config.log' for more details
## ---------------- ##
## Cache variables. ##
## ---------------- ##
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_XMKMF_set=
ac_cv_env_XMKMF_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_install='/usr/bin/install -c'
ac_cv_path_mkdir=/bin/mkdir
ac_cv_prog_AWK=mawk
ac_cv_prog_make_make_set=no
## ----------------- ##
## Output variables. ##
## ----------------- ##
ACLOCAL='${SHELL} /home/luc/Desktop/stjerm-0.16/missing --run aclocal-1.11'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='$${TAR-tar}'
AUTOCONF='${SHELL} /home/luc/Desktop/stjerm-0.16/missing --run autoconf'
AUTOHEADER='${SHELL} /home/luc/Desktop/stjerm-0.16/missing --run autoheader'
AUTOMAKE='${SHELL} /home/luc/Desktop/stjerm-0.16/missing --run automake-1.11'
AWK='mawk'
CC=''
CCDEPMODE=''
CFLAGS=''
CPP=''
CPPFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
GLIB_REQUIRED=''
GREP=''
GTK_REQUIRED=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
LDFLAGS=''
LIBOBJS=''
LIBS=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /home/luc/Desktop/stjerm-0.16/missing --run makeinfo'
MKDIR_P='/bin/mkdir -p'
OBJEXT=''
PACKAGE='stjerm'
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_URL=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
SET_MAKE='MAKE=make'
SHELL='/bin/bash'
STRIP=''
VERSION='0.16'
XMKMF=''
ac_ct_CC=''
am__EXEEXT_FALSE=''
am__EXEEXT_TRUE=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__include=''
am__isrc=''
am__leading_dot='.'
am__nodep=''
am__quote=''
am__tar='$${TAR-tar} chof - "$$tardir"'
am__untar='$${TAR-tar} xf -'
bindir='${exec_prefix}/bin'
build_alias=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE}'
dvidir='${docdir}'
exec_prefix='NONE'
glib_CFLAGS=''
glib_LIBS=''
gthread_CFLAGS=''
gthread_LIBS=''
gtk_CFLAGS=''
gtk_LIBS=''
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
install_sh='${SHELL} /home/luc/Desktop/stjerm-0.16/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
mkdir_p='/bin/mkdir -p'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='NONE'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''
vte_CFLAGS=''
vte_LIBS=''
## ----------- ##
## confdefs.h. ##
## ----------- ##
/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
configure: exit 1
# exit
|
|
|
11-13-2014, 02:24 AM
|
#2
|
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 22,702
|
configure: error: no acceptable C compiler found in $PATH
so install a c compiler or set PATH
|
|
|
11-13-2014, 07:11 AM
|
#3
|
Senior Member
Registered: Aug 2005
Location: Brazil
Distribution: Debian
Posts: 1,460
Original Poster
Rep:
|
What C compiler? Isn't that GCC? I have it in my PATH, I even compiled vmm modules for VMWare.
|
|
|
11-13-2014, 07:42 AM
|
#4
|
LQ Addict
Registered: Mar 2012
Location: Hungary
Distribution: debian/ubuntu/suse ...
Posts: 22,702
|
no, it wasn't. Just look at the log:
Code:
checking for gcc... no
checking for cc... no
so please check it again.
|
|
|
11-13-2014, 10:40 AM
|
#6
|
Senior Member
Registered: Aug 2005
Location: Brazil
Distribution: Debian
Posts: 1,460
Original Poster
Rep:
|
I have gcc 4.6:
#~> which gcc-4.6
/usr/bin/gcc-4.6
How come I have installed VMWare modules?
If I install g++ ou build-essential, I will get gcc 4.7, which may cause conflicts (it already has in other tests) because my kernel was compiled with 4.6.
Any ideas about that?
|
|
|
11-13-2014, 11:19 AM
|
#7
|
LQ 5k Club
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,519
|
← #6 .
You can have as many versions of gcc as you want,
installed at the same time.
They all have unique file names. No conflicts.
The default Debian Wheezy gcc´s are gcc-4.4, gcc-4.6, gcc-4.7 .
Using ``gcc-4.6´´ :
$ cd stjerm-0.16/
$ patch -p1 < missing_libs.patch
$ export CC=gcc-4.6 CXX=g++-4.6 && ./configure
-
|
|
1 members found this post helpful.
|
11-13-2014, 11:26 AM
|
#8
|
Senior Member
Registered: Aug 2005
Location: Brazil
Distribution: Debian
Posts: 1,460
Original Poster
Rep:
|
First I tried the Ubuntu package, because a package is always nicer. It installed and ran, but the cursor just blinked and I couldn't type anything. I uninstalled it and tried compiling it again:
~# patch -p1 < missing_libs.patch
patching file src/Makefile.am
~# export CC=gcc-4.6 CXX=g++-4.6
~# ./autogen.sh
This will do all the autotools stuff so that you can build
stjerm successfully.
When it is finished, take the usual steps to install:
./configure
make
make install
Generating configuration files for stjerm, please wait...
configure.ac:6: installing `./install-sh'
configure.ac:6: installing `./missing'
src/Makefile.am: installing `./depcomp'
~# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc-4.6
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc-4.6 accepts -g... yes
checking for gcc-4.6 option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc-4.6... gcc3
./configure: line 3627: syntax error near unexpected token `glib,'
./configure: line 3627: `PKG_CHECK_MODULES(glib, glib-2.0 >= 2.10)'
|
|
|
11-13-2014, 03:10 PM
|
#9
|
LQ Muse
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,636
|
Quote:
/home/luc/Desktop/stjerm-0.16'
|
also linux is not windows
you really do NOT want to build software on the "Desktop"
even windows can have issues with that --- not a great idea
there should be a folder called " bin" in your home folder
/home/luc/bin
the "Desktop" is a "special" folder and you might encounter "issues" using that
|
|
|
11-13-2014, 05:25 PM
|
#10
|
Senior Member
Registered: Aug 2005
Location: Brazil
Distribution: Debian
Posts: 1,460
Original Poster
Rep:
|
Linux is not Windows, and what is the relevance of that?
The ~/Desktop directory on Linux provides exatly the same convenience as the ~/Desktop "folder" on Windows: I have immediate access to it by simply minimizing all windows - by conveniently pressing Win+d, just like on Windows! Isn't that convenient.
And why is it so "special"? I have been retrieving a lot of data from backups lately, including things I keep in this mysterious Linux Desktop directory. I hook up my external drive on USB, browse to /home/luc/Desktop and guess what: all the files are still there, all of them, intact and glorious.
Special indeed. Have I mentioned it's convenient?
Last edited by lucmove; 11-13-2014 at 05:26 PM.
|
|
|
11-14-2014, 07:44 AM
|
#11
|
LQ 5k Club
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,519
|
About stjerm : $ stjerm --toggle
.. the reply is : "User defined signal 1".
.. Same "reply" with any version of stjerm,
-0.15, 0.16 Ubuntu packages, i386 and amd64.
Also the stjerm-016 that were built in Debian 7 Wheezy,
i686 and x86_64 Wheezy versions ... same reply,
"User defined signal 1".
-
|
|
|
11-14-2014, 10:15 AM
|
#12
|
Senior Member
Registered: Aug 2005
Location: Brazil
Distribution: Debian
Posts: 1,460
Original Poster
Rep:
|
Quote:
Originally Posted by knudfl
About stjerm : $ stjerm --toggle
.. the reply is : "User defined signal 1".
.. Same "reply" with any version of stjerm,
-0.15, 0.16 Ubuntu packages, i386 and amd64.
Also the stjerm-016 that were built in Debian 7 Wheezy,
i686 and x86_64 Wheezy versions ... same reply,
"User defined signal 1".
-
|
Thanks, but... I don't understand what you mean. How is that related to compiling stjerm? Can you please rephrase?
Or rather, where did you get stjerm-016 built for Wheezy?
|
|
|
11-14-2014, 11:17 AM
|
#13
|
LQ 5k Club
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,519
|
← #12 .
Quote:
How is that related to compiling stjerm ?
|
I compiled two times stjerm-0.16 on Debian 7 :
1) By using Debian 7 Wheezy, 32bits (i686).
2) On Debian 7 Wheezy, 64bits (x86_64).
Both seemingly OK, but no "stjerm window" opened ($ stjerm --toggle),
.. the only result was the terminal message `User defined signal 1´.
-
|
|
|
All times are GMT -5. The time now is 07:39 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|