I am new to linux, and have problems with installing "Alarm clock "program for Genome. i have extracted the folder and entered
./configure
when trying to enter make command i got the following message
“make: *** No targets specified and no makefile found. Stop”
here are the content of extracted folder:
Makefile.am
Makefile.in
install-sh
Itmain.sh
missing
mkistalldirs
depcomp
configure.ac
configure
configu.sub
configu.rpath
configu.log
configu.h.in
config.guess
autogen.sh
aclocal.m4
src folder
po folder
m4 folder
could you please tell me what is wrong? or you might also suggest other alarm program which will be easier to install with Genome environment.
Usually there’s a README file that you can open to get instructions. Were you in the build directory when you issued the ‘make’ command? Try ‘make Makefile’ or ‘make install’, and see if that works.
hi,
Yes, i am in the alarm directory. When i enter
make Makefile or
make install
i got the following messages
make: *** No rule to make target Makefile'. Stop make: *** No rule to make target install’. Stop
hi,
I am using Opensuse 11.2 Genome and from install software i found only Kalarm package which doesn’t start up automatically on login with Genome enviroment.
Yeah I don’t see this particular program in the repositories, but it looks like there are alternatives. I just grabbed it off the web and it worked for me, if you really want this program instead of another alarm clock program your problem is that the configure script isn’t producing a makefile. You are almost definitely missing a dependency.
Some quick package ideas to make sure you have from glancing at the output of the configure script are “gcc” and “perl”, and I am presuming you will need “gtk2-devel”. It’s easiest to get these from Yast->install software, or just click on install software from the right of the computer menu on the bottom left of the gnome screen. Put their name in the search box one by one, select them and click install.
If that doesn’t do it, then try “./configure > error.txt” and then post error.txt, or just do “./configure” and cut and paste the output from the terminal.
how can i put it in the start directory? do you mean /home/username?
gtk2-devel is installed
,bellow is the output when i do configure command:—>>
./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… gawk
checking whether make sets $(MAKE)… yes
checking whether to enable maintainer-specific portions of Makefiles… no
checking for style of include used by make… 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 ISO C89… none needed
checking dependency style of gcc… gcc3
checking for library containing strerror… none required
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ISO C89… (cached) none needed
checking dependency style of gcc… (cached) gcc3
checking for gcc… (cached) gcc
checking whether we are using the GNU C compiler… (cached) yes
checking whether gcc accepts -g… (cached) yes
checking for gcc option to accept ISO C89… (cached) none needed
checking dependency style of gcc… (cached) gcc3
checking how to run the C preprocessor… gcc -E
checking for grep that handles long lines and -e… /usr/bin/grep
checking for egrep… /usr/bin/grep -E
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 locale.h usability… yes
checking locale.h presence… yes
checking for locale.h… yes
checking for LC_MESSAGES… yes
checking libintl.h usability… yes
checking libintl.h presence… yes
checking for libintl.h… yes
checking for ngettext in libc… yes
checking for dgettext in libc… yes
checking for bind_textdomain_codeset… yes
checking for msgfmt… /usr/bin/msgfmt
checking for dcgettext… yes
checking if msgfmt accepts -c… yes
checking for gmsgfmt… /usr/bin/msgfmt
checking for xgettext… /usr/bin/xgettext
checking whether NLS is requested… yes
checking for intltool >= 0.35.0… 0.40.6 found
checking for intltool-update… /usr/bin/intltool-update
checking for intltool-merge… /usr/bin/intltool-merge
checking for intltool-extract… /usr/bin/intltool-extract
checking for xgettext… (cached) /usr/bin/xgettext
checking for msgmerge… /usr/bin/msgmerge
checking for msgfmt… (cached) /usr/bin/msgfmt
checking for gmsgfmt… (cached) /usr/bin/msgfmt
checking for perl… /usr/bin/perl
checking for perl >= 5.8.1… 5.10.0
checking for XML::Parser… ok
checking build system type… x86_64-unknown-linux-gnu
checking host system type… x86_64-unknown-linux-gnu
checking for a sed that does not truncate output… /usr/bin/sed
checking for fgrep… /usr/bin/grep -F
checking for ld used by gcc… /usr/x86_64-suse-linux/bin/ld
checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld… yes
checking for BSD- or MS-compatible name lister (nm)… /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface… BSD nm
checking whether ln -s works… yes
checking the maximum length of command line arguments… 1572864
checking whether the shell understands some XSI constructs… yes
checking whether the shell understands “+=”… yes
checking for /usr/x86_64-suse-linux/bin/ld option to reload object files… -r
checking for objdump… objdump
checking how to recognize dependent libraries… pass_all
checking for ar… ar
checking for strip… strip
checking for ranlib… ranlib
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for dlfcn.h… yes
checking for objdir… .libs
checking if gcc supports -fno-rtti -fno-exceptions… no
checking for gcc option to produce PIC… -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works… yes
checking if gcc static flag -static works… yes
checking if gcc supports -c -o file.o… yes
checking if gcc supports -c -o file.o… (cached) yes
checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) 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
checking for pkg-config… /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0… yes
checking for ALARMCLOCK… configure: error: Package requirements (gtk±2.0 >= 2.8 glib-2.0 gthread-2.0 gstreamer-0.10 libnotify) were not met:
No package ‘libnotify’ 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 ALARMCLOCK_CFLAGS
and ALARMCLOCK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
The last few lines of your .configure script is giving you the reason it won’t build. Maybe you should read it more carefully and follow what it says.
Here’s the few lines I’m referring to…
checking for ALARMCLOCK… configure: error: Package requirements (gtk±2.0 >= 2.8 glib-2.0 gthread-2.0 gstreamer-0.10 libnotify) were not met:
No package ‘libnotify’ 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 ALARMCLOCK_CFLAGS
and ALARMCLOCK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Do you have libnotify installed? Go to Yast->install software, search for libnotify, and see if it is installed. Mine is. Basically, keep searching for the libs it can’t find in install software, and if one of them isn’t coming up, repost, because it worked on mine so it would just be a problem of figuring out what package you need. But “libnotify” is a package in install software, so get that next.
Oh no matter what you are going to have to set up the program as a startup application. Sorry I didn’t really notice that was the primary problem. From the command line: “gnome-session-properties” or, go to the bottom panel, select to add “traditional-menu” to the panel, and from there it is system->system->startup. Sorry I don’t know how to get there from the fancy openSUSE gnome menu, I kind of stuck with the familiar. But from there you click add, and put in the program name that you want to start up.
But you are probably pretty close on the gnome alarm clock, and I’ve looked at it and it has the clean gnome look and feel to it, so if you want that one I understand. Definately try adding the libnotify, I have a good feeling that’s the last one ;).
Arggg, I guess my earlier replies didn’t go through. Sorry if this is a duplicate, and sorry for being terse, but I just put this in.
You will have to put in any program as a startup application if you want it to startup. There are other ways to launch it, but from the command line enter “gnome-session-properties”, and from there click add, and enter the command that launches the alarm clock program you decided on.
As to getting the alarm clock program built, your next step is to add libnotify, which you can do from Yast->install software and searching for “libnotify”. I checked, it’s in there, you need it.
As I said I’m being terse because I just entered all this stuff and it didn’t work, I’m not trying to be rude.
Definately try adding the libnotify, I have a good feeling that’s the last one .
Hm. What about ‘libnotify-devel’?
Seriously, I wouldn’t consider compiling an app a good lesson for beginners. One should actually know what is going on while doing so, at least when executing ‘make install’ (which has lots of drawbacks).
