Re: gtk configuration problem
On 21/07/2009 16:19, soumen ghosh wrote: Hi, I am trying to install gtk in linux system. So, for that I downloaded anjuta-2.0.2 and try to configure this. I also downloaded glib-2.0.0 and glib-2.20.0 Hello, You are not on the right mailing list, this is not a technical list. I guess that kind of support should go to gnome-love list, please post there. and please, send mail in text format not html. Thanks smime.p7s Description: S/MIME Cryptographic Signature ___ foundation-list mailing list foundation-list@gnome.org http://mail.gnome.org/mailman/listinfo/foundation-list
gtk configuration problem
Hi, I am trying to install gtk in linux system. So, for that I downloaded anjuta-2.0.2 and try to configure this. I also downloaded glib-2.0.0 and glib-2.20.0 So follow some steps, are describing below: *1. I set the PKG_CONFIG_PATH=usr/lib 2. I put the package glib-2.0.0 in the path usr/lib and usr/include 3. In the path /usr/lib/pkgconfig, there is some .pc files. I edited the file glib-2.0.pc, change the glib version to 2.0.0(that I have glib-2.0.0) I edited the file gobject-2.0.pc, here also change the glib version to 2.0.0(that I have glib-2.0.0) 4. then I run the command ./configure * The output of that configuration is: 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 whether to enable maintainer-specific portions of Makefiles... no checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for iconv... /usr/bin/iconv checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... /usr/bin/msgmerge checking for xgettext... /usr/bin/xgettext 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 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 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 for library containing strerror... none required checking for egrep... grep -E checking for ANSI C header files... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/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 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... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes 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/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 configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/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/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 if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 static flag -static works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/bin/ld) supports shared
Re: gtk configuration problem
Hi Soumen, Foundation list is not a technical list. Please go here ( http://mail.gnome.org/mailman/listinfo) to find a more appropriate list in the future (gtk-list might be a good starting point). I also suggest going on Freenode irc and chatting with people in #gnome or #gtk. Since you are running into a basic problem I can help you with, I'm going to e-mail you off list. -- John (J5) Palmieri 2009/7/21 soumen ghosh ghosh.soume...@gmail.com Hi, I am trying to install gtk in linux system. So, for that I downloaded anjuta-2.0.2 and try to configure this. I also downloaded glib-2.0.0 and glib-2.20.0 So follow some steps, are describing below: *1. I set the PKG_CONFIG_PATH=usr/lib 2. I put the package glib-2.0.0 in the path usr/lib and usr/include 3. In the path /usr/lib/pkgconfig, there is some .pc files. I edited the file glib-2.0.pc, change the glib version to 2.0.0(that I have glib-2.0.0) I edited the file gobject-2.0.pc, here also change the glib version to 2.0.0(that I have glib-2.0.0) 4. then I run the command ./configure * The output of that configuration is: 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 whether to enable maintainer-specific portions of Makefiles... no checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for iconv... /usr/bin/iconv checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... /usr/bin/msgmerge checking for xgettext... /usr/bin/xgettext 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 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 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 for library containing strerror... none required checking for egrep... grep -E checking for ANSI C header files... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/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 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... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes 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/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 configure: creating libtool appending configuration tag CXX to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/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/bin/ld) supports shared libraries... yes checking
Re: gtk configuration problem
On Tue, 2009-07-21 at 12:23 -0400, john palmieri wrote: Hi Soumen, Foundation list is not a technical list. Please go here (http://mail.gnome.org/mailman/listinfo) to find a more appropriate list in the future (gtk-list might be a good starting point). I also suggest going on Freenode irc and chatting with people in #gnome or #gtk. Since you are running into a basic problem I can help you with, I'm going to e-mail you off list. This seems to happen relatively frequently, and I suspect it's because of the Support section here: http://www.gtk.org/development.html If you want to help the GTK+ project by donating money OR perhaps your company wants to pay someone to develop GTK+, you can email the GNOME foundation. Any donations to GNOME for GTK+ will ONLY be spent on GTK+. Then there's a link to email foundation-list. The paragraph is pretty clear if you read it. Unfortunately, people don't really read pages like this. They see Support and a big blue like and click. Two ideas on how to address this come to mind. We could put some sort of admonition there reiterating that the link is only for certain types of support. It would have to be big and in your face to ensure people read it. Alternatively (and I think this is better), *first* have a link for community support, then the foundation link. -- Shaun ___ foundation-list mailing list foundation-list@gnome.org http://mail.gnome.org/mailman/listinfo/foundation-list
