LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   [SLACK 12] Dropline Gnome corrupt files? (https://www.linuxquestions.org/questions/slackware-14/%5Bslack-12%5D-dropline-gnome-corrupt-files-636951/)

koentje93 04-22-2008 12:53 AM

[SLACK 12] Dropline Gnome corrupt files?
 
Hello everybody,

I have a problem on slackware 12.0 with my Dropline installer. I have installed all packages. But not 2 of the packages. I don't now exact witch package version but it are the packages:
gnome-mime-data and
gnome-utils
The first package have I installed good! But it's strange that the Dropline installer gives again the message that the 2 files are corrupt! :confused:
Ok I have installed package 2 but that have a problem with the make file! :confused:
It says that I must use another strange program ??

I am not now on my linux desktop :cry: (because I am on school)
You must wait in the evening then I post my errors, reports etc. :)

Greets,

Koen

koentje93 04-22-2008 07:01 AM

Here the error and that kind of stuff ;)

Code:

AUTHORS      README        config.h.in  gnome-dictionary/    install-sh*          m4/
COPYING      THANKS        config.log    gnome-doc-utils.make  intltool-extract.in  missing*
ChangeLog    acinclude.m4  config.sub*  gnome-screenshot/    intltool-merge.in    mkinstalldirs*
INSTALL      aclocal.m4    configure*    gnome-utils.spec      intltool-update.in  omf.make
Makefile.am  baobab/        configure.in  gnome-utils.spec.in  libtool*            po/
Makefile.in  compile*      depcomp*      gsearchtool/          logview/            xmldocs.make
NEWS        config.guess*  gfloppy/      gtk-doc.make          ltmain.sh
root@vervoordeldonk:/down/gnome-utils-2.20.0.1# ./configure
checking for a BSD-compatible install... /usr/bin/ginstall -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 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 intltool >= 0.35.0... 0.36.1 found
checking for perl... /usr/bin/perl
checking for XML::Parser... ok
checking for library containing strerror... none required
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 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 bison... bison -y
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) 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... /usr/bin/sed
checking for ld used by gcc... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
checking for /usr/i486-slackware-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
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/i486-slackware-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... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/i486-slackware-linux/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/i486-slackware-linux/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... yes
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/i486-slackware-linux/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for glib-genmarshal... /usr/bin/glib-genmarshal
checking for glib-mkenums... /usr/bin/glib-mkenums
checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes
checking what language compliance flags to pass to the C compiler...
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for off_t... yes
checking for pid_t... yes
checking for size_t... yes
checking for struct stat.st_rdev... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for uid_t in sys/types.h... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking return type of signal handlers... void
checking for strftime... yes
checking for getcwd... yes
checking for gettimeofday... yes
checking for getwd... yes
checking for putenv... yes
checking for strdup... yes
checking for strtoul... yes
checking for uname... yes
checking for logf... no
checking for getpgid... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GNOME_UTILS... configure: error: Package requirements (glib-2.0 >= 2.13.3                                gtk+-2.0 >= 2.11.6                                libgnome-2.0 >= 2.13.2                                libgnomeui-2.0 >= 2.13.7) were not met:

Requested 'glib-2.0 >= 2.13.3' but version of GLib is 2.12.12
Requested 'gtk+-2.0 >= 2.11.6' but version of GTK+ is 2.10.13
No package 'libgnome-2.0' found
No package 'libgnomeui-2.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 GNOME_UTILS_CFLAGS
and GNOME_UTILS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

root@vervoordeldonk:/down/gnome-utils-2.20.0.1#
root@vervoordeldonk:/down/gnome-utils-2.20.0.1#


XavierP 04-22-2008 11:07 AM

Code:

Requested 'glib-2.0 >= 2.13.3' but version of GLib is 2.12.12
Requested 'gtk+-2.0 >= 2.11.6' but version of GTK+ is 2.10.13
No package 'libgnome-2.0' found
No package 'libgnomeui-2.0' found

This is the pertinent information: you need a higher version of glib and gtk+ and the 2 libgnome files.

jong357 04-22-2008 01:29 PM

Dropline has pre-made packages. I'm curious as to why you are compiling the source...

koentje93 04-23-2008 12:06 PM

Quote:

Originally Posted by jong357 (Post 3129340)
Dropline has pre-made packages. I'm curious as to why you are compiling the source...

I compile it because those packages where corrupt of he has no installed it !
I Download the source then and compile the files ;)

shilo 04-23-2008 01:04 PM

If two files that were downloaded are corrupt, the installer won't continue. The easiest solution is to delete the two corrupt files and run the installer again. Since the two files will be missing, they will be downloaded again.

No need to compile anything.

koentje93 04-23-2008 01:12 PM

Quote:

Originally Posted by shilo (Post 3130517)
If two files that were downloaded are corrupt, the installer won't continue. The easiest solution is to delete the two corrupt files and run the installer again. Since the two files will be missing, they will be downloaded again.

No need to compile anything.

Ok I go delete those packages and run dropline-gnome again!

koentje93 04-24-2008 01:06 PM

I have downloaded and installed Dropline-Gnome succesfull ! :)

Thanks


All times are GMT -5. The time now is 08:13 PM.