| Autor | Nachricht | 
  
    |  | 
        
          |   | Titel: Kennt jemand 'kfourier-1.1' ?  Verfasst am: 06.01.2008, 18:40 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 18. Okt 2006
 Beiträge: 185
 
 
 |  | 
        
          | Kennt hier jemand die spezifische Bedingungen um 'kfourier-1.1' mit Etch kompilieren zu können? 
 Ich habe bereit schon mehrfache Entwickelungspackete installiert, einschließlich jetzt 'libqt3-mt-dev' vollständig, plus 'libqt3-compat-headers' . Jedoch fehlen dem Quellcode-Ordner bei der Erstellung der Makefile immer noch ausdrücklich "QT-1.3" Header und Bibliotheken, die der Vorgang nicht nennt.
 
 Dieses Programm hat als Zweck, ein Bild in 2D mit Fourier-Transform zu analysieren, und auch sehr prakisch Frequenzen als Bildrauschen usw. auszuschneiden. Es brauch also Grafik, aber im 2D-Bereich, nicht etwa im 3D-Bereich.
 
 Dirk
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel: Kennt jemand  Verfasst am: 06.01.2008, 18:56 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 28. Feb 2005
 Beiträge: 1112
 Wohnort: Camelot
 
 |  | 
        
          | manche Programme sind echt nicht der Hit probiere aber mal ./configure --help
 das gibt dir die Optionen um die Pfade zu übergeben
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
          |   | Titel:  Verfasst am: 07.01.2008, 01:09 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 18. Okt 2006
 Beiträge: 185
 
 
 |  | 
        
          | Damit haben Sie mir sehr geholfen! Es gibt ein configure-Argument, mit dem man die Stelle vorgeben darf, wo sich QT befindet!   
 Daher konnte ./configure dieses Mal QT finden. Jedoch hat das danach nur zu einem weiteren Problem gefuehrt: ./configure findet den KDE-Pfad nicht, und ich finde auch so schnell nicht, wie man den setzen kann. Hier also der Code:
 
 dirk@KanotixBox:~/Desktop/kfourier-1.1$ configure --help
 Usage: configure [options] [host]
 Options: [defaults in brackets after descriptions]
 Configuration:
 --cache-file=FILE       cache test results in FILE
 --help                  print this message
 --no-create             do not create output files
 --quiet, --silent       do not print `checking...' messages
 --version               print the version of autoconf that created configure
 Directory and file names:
 --prefix=PREFIX         install architecture-independent files in PREFIX
 [/usr/local/kde]
 --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
 [same as prefix]
 --bindir=DIR            user executables in DIR [EPREFIX/bin]
 --sbindir=DIR           system admin executables in DIR [EPREFIX/sbin]
 --libexecdir=DIR        program executables in DIR [EPREFIX/libexec]
 --datadir=DIR           read-only architecture-independent data in DIR
 [PREFIX/share]
 --sysconfdir=DIR        read-only single-machine data in DIR [PREFIX/etc]
 --sharedstatedir=DIR    modifiable architecture-independent data in DIR
 [PREFIX/com]
 --localstatedir=DIR     modifiable single-machine data in DIR [PREFIX/var]
 --libdir=DIR            object code libraries in DIR [EPREFIX/lib]
 --includedir=DIR        C header files in DIR [PREFIX/include]
 --oldincludedir=DIR     C header files for non-gcc in DIR [/usr/include]
 --infodir=DIR           info documentation in DIR [PREFIX/info]
 --mandir=DIR            man documentation in DIR [PREFIX/man]
 --srcdir=DIR            find the sources in DIR [configure dir or ..]
 --program-prefix=PREFIX prepend PREFIX to installed program names
 --program-suffix=SUFFIX append SUFFIX to installed program names
 --program-transform-name=PROGRAM
 run sed PROGRAM on installed program names
 Host type:
 --build=BUILD           configure for building on BUILD [BUILD=HOST]
 --host=HOST             configure for HOST [guessed]
 --target=TARGET         configure for TARGET [TARGET=HOST]
 Features and packages:
 --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
 --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
 --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
 --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
 --x-includes=DIR        X include files are in DIR
 --x-libraries=DIR       X library files are in DIR
 --enable and --with options recognized:
 --enable-debug          creates debugging code [default=no]
 --enable-shared         build shared libraries [default=yes]
 --enable-static         build static libraries [default=no]
 --with-gnu-ld           assume the C compiler uses GNU ld [default=no]
 --disable-nls           do not use Native Language Support
 --with-qt-dir           where the root of qt is installed
 --with-qt-includes      where the qt includes are.
 --with-qt-libraries     where the qt library is installed.
 --with-extra-includes   adds non standard include paths
 --with-extra-libs       adds non standard library paths
 --disable-path-check    don't try to find out, where to install
 --with-install-root     the root, where to install to [default=/]
 --disable-rpath         do not use the rpath feature of ld
 dirk@KanotixBox:~/Desktop/kfourier-1.1$ configure --with-qt-dir=/usr/share/qt3
 loading cache ./config.cache
 checking host system type... i686-pc-linux-gnu
 checking target system type... i686-pc-linux-gnu
 checking build system type... i686-pc-linux-gnu
 checking for a BSD compatible install... /usr/bin/install -c
 checking whether build environment is sane... yes
 checking whether make sets ${MAKE}... yes
 checking for working aclocal... missing
 checking for working autoconf... missing
 checking for working automake... missing
 checking for working autoheader... missing
 checking for working makeinfo... missing
 checking for a C-Compiler...
 checking for gcc... gcc
 checking whether the C compiler (gcc  ) works... yes
 checking whether the C compiler (gcc  ) is a cross-compiler... no
 checking whether we are using GNU C... yes
 checking how to run the C preprocessor... gcc -E
 checking for a C++-Compiler...
 checking for g++... g++
 checking whether the C++ compiler (g++  -s) works... yes
 checking whether the C++ compiler (g++  -s) is a cross-compiler... no
 checking whether we are using GNU C++... yes
 checking for ranlib... ranlib
 checking for ld used by GCC... /usr/bin/ld
 checking if the linker (/usr/bin/ld) is GNU ld... yes
 checking for BSD-compatible nm... /usr/bin/nm -B
 checking whether ln -s works... yes
 checking for g++ option to produce PIC... -fPIC
 checking if g++ PIC flag -fPIC works... yes
 checking if g++ static flag -static works... -static
 checking if the linker (/usr/bin/ld) is GNU ld... yes
 checking whether the linker (/usr/bin/ld) supports shared libraries... yes
 checking command to parse /usr/bin/nm -B output... yes
 checking how to hardcode library paths into programs... immediate
 checking for /usr/bin/ld option to reload object files... -r
 checking dynamic linker characteristics... Linux ld.so
 checking if libtool supports shared libraries... yes
 checking whether to build shared libraries... yes
 checking whether to build static libraries... no
 checking for objdir... .libs
 creating libtool
 checking whether NLS is requested... yes
 checking for msgfmt... /usr/bin/msgfmt
 checking for gmsgfmt... /usr/bin/msgfmt
 checking for xgettext... /usr/bin/xgettext
 checking for socket in -lsocket... no
 checking for X... libraries , headers
 checking for QT... libraries /usr/share/qt3/lib, headers /usr/share/qt3/include
 checking if Qt compiles without flags... no
 checking for moc... /usr/bin/moc
 checking for rpath... yes
 checking for bool... yes
 checking for KDE... will be installed in /usr/local/kde
 checking for extra includes... no
 checking for extra libs... no
 checking for KDE paths... problems
 configure: error: configure can not run a little KDE program to test the environment.
 Look at config.log for details. If you are not able to fix this, please contact Stephan Kulow <coolo@kde.org>.
 
 Verstehen Sie jetzt, wie dumm ich hier in die Roehre kucke?
 Dirk
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 07.01.2008, 06:05 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 28. Feb 2005
 Beiträge: 1112
 Wohnort: Camelot
 
 |  | 
        
          | ---> checking for KDE... will be installed in /usr/local/kde 
 musst auch den Pfad zu den kde-headern angeben, das Programm sucht den in /usr/local und das stimmt ja nicht
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
          |   | Titel:  Verfasst am: 07.01.2008, 16:35 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 18. Okt 2006
 Beiträge: 185
 
 
 |  | 
        
          | Da stimme ich zu. Nur habe ich noch nicht das Argument in der Befehlszeile gefunden das zu tun. Auch, seit meiner letzten Bekanntgebung habe ich 'kdelibs4-dev' installiert, was noch mal die Fehlerberichtung geaendert hat. Jetzt sieht meine config.log Datei so aus: 
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
 configure:595: checking host system type
 configure:616: checking target system type
 configure:634: checking build system type
 configure:687: checking for a BSD compatible install
 configure:740: checking whether build environment is sane
 configure:778: checking whether make sets ${MAKE}
 configure:824: checking for working aclocal
 configure:837: checking for working autoconf
 configure:850: checking for working automake
 configure:863: checking for working autoheader
 configure:876: checking for working makeinfo
 configure:911: checking for a C-Compiler
 configure:917: checking for gcc
 configure:1020: checking whether the C compiler (gcc  ) works
 configure:1034: gcc -o conftest    conftest.c  1>&5
 configure:1054: checking whether the C compiler (gcc  ) is a cross-compiler
 configure:1059: checking whether we are using GNU C
 configure:1068: gcc -E conftest.c
 configure:1125: checking how to run the C preprocessor
 configure:1146: gcc -E  conftest.c >/dev/null 2>conftest.out
 configure:1187: checking for a C++-Compiler
 configure:1193: checking for g++
 configure:1305: checking whether the C++ compiler (g++  -s) works
 configure:1319: g++ -o conftest   -s conftest.C  1>&5
 configure:1345: checking whether the C++ compiler (g++  -s) is a cross-compiler
 configure:1350: checking whether we are using GNU C++
 configure:1359: g++ -E conftest.C
 configure:1434: checking for ranlib
 configure:1473: checking for ld used by GCC
 configure:1530: checking if the linker (/usr/bin/ld) is GNU ld
 GNU ld version 2.17 Debian GNU/Linux
 configure:1546: checking for BSD-compatible nm
 configure:1583: checking whether ln -s works
 configure:1681: checking whether NLS is requested
 configure:1702: checking for msgfmt
 configure:1736: checking for gmsgfmt
 configure:1768: checking for xgettext
 configure:1815: checking for socket in -lsocket
 configure:1834: gcc -o conftest -O2 -Wall  -s conftest.c -lsocket   1>&5
 /usr/bin/ld: cannot find -lsocket
 collect2: ld returned 1 exit status
 configure: failed program was:
 #line 1823 "configure"
 #include "confdefs.h"
 /* Override any gcc2 internal prototype to avoid an error.  */
 /* We use char because int might match the return type of a gcc2
 builtin and then its argument prototype would still apply.  */
 char socket();
 
 int main() {
 socket()
 ; return 0; }
 configure:1860: checking for X
 configure:1877: gcc -E  conftest.c >/dev/null 2>conftest.out
 configure:1953: gcc -o conftest -O2 -Wall  -s conftest.c -lXt  1>&5
 configure: In function 'main':
 configure:1949: warning: implicit declaration of function 'XtMalloc'
 configure:2093: checking for QT
 configure:2242: checking if Qt compiles without flags
 configure:2280: g++ -o conftest -O2 -Wall -I/usr/share/qt3/include   conftest.C -lqt -lXext -lX11  1>&5
 /usr/bin/ld: cannot find -lqt
 collect2: ld returned 1 exit status
 configure: failed program was:
 #include "confdefs.h"
 #include <qmovie.h>
 int main() {
 QMovie m;
 m.setSpeed(20);
 return 0;
 }
 configure:2332: checking for moc
 configure:2366: checking for rpath
 configure:2386: checking for bool
 configure:2406: g++ -c -O2 -Wall  conftest.C 1>&5
 configure: In function 'int main()':
 configure:2402: warning: unused variable 'aBool'
 configure:2429: checking for KDE
 configure:2551: checking for extra includes
 configure:2578: checking for extra libs
 configure:2647: checking for KDE paths
 configure:2714: /bin/sh ./libtool --mode=link g++ -o conftest -O2 -Wall -I/usr/include/kde -I/usr/share/qt3/include   -s -L/usr/share/qt3/lib  conftest.C  -lkdecore -lqt -lXext -lX11  -rpath /usr/lib -rpath /usr/share/qt3/lib  1>&5
 g++ -o conftest -O2 -Wall -I/usr/include/kde -I/usr/share/qt3/include -s -L/usr/share/qt3/lib conftest.C -lkdecore -lqt -lXext -lX11 -Wl,--rpath -Wl,/usr/lib -Wl,--rpath -Wl,/usr/share/qt3/lib
 conftest.C: In function 'int main()':
 conftest.C:7: error: 'kde_htmldir' is not a member of 'KApplication'
 conftest.C:8: error: 'kde_appsdir' is not a member of 'KApplication'
 conftest.C:9: error: 'kde_icondir' is not a member of 'KApplication'
 conftest.C:10: error: 'kde_datadir' is not a member of 'KApplication'
 conftest.C:11: error: 'kde_localedir' is not a member of 'KApplication'
 conftest.C:12: error: 'kde_cgidir' is not a member of 'KApplication'
 conftest.C:13: error: 'kde_configdir' is not a member of 'KApplication'
 conftest.C:14: error: 'kde_mimedir' is not a member of 'KApplication'
 conftest.C:15: error: 'kde_toolbardir' is not a member of 'KApplication'
 conftest.C:16: error: 'kde_wallpaperdir' is not a member of 'KApplication'
 conftest.C:17: error: 'kde_bindir' is not a member of 'KApplication'
 conftest.C:18: error: 'kde_partsdir' is not a member of 'KApplication'
 
 Das sieht mir inzwischen mehr danach aus, als ob in dem Quellcode irgendwas nicht stimmt. Aber natuerlich werde ich das weiter forschen, wenn ich die Zeit finde.
 
 Danke noch mal, Merlin.
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 07.01.2008, 18:20 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 28. Feb 2005
 Beiträge: 1112
 Wohnort: Camelot
 
 |  | 
        
          | Vergiss es einfach! Das Programm kannst du garantiert nicht mehr compilieren. Es wurde seit ende 1998 nicht mehr weiter entwickelt!
 Kannst es natürlich versuchen auf kde3.x oder gar kde-4 zu portieren. Solltest dazu aber schon gut programmieren können.
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 03.02.2008, 16:46 Uhr |  | 
  
    | 
        
          | 
 
 Anmeldung: 30. Apr 2005
 Beiträge: 63
 
 
 |  | 
        
          | Wahrscheinlich off-topic, sorry. Aber kennt jemand andere freie Programme im Bereich Signalverarbeitung / Fourieranalyse?
 |  
          |  |  
         
	        |  |  | 
  
    |  | 
  
    |  | 
  
    |  | 
        
					| Titel:  Verfasst am: 03.03.2008, 08:14 Uhr |  | 
  
    | 
        
          | 
  
 Anmeldung: 29. Apr 2004
 Beiträge: 393
 Wohnort: Berlin
 
 |  |  | 
  
    |  | 
  
    |  | 
  
  
    |  |