Installing Anjuta

Any help is appreciated. When I run the #/configure, I get:

user1@linux-xofj:~/anjuta-3.0.3.0> ./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 disable maintainer-specific portions of Makefiles… yes
checking for gcc… gcc
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 accepts -g… yes
checking for gcc option to accept ISO C89… none needed
checking for style of include used by make… GNU
checking dependency style of gcc… gcc3
checking how to run the C preprocessor… gcc -E
checking for flex… flex
checking lex output file root… lex.yy
checking lex library… -lfl
checking whether yytext is a pointer… yes
./configure: line 4684: flex: command not found
checking for bison… bison -y
./configure: line 4730: bison -y: command not found
checking for g++… g++
checking whether we are using the GNU C++ compiler… yes
checking whether g++ accepts -g… yes
checking dependency style of g++… gcc3
checking whether gcc and cc understand -c and -o together… yes
checking whether gcc understands -Wno-sign-compare… yes
checking what warning flags to pass to the C compiler… -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare
checking what language compliance flags to pass to the C compiler…
checking for pkg-config… /usr/bin/pkg-config
checking pkg-config is at least version 0.16… yes
checking for pkg-config… (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.22… yes
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking how to print strings… printf
checking for a sed that does not truncate output… /usr/bin/sed
checking for grep that handles long lines and -e… /usr/bin/grep
checking for egrep… /usr/bin/grep -E
checking for fgrep… /usr/bin/grep -F
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 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 how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format… func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format… func_convert_file_noop
checking for /usr/i586-suse-linux/bin/ld option to reload object files… -r
checking for objdump… objdump
checking how to recognize dependent libraries… pass_all
checking for dlltool… no
checking how to associate runtime and link libraries… printf %s

checking for ar… ar
checking for archiver @FILE support… @
checking for strip… strip
checking for ranlib… ranlib
checking command to parse /usr/bin/nm -B output from gcc object… ok
checking for sysroot… no
checking for mt… mt
checking if mt is a manifest tool… no
checking for ANSI C header files… no
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 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/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… no
checking how to run the C++ preprocessor… g++ -E
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 -DPIC
checking if g++ PIC flag -fPIC -DPIC works… yes
checking if g++ static flag -static works… yes
checking if g++ supports -c -o file.o… yes
checking if g++ supports -c -o file.o… (cached) yes
checking whether the g++ linker (/usr/i586-suse-linux/bin/ld) supports shared libraries… yes
checking dynamic linker characteristics… (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs… immediate
checking for gobject-introspection… no
checking for ANJUTA… no
configure: error: Package requirements (gthread-2.0 >= 2.22.0
glib-2.0 >= 2.28.0
gio-2.0 >= 2.28.0
gtk±3.0 >= 3.0.0
gdk-pixbuf-2.0 >= 2.0.0) were not met:

No package ‘gtk±3.0’ 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 ANJUTA_CFLAGS
and ANJUTA_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

On 07/22/2011 05:06 PM, mddhmuser1 wrote:
>
> Any help is appreciated. When I run the #/configure, I get:

please don’t run configure or make as root…only run “make install” as
root…

> No package ‘gtk±3.0’ found

gtk3 is not default installed in openSUSE 11.4, so use YaST to search
for and install gtk3-devel (at least, maybe others)

as for the notes about path variables…i have no clue…but, for sure
its not gonna compile until you meet all the dependencies…they should
be listed in the README (or similar) packaged with the source, or at the
download site: http://www.anjuta.org/downloads


DD
Caveat-Hardware-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!

What about:


su -c 'zypper in -t pattern devel_ide' 

or just

su -c 'zypper in anjuta'

?

On 07/23/2011 01:26 AM, please try again wrote:
>
> su -c ‘zypper in anjuta’

oh YES! my bad, i didn’t see it was in the standard repos!!

or @mddhmuser1 just use YaST > Software Management…
oh, now i see you are new here -=welcome=- to openSUSE, we have our own
repos full of clean and trusted packages…no need to compile most
stuff…just use YaST or zypper, read more:

http://old-en.opensuse.org/Concepts#Software_handling_.28Package_Management.29
http://doc.opensuse.org/

ask more too.


DD
Caveat-Hardware-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!