sabari.girish | 2 Feb 14:25 2004

Error while running Configure after creating a new project in Kdevelop -3.1.4

Hi,
 
I have installed the KDE-Cygwin(3.1.4 release) environment along with
Kdevelop 3.0.0b1 release . In Kdevelop,I created a new project
(the simple Hello world). While trying to "Run Configure" from the "BUILD" menu,
I am getting the following messages below:
________________________________________________________________________________________________________
*cd /home/sabarig/CPrograms/travelplanner/hello && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" make -f Makefile.cvs && cd /home/sabarig/CPrograms/travelplanner/hello/debug && CFLAGS="-O0 -g3" /home/sabarig/CPrograms/travelplanner/hello/configure --enable-debug=full && cd /home/sabarig/CPrograms/travelplanner/hello/debug && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" make -k distclean
*checking for suffix of executables... aclocal
*autoheader
*autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
*autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
*autoheader: WARNING: is deprecated and discouraged.
*autoheader: 
*autoheader: WARNING: Using the third argument of `AC_DEFINE' and
*autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
*autoheader: WARNING: `acconfig.h':
*autoheader: 
*autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
*autoheader: [Define if a function `main' is needed.])
*autoheader: 
*autoheader: WARNING: More sophisticated templates can also be produced, see the
*autoheader: WARNING: documentation.
*automake
*autoconf
*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 for gcc... gcc
*checking for C compiler default output file name... a.exe
*checking whether the C compiler works... yes
*checking whether we are cross compiling... no
*checking for suffix of executables... .exe
*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 build system type... i686-pc-cygwin
*checking host system type... i686-pc-cygwin
*checking for a sed that does not truncate output... /usr/bin/sed
*checking for egrep... grep -E
*checking for ld used by gcc... /usr/i686-pc-cygwin/bin/ld.exe
*checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes
*checking for /usr/i686-pc-cygwin/bin/ld.exe 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... file_magic ^x86 archive import|^x86 DLL
*checking how to run the C preprocessor... gcc -E
*checking for ANSI C header files... yes
*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 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 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... 8192
*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 static flag works... yes
*checking if gcc supports -fno-rtti -fno-exceptions... no
*checking for gcc option to produce PIC... 
*checking if gcc supports -c -o file.o... yes
*checking whether the gcc linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes
*checking whether -lc should be explicitly linked in... yes
*checking how to hardcode library paths into programs... immediate
*checking whether stripping libraries is possible... yes
*checking dynamic linker characteristics... Win32 ld.exe
*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/i686-pc-cygwin/bin/ld.exe
*checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld... yes
*checking whether the g++ linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes
*checking for g++ option to produce PIC... 
*checking if g++ supports -c -o file.o... yes
*checking whether the g++ linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes
*checking how to hardcode library paths into programs... immediate
*checking whether stripping libraries is possible... yes
*checking dynamic linker characteristics... Win32 ld.exe
*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... 
*checking if g77 supports -c -o file.o... yes
*checking whether the g77 linker (/usr/i686-pc-cygwin/bin/ld.exe) supports shared libraries... yes
*checking how to hardcode library paths into programs... immediate
*checking whether stripping libraries is possible... yes
*checking dynamic linker characteristics... Win32 ld.exe
**** Exited with status: 1 ***
________________________________________________________________________________________________________
 
Can anyone help me out of this problem?
 
Thanks in advance.
 
Best Regards,
Sabari

Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or Mailadmin <at> wipro.com immediately and destroy all copies of this message and any attachments.
_______________________________________________
kde-cygwin mailing list
kde-cygwin <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-cygwin
Ralf Habacker | 2 Feb 15:05 2004
Picon

Re: Error while running Configure after creating a new project in Kdevelop -3.1.4

On Monday 02 February 2004 14:25, sabari.girish <at> wipro.com wrote:
> I have installed the KDE-Cygwin(3.1.4 release) environment along with
> Kdevelop 3.0.0b1 release . In Kdevelop,I created a new project
> (the simple Hello world). While trying to "Run Configure" from the
> "BUILD" menu,
> I am getting the following messages below:

I have two questions

1. What is the last error reported in config.log ? 
2. Does the related configure command run from a bash shell ? 

Ralf 
sabari.girish | 2 Feb 15:33 2004

RE: Error while running Configure after creating a new project in Kdevelop -3.1.4


Hi Ralf,

I did not run the configure command from the Bash shell.
I chose the configure command from the Kdevelop  "BUILD" Menu.
First I got the KDE running by issuing "start &".
Then I chose the Kdevelop application and created a
New project. Then I tried to Build the project.
That was when I got the messages and finally the error which
I had mailed you.

Please find attached the "Config" file which was generated by
Configure command.

Please do let me know if you need any further info.

Thanks a lot for responding to this mail. Kindly help me
With this issue.

Best Regards,
Sabari

-----Original Message-----
From: Ralf Habacker [mailto:ralf.habacker <at> freenet.de]
Sent: Monday, February 02, 2004 7:35 PM
To: For developers interested in porting KDE to Windows using Cygwin;
Sabari Girish (WT01 - TELECOM SERVICE PROVIDER)
Subject: Re: Error while running Configure after creating a new project
in Kdevelop -3.1.4

On Monday 02 February 2004 14:25, sabari.girish <at> wipro.com wrote:
> I have installed the KDE-Cygwin(3.1.4 release) environment along with
> Kdevelop 3.0.0b1 release . In Kdevelop,I created a new project (the
> simple Hello world). While trying to "Run Configure" from the "BUILD"
> menu, I am getting the following messages below:

I have two questions

1. What is the last error reported in config.log ?
2. Does the related configure command run from a bash shell ?

Ralf

Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin <at> wipro.com immediately
and destroy all copies of this message and any attachments.
Attachment (config.log): application/octet-stream, 38 KiB
_______________________________________________
kde-cygwin mailing list
kde-cygwin <at> kde.org
https://mail.kde.org/mailman/listinfo/kde-cygwin
Kleag | 3 Feb 23:26 2004
Picon

Re: Cygwin Kdevelop no Hello World

Hello,

I had the same problem. If you look at the end of the message, you see that 
the perl scrip "/opt/kde3/..../script" fails at line 3 with a wrong  <at> INC 
variable. In fact, this varaible is defined in the same script as such:
"#!perl 
-I/var/tmp/portage/kdevelop-3.0.0-r8/image//opt/kde3/share/apps/kdevappwizard/temp
late-common"

The path is wrong. If you remove "/var/tmp/portage/kdevelop-3.0.0-r8/image/", 
it works (at least for me).

It seems to me that it's the same for other project-generation scripts. 

Cheers,

Kleag

Le jeudi 29 Janvier 2004 15:17, Charles Repetti a écrit :
> Hello, Mr. Amilcar Lucas, and thank you for your response. I have
> enclosed a screen shot to help clarify my results. As you may see, there
> is no "new" option under file. Also, the script error in the message box
> came from the "Simple Hello World" option from the new project
> selection.
>
>  - Charlie
>
> -----Original Message-----
> From: Amilcar do Carmo Lucas [mailto:amilcar <at> ida.ing.tu-bs.de]
> Sent: Thursday, January 29, 2004 12:22 AM
> To: kdevelop-devel <at> kdevelop.org; Charlie <at> Camper-Thermostat.com
> Subject: Re: Cygwin Kdevelop no Hello World
>
> Charles Repetti wrote:
> >I installed KDevelop/Cygwin as per instructions. It looks great!
>
> Thanks.
>
> > But it
> >would not start a new hello world project. A script error was reported,
>
> Wich error? You have to be more precise so that we can help you!
>
> >and I could see no way to simply start a new file.
>
> File-> New  works fine here! :)
>
> Have fun,
Ralf Habacker | 3 Feb 23:54 2004
Picon

Re: Cygwin Kdevelop no Hello World

On Tuesday 03 February 2004 23:26, Kleag wrote:
> Hello,
>
> I had the same problem. If you look at the end of the message, you see that
> the perl scrip "/opt/kde3/..../script" fails at line 3 with a wrong  <at> INC
> variable. In fact, this varaible is defined in the same script as such:
> "#!perl
> -I/var/tmp/portage/kdevelop-3.0.0-r8/image//opt/kde3/share/apps/kdevappwiza
>rd/temp late-common"
>
> The path is wrong. If you remove
> "/var/tmp/portage/kdevelop-3.0.0-r8/image/", it works (at least for me).
>
> It seems to me that it's the same for other project-generation scripts.
>
This is a packaging issue, because in my build system (using portage) i 
install a package temporary with make install 
prefix=/var/tmp/portage/kdevelop-3.0.0-r8/image//opt/kde3 and the kde 
Makefile takes over the path into the perl scripts. I have reported this 
problem some time ago to bugs.kde.org (see 
http://bugs.kde.org/show_bug.cgi?id=66155),  but it seems that noone else use 
such a build enviroment :-(, so I have to find a way to avoid this in further 
releases. 

A workaround could be found in 
https://sourceforge.net/tracker/index.php?func=detail&aid=822303&group_id=27249&atid=389712

Ralf 

>
> Le jeudi 29 Janvier 2004 15:17, Charles Repetti a écrit :
> > Hello, Mr. Amilcar Lucas, and thank you for your response. I have
> > enclosed a screen shot to help clarify my results. As you may see, there
> > is no "new" option under file. Also, the script error in the message box
> > came from the "Simple Hello World" option from the new project
> > selection.
> >
> >  - Charlie
> >
> > -----Original Message-----
> > From: Amilcar do Carmo Lucas [mailto:amilcar <at> ida.ing.tu-bs.de]
> > Sent: Thursday, January 29, 2004 12:22 AM
> > To: kdevelop-devel <at> kdevelop.org; Charlie <at> Camper-Thermostat.com
> > Subject: Re: Cygwin Kdevelop no Hello World
> >
> > Charles Repetti wrote:
> > >I installed KDevelop/Cygwin as per instructions. It looks great!
> >
> > Thanks.
> >
> > > But it
> > >would not start a new hello world project. A script error was reported,
> >
> > Wich error? You have to be more precise so that we can help you!
> >
> > >and I could see no way to simply start a new file.
> >
> > File-> New  works fine here! :)
> >
> > Have fun,
>
> _______________________________________________
> kde-cygwin mailing list
> kde-cygwin <at> kde.org
> https://mail.kde.org/mailman/listinfo/kde-cygwin
Ralf Habacker | 4 Feb 00:32 2004
Picon

new feature: using windows truetype fonts for better font displays

Hi, 
in the last day i've figured out how to use windows truetype fonts with 
KDE-cygwin, which results in a much better visibility. See 
http://kde-cygwin.sourceforge.net/kde3/faq.php#truetype for further 
informations. 

Any feedback about this topic is welcome. 

Ralf 
Dominik Stadler | 6 Feb 15:21 2004
Picon

Switching to KDE with ALT-TAB always opens the menu


Hi, 

I am using KDE 3.1.4 for Cygwin in "multiwindow" mode where
KDE-Applications are shown as separate tasks in Windows.

Normally I have konsole running to connect to some Unix-boxes. When I
switch with ALT-Tab to this window, it seems that the release of the
ALT-Key from using ALT-Tab is sent to konsole, because I always get the
menu selected and can not type away, but have to press ESC first before I
can start typing. 

This is very annoying as it is different as with other
Windows applications.

Is there a way to configure KDE/Cygwin so it doesn't do this?

Dominik.
Holger Karl | 8 Feb 11:18 2004
Picon

kmail maildir patches???

Hello,

I admit to being completely smitten with KDE on cygwin! Especially the fact 
that kmail can use maildir is almost enough to make me throw away outlook.

Why almost? Because I still can't sync with kmail on a linux box, as the 
maildir filenames  have ":" on linux and "." on windows (obviously, since : 
causes problems). 

Now: did you patch the kamil source code? would this patch be applicable to 
the standard  kmail as well? (Is there a chance to get the kamil-folks make 
the : <-> . thing configurable, so it is easy to decide which format to use - 
wrong people to ask here, I know).  Or did you do something else?

If that would work, lots of problems would go away for me!

Thanks and bundle and keep up the most impressive work!

Holger
Christian Hohnstaedt | 10 Feb 09:16 2004
Picon

qt-win32

Hello List,

I am developing a QT application (a free one of course) and
the W32 part is a mess with VC++ and qt-mt230nc.
	http://www.hohnstaedt.de/xca/xca.html

So I'm very intrested in a qt-win32 version to be used with the 
MinGW cross compiler.

Is your port already usable ? Is it actively developed ?
Can I participate ? How far is the light at the end of the tunnel ?

Best regards

Christian
IVAN DE JESUS DERAS TABORA | 10 Feb 15:49 2004
Picon
Picon

Re: qt-win32

 --- Christian Hohnstaedt <christian <at> hohnstaedt.de>
escribió: > Hello List,
> 
> I am developing a QT application (a free one of
> course) and
> the W32 part is a mess with VC++ and qt-mt230nc.
> 	http://www.hohnstaedt.de/xca/xca.html
> 
> So I'm very intrested in a qt-win32 version to be
> used with the 
> MinGW cross compiler.
> 
> Is your port already usable ? 
Not at all!!! But you could see some screenshots in
qt3-Win32 page!!!

>Is it actively developed ?
No!! :-(

> Can I participate ? 
Yes, that would be great, we need developers!!!

>How far is the light at the end of the tunnel ?
Well, no comments!!!

> 
> Best regards
> 
> Christian
> _______________________________________________
> kde-cygwin mailing list
> kde-cygwin <at> kde.org
> https://mail.kde.org/mailman/listinfo/kde-cygwin 

___________________________________________________
Yahoo! Messenger - Nueva versión GRATIS
Super Webcam, voz, caritas animadas, y más...
http://messenger.yahoo.es

Gmane