[email protected]
[Top] [All Lists]

Re: [Tkabber] Problems compiling tclgpgme on Suse 10.2

Subject: Re: [Tkabber] Problems compiling tclgpgme on Suse 10.2
From: Paul Rauch
Date: Wed, 03 Jan 2007 21:31:31 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sergei Golovan schrieb:
> On 1/3/07, Paul Rauch <[email protected]> wrote:
>> I managed to build gpgme 0.3.16 now :)
>> proceding to tclgpgme
>> it has problems to find tcl config. could you happen to know where it's
>> located on suse?
> 
> I guess, you have to install tcl-devel (or something like that).
> 
i did that already. tcl-devel has been installed
here the debug output:

checking for Tcl configuration... configure: error: yes directory
doesn't contain tclConfig.sh
error: Bad exit status from /var/tmp/rpm-tmp.24166 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.24166 (%build)

as an attachment you'll get the configure log from tclgpgme

mfg Light Lan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iQIVAwUBRZwSoxG67lyyQrltAQJf2hAApxc62PAqh1SKNshHrxmKGz2RhCUKgePd
BLX6zFaMd3MGVcbcejSa/6FWYdIvcly3OUdEdnZKxkI6FDcc0O77Tdim98+GKWVU
65uLv9wvAjikEJOMbWyb0CYEyVgF9PbmgFedTGo+NAQ2YGDeOE6vNx+CFISpKy8w
sQACxrpr3qeV+ri0fMz6DKesvJ3QXDFhpsydPGLnVt/2HFHhevrzyUDGoCyFIM5y
Fz4nabIKWCHnI6hwZvyYOS7LrZ0KZU0FqoEagSKU4Ol/WUbvPV/m51JZv4mCgqqz
uMvYeMWUa/mpo5Zqdzpq/S0HYxQOAUZNmen6YXfSmi5k4sGE7TiSGnq2jKr1PHqw
FF+bsLjKGNSpRu5z1cVgdcINI+K41ViTs5lgcQ5Pr/9xSMWGA9CEeozMyzNnG8q4
nTXpYwy6YGrwAckdlR6PebjKE+r27+VFfbNjwBpP1bjUafHPt6EmoMg+JpGkofS9
5KGGYtlKZfxQ+tgk7zCYlmfTkUuW8nwImJcGFHUGlNN5a171b/zCfCcBjAgMMU5C
imiNLmO2Pe8KvHLCKNhkCCImN4On+o04ZQEYeURtOjV3A20b/qpcdhwmvEuyz/QH
ZXC/f2k1TQlK1eZbyaOWSFg48jrtpuOqlKa/vyPBnM/frqD2tsatZHR6fn56BHEo
5US6JVeiqv8=
=m9lT
-----END PGP SIGNATURE-----
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:551: checking for Cygwin environment
configure:567: cc -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2  conftest.c 
1>&5
configure: In function 'main':
configure:563: error: '__CYGWIN32__' undeclared (first use in this function)
configure:563: error: (Each undeclared identifier is reported only once
configure:563: error: for each function it appears in.)
configure: failed program was:
#line 556 "configure"
#include "confdefs.h"

int main() {

#ifndef __CYGWIN__
#define __CYGWIN__ __CYGWIN32__
#endif
return __CYGWIN__;
; return 0; }
configure:584: checking for mingw32 environment
configure:596: cc -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2  conftest.c 
1>&5
configure: In function 'main':
configure:592: error: '__MINGW32__' undeclared (first use in this function)
configure:592: error: (Each undeclared identifier is reported only once
configure:592: error: for each function it appears in.)
configure: failed program was:
#line 589 "configure"
#include "confdefs.h"

int main() {
return __MINGW32__;
; return 0; }
configure:637: checking for gcc
configure:750: checking whether the C compiler (gcc -O2 -g -fmessage-length=0 
-D_FORTIFY_SOURCE=2 ) works
configure:766: gcc -o conftest -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2   
conftest.c  1>&5
configure:792: checking whether the C compiler (gcc -O2 -g -fmessage-length=0 
-D_FORTIFY_SOURCE=2 ) is a cross-compiler
configure:797: checking whether we are using GNU C
configure:806: gcc -E conftest.c
configure:825: checking whether gcc accepts -g
configure:932: checking host system type
configure:953: checking build system type
configure:982: checking for ld used by GCC
configure:1050: checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld
GNU ld version 2.17.50.0.5 20060927 (SUSE Linux)
configure:1067: checking for /usr/x86_64-suse-linux/bin/ld option to reload 
object files
configure:1079: checking for BSD-compatible nm
configure:1117: checking whether ln -s works
configure:1138: checking how to recognise dependant libraries
configure:1302: checking for object suffix
configure:1308: gcc -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2  
conftest.c 1>&5
configure:1328: checking for executable suffix
configure:1338: gcc -o conftest -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2   
conftest.c  1>&5
configure:1371: checking for file
configure:1504: checking for ranlib
configure:1571: checking for strip
ltcf-c.sh:need_lc: gcc -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2  
conftest.c 1>&5
ltcf-c.sh:need_lc: gcc -shared conftest.  -v -Wl,-soname -Wl,conftest -o 
conftest
ltconfig:678:checking for gcc option to produce PIC
ltconfig:687:checking that gcc PIC flag -fPIC -DPIC works.
ltconfig:697: gcc -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fPIC -DPIC 
-DPIC  conftest.c 1>&5
ltconfig:749: checking if gcc static flag -static works
ltconfig:758: gcc -o conftest -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2   
-static conftest.c  1>&5
ltconfig:780: finding the maximum length of command line arguments
ltconfig:@[email protected]: result: 49153
ltconfig:833: checking if gcc supports -c -o file.o
ltconfig:834: gcc -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -o 
out/conftest2.o  conftest.c 1>&5
ltconfig:887: checking if gcc supports -fno-rtti -fno-exceptions
ltconfig:888: gcc -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fno-rtti 
-fno-exceptions -c conftest.c  conftest.c 1>&5
ltconfig:1432: checking if global_symbol_pipe works
ltconfig:1433: gcc -c -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2  conftest.c 
1>&5
ltconfig:1436: eval "/usr/bin/nm -B conftest.o | sed -n -e 's/^.*[      
]\([ABCDGISTW][ABCDGISTW]*\)[   ][      ]*\(\)\([_A-Za-z][_A-Za-z0-9]*\)$/\1 
\2\3 \3/p' > conftest.nm"
ltconfig:1488: gcc -o conftest -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 
-fno-builtin   conftest.c conftstm.o 1>&5
configure:1845: checking for gpgme-config
configure:1880: checking for GPGME - version >= 0.3.0
configure:1991: checking for gcc
configure:2104: checking whether the C compiler (gcc -O2 -g -fmessage-length=0 
-D_FORTIFY_SOURCE=2 ) works
configure:2120: gcc -o conftest -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2   
conftest.c  1>&5
configure:2146: checking whether the C compiler (gcc -O2 -g -fmessage-length=0 
-D_FORTIFY_SOURCE=2 ) is a cross-compiler
configure:2151: checking whether we are using GNU C
configure:2179: checking whether gcc accepts -g
configure:2223: checking for a BSD compatible install
configure:2281: checking whether make sets ${MAKE}
configure:2315: checking for ranlib
configure:2348: checking for Cygwin environment
configure:2386: checking for object suffix
configure:2412: checking for executable suffix
configure:2488: checking for Tcl configuration
_______________________________________________
Tkabber mailing list
[email protected]
http://lists.jabber.ru/mailman/listinfo/tkabber
<Prev in Thread] Current Thread [Next in Thread>