kdiff3-user — User questions about KDiff3.

Re: [Kdiff3-user] Desktop file install issue

[Joachim E. <joa...@gm...>]

Hi Neal,

I don't know enough about desktop files to help here, but I know that the 
libkdiff3part.so isn't essential anymore, since everything is in the 
kdiff3-executable now.

The libkdiff3part.so would only be necessary for other programs like KDevelop 
to integrate KDiff3. But since KDevelop4 isn't ready yet, I didn't test this 
anyway.

So just don't install libkdiff3part.so and kdiff3part.desktop if possible.

Joachim

Am Tuesday 06 January 2009 17:27:13 schrieb Neal Becker:
> Desktop files must be installed using desktop-file-install on fedora.
>
> desktop-file-install gives an error:
>
> desktop-file-install --vendor fedora --dir
> /home/nbecker/RPM/BUILDROOT/kdiff3-0.9.93-1.fc11.x86_64/usr/share/kde4/serv
>ices
> /home/nbecker/RPM/BUILDROOT/kdiff3-0.9.93-1.fc11.x86_64/usr/share/kde4/serv
>ices/kdiff3part.desktop
>
> /home/nbecker/RPM/BUILDROOT/kdiff3-0.9.93-1.fc11.x86_64/usr/share/kde4/serv
>ices/fedora- kdiff3part.desktop: error: key "MimeType" is present in group
> "Desktop Entry", but the type is "Service" while this key is only valid for
> type "Application"
>
> I don't really know much about desktop files, is there something wrong with
> kdiff3part.desktop as desktop-file-install says?

[Kdiff3-user] Desktop file install issue

[Neal B. <ndb...@gm...>]

Desktop files must be installed using desktop-file-install on fedora.

desktop-file-install gives an error:

desktop-file-install --vendor fedora --dir 
/home/nbecker/RPM/BUILDROOT/kdiff3-0.9.93-1.fc11.x86_64/usr/share/kde4/services 
/home/nbecker/RPM/BUILDROOT/kdiff3-0.9.93-1.fc11.x86_64/usr/share/kde4/services/kdiff3part.desktop

/home/nbecker/RPM/BUILDROOT/kdiff3-0.9.93-1.fc11.x86_64/usr/share/kde4/services/fedora-
kdiff3part.desktop: error: key "MimeType" is present in group "Desktop Entry", 
but the type is "Service" while this key is only valid for type "Application"

I don't really know much about desktop files, is there something wrong with 
kdiff3part.desktop as desktop-file-install says?

Re: [Kdiff3-user] Kdiff3 deletes directory instead of updating files during merge

[Joachim E. <joa...@gm...>]

Hi A.D,

I wasn't able to reproduce the problem with the new version I released today.
Perhaps you could also give it a try and please inform me if the problem 
remains.

Cheers,
Joachim

Am Wednesday 17 December 2008 09:38:37 schrieb androdev k:
> Please help.
>
> When I run directory merge (F7), KDiff3 first deletes the folder in the
> destination (C), and copies the files from the source (B). So if my
> destination folder contains "ignored" content such as CVS folder, binary
> content, etc. they will all be deleted/lost.
>
> This is the simulation run output:
> delete directory recursively( <C>/commoncpp )
> delete directory recursively( <C>/commoncpp/src )
> delete directory recursively( <C>/commoncpp/src/common )
> delete( <C>/commoncpp/src/common/DatabaseException.cpp )
> copy( <B>/commoncpp/src/common/DatabaseException.cpp ->
> <C>/commoncpp/src/common/DatabaseException.cpp )
> delete( <C>/commoncpp/src/common/DatabaseException.h )
> copy( <B>/commoncpp/src/common/DatabaseException.h ->
> <C>/commoncpp/src/common/DatabaseException.h )
>
> How can I change this behaviour? Deleting <C> folders just to update one of
> the files inside has very bad side effects.
>
> Thanks.
> A.D

Re: [Kdiff3-user] KDiff3-0.9.93 released

[Neal B. <ndb...@gm...>]

On Tuesday 06 January 2009, Joachim Eibl wrote:
> Am Tuesday 06 January 2009 16:41:48 schrieb Neal Becker:
> > On Tuesday 06 January 2009, Joachim Eibl wrote:
> > > Hi KDiff3-Users,
> > >
> > > After a very long wait finally KDiff3-0.9.93 is ready to download.
> >
> > Great!  Where is the download?
>
> Hi,
> Using the Download-link an kdiff3.sourceforge.net should take you there.
> Select 0.9.93 and then the file to download.
> At the moment only the source package and the windows version are
> available. Other binaries will follow when users of the respective systems
> send them to me for upload.
>
I maintain kdiff3 on fedora.  I'm working on an update now.

Re: [Kdiff3-user] KDiff3-0.9.93 released

[Joachim E. <joa...@gm...>]

Am Tuesday 06 January 2009 16:41:48 schrieb Neal Becker:
> On Tuesday 06 January 2009, Joachim Eibl wrote:
> > Hi KDiff3-Users,
> >
> > After a very long wait finally KDiff3-0.9.93 is ready to download.
>
> Great!  Where is the download?

Hi,
Using the Download-link an kdiff3.sourceforge.net should take you there.
Select 0.9.93 and then the file to download.
At the moment only the source package and the windows version are available.
Other binaries will follow when users of the respective systems send them to 
me for upload.

Cheers,
Joachim

Re: [Kdiff3-user] KDiff3-0.9.93 released

[Neal B. <ndb...@gm...>]

On Tuesday 06 January 2009, Joachim Eibl wrote:
> Hi KDiff3-Users,
>
> After a very long wait finally KDiff3-0.9.93 is ready to download.
>

Great!  Where is the download?

[Kdiff3-user] KDiff3-0.9.93 released

[Joachim E. <joa...@gm...>]

Hi KDiff3-Users,

After a very long wait finally KDiff3-0.9.93 is ready to download.

Here is the short ChangeLog.

Version 0.9.93 - 2008/01/06
===========================
- Support for KDE4 (with much porting help from Valentin Rusu)
- Fix for diff_ext_for_kdiff3 (by Sergey Zorin)
- Win32-Installation: SendTo-integration fixed for Vista.
- Optional auto detection of line end style for saving.
- Option to close on ESC (default is off)

Although the list is very short, this is a very big step. The switch to KDE4 
implies switching to cmake as build system, testing almost all existing 
features, fixing tons of issues to avoid as many regressions as possible. The 
Qt4-version (without KDE4) is also much improved. This is especially relevant 
for Windows and Mac users.

Without the help of Valentin Rusu who volunteered to do the port of the build 
system and made the code compile again against KDE4-libs this wouldn't have 
happened. - Thanks a lot!

Still there remained many more details until this release was possible.
I decided to drop the Qt3/KDE3 version completely because this would have been 
a maintenance nightmare. Anybody who needs it can continue with 0.9.92, but 
except for few details (like Konqueror-context-menu) the KDE4-version also 
works with KDE3.

As a private note I must confess, that I don't have as much time anymore for 
KDiff3. It is foreseeable that improvements from my side will be possible at 
a rather very slow pace. So if you want a feature or bugfix it might not 
happen unless somebody volunteers to invest time to get it to work.
If you want to help: Now there exists a new free IDE "Qt Creator" from 
trolltech.com that runs on all platforms. It has much support for 
editing/compiling and debugging Qt4-programs.

I hope the porting-job (like Qt3 to Qt4 and KDE3 to KDE4) need never be 
repeated, because it's so much effort and you - the users - don't have much 
benefit for a very long time. I did it to provide a good basis for the 
future, and in the hope that it will be easier for others to help.

So have fun with the new version of KDiff3 and a happy new year 2009!
Joachim

[Kdiff3-user] Kdiff3 deletes directory instead of updating files during merge

[androdev k <and...@gm...>]

Please help.

When I run directory merge (F7), KDiff3 first deletes the folder in the
destination (C), and copies the files from the source (B). So if my
destination folder contains "ignored" content such as CVS folder, binary
content, etc. they will all be deleted/lost.

This is the simulation run output:
delete directory recursively( <C>/commoncpp )
delete directory recursively( <C>/commoncpp/src )
delete directory recursively( <C>/commoncpp/src/common )
delete( <C>/commoncpp/src/common/DatabaseException.cpp )
copy( <B>/commoncpp/src/common/DatabaseException.cpp ->
<C>/commoncpp/src/common/DatabaseException.cpp )
delete( <C>/commoncpp/src/common/DatabaseException.h )
copy( <B>/commoncpp/src/common/DatabaseException.h ->
<C>/commoncpp/src/common/DatabaseException.h )

How can I change this behaviour? Deleting <C> folders just to update one of
the files inside has very bad side effects.

Thanks.
A.D

Re: [Kdiff3-user] Kdiff3: Diff saving

[Joachim E. <joa...@gm...>]

Hi Ivo,

> I'm a big fan of Kdiff since some time now (and even wonder when version 1
> will be released...).

Thank you. A next version is not far away, but if I will ever arrive at 1.0 I 
don't know. ;-)

> I have a suggestion:
> I would like to have the chance to save a diff status of files or folders.
> I explain: I often need to diff folder content which need to be merged but
> there are always differences which should always exist.
> So what I propose is the chance of saving a diff status and use it next
> time (optionally) I make a diff of those folder in order to have the
> desired differences ignored (avoiding having to go through every file again
> and again)...
>
> If this already exists and I didn't notice it, accept my apologies :-)
> If not, would it be possible?

I once started to implement such a feature, but it turned out to be too 
complicated, given the limited time I had. Sorry. Perhaps some later time.

Joachim

[Kdiff3-user] Kdiff3: Diff saving

[I. G. <ibe...@gm...>]

Hi there! :-)

I'm a big fan of Kdiff since some time now (and even wonder when version 1
will be released...).

I have a suggestion:
I would like to have the chance to save a diff status of files or folders. I
explain: I often need to diff folder content which need to be merged but
there are always differences which should always exist.
So what I propose is the chance of saving a diff status and use it next time
(optionally) I make a diff of those folder in order to have the desired
differences ignored (avoiding having to go through every file again and
again)...

If this already exists and I didn't notice it, accept my apologies :-)
If not, would it be possible?

Thanks in advance,
    iG

-- 
---
Ivo Belchior Gonçalves

Re: [Kdiff3-user] Newbie - installation trouble, help required.

[Joachim E. <joa...@gm...>]

Hi Vinodh,

> checking for Qt... configure: error: Qt (>= Qt 3.2 and < 4.0) (headers
> and libraries) not found. Please check your installation!

> blr-mcp-bld-02-64> cd /usr/lib/qt-3.3/
> blr-mcp-bld-02-65> ls
> bin  etc  lib  plugins

You are probably missing the Qt3-"include"-directory which would be in a so 
called "devel"-package.
On Opensuse it is called "qt3-devel" (to be installed via yast).
You also need "kdelibs3-devel" and "kdebase3-devel". (Opensuse-package names.)

Cheers,
Joachim


Am Montag 20 Oktober 2008 18:42:23 schrieb Vinodh Rajaraman (vrajaram):
> Hi
>
>
>
> I am trying to install kdiff3 on my linux server, for the first time.
> Ran into install issue, hope someone can point out my mistakes. Please
> let me know if information provided below is insufficient.
>
>
>
> blr-mcp-bld-02-62> uname -a
>
> Linux blr-mcp-bld-02 2.6.9-42.7.ELsmp #1 SMP Tue Sep 5 18:29:39 EDT 2006
> i686 i686 i386 GNU/Linux
>
>
>
> Qt version 3.3 is available here at, I have set QTDIR as below.
>
>
>
> blr-mcp-bld-02-63> env | grep QTD
>
> 10:QTDIR=/usr/lib/qt-3.3
>
> blr-mcp-bld-02-64> cd /usr/lib/qt-3.3/
>
> blr-mcp-bld-02-65> ls
>
> bin  etc  lib  plugins
>
> blr-mcp-bld-02-66>
>
>
>
>
>
> I copied the tar and executed the command as below. Installation fails
> on checking for QT.
>
>
>
> blr-mcp-bld-02-60> pwd
>
> /users/vrajaram/tmpsrc/kdif/kdiff3-0.9.92
>
> blr-mcp-bld-02-61> ./configure --prefix=/usr
>
> checking build system type... i686-pc-linux-gnu
>
> checking host system type... i686-pc-linux-gnu
>
> checking target system type... i686-pc-linux-gnu
>
> checking for a BSD-compatible install... /usr/bin/install -c
>
> checking for -p flag to install... yes
>
> checking whether build environment is sane... yes
>
> checking for gawk... gawk
>
> checking whether make sets $(MAKE)... yes
>
> checking for kde-config... /usr/bin/kde-config
>
> checking where to install... /usr (as requested)
>
> 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 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 whether gcc is blacklisted... no
>
> checking whether g++ supports -Wmissing-format-attribute... yes
>
> checking whether gcc supports -Wmissing-format-attribute... yes
>
> checking whether g++ supports -Wundef... yes
>
> checking whether g++ supports -Wno-long-long... yes
>
> checking whether g++ supports -Wno-non-virtual-dtor... yes
>
> checking whether g++ supports -fno-reorder-blocks... yes
>
> checking whether g++ supports -fno-exceptions... yes
>
> checking whether g++ supports -fno-check-new... yes
>
> checking whether g++ supports -fno-common... yes
>
> checking whether g++ supports -fexceptions... yes
>
> checking whether system headers can cope with -O2 -fno-inline...
> irrelevant
>
> checking how to run the C++ preprocessor... g++ -E
>
> checking whether g++ supports -O0... yes
>
> checking whether g++ supports -Wl,--no-undefined... yes
>
> checking whether g++ supports -Wl,--allow-shlib-undefined... yes
>
> not using lib directory suffix
>
> checking for a sed that does not truncate output... /bin/sed
>
> checking for grep that handles long lines and -e... /router/bin/grep
>
> checking for egrep... /router/bin/grep -E
>
> 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 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 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 static flag  works... yes
>
> 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 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 for shl_load... no
>
> checking for shl_load in -ldld... no
>
> checking for dlopen... no
>
> checking for dlopen in -ldl... yes
>
> checking whether a program can dlopen itself... yes
>
> checking whether a statically linked program can dlopen itself... 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++ 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
>
> checking whether stripping libraries is possible... yes
>
> checking for shl_load... (cached) no
>
> checking for shl_load in -ldld... (cached) no
>
> checking for dlopen... (cached) no
>
> checking for dlopen in -ldl... (cached) yes
>
> checking whether a program can dlopen itself... (cached) yes
>
> checking whether a statically linked program can dlopen itself...
> (cached) yes
>
> 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 supports -c -o file.o... yes
>
> checking whether the g77 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
>
> checking whether stripping libraries is possible... yes
>
> checking for msgfmt... /usr/bin/msgfmt
>
> checking for gmsgfmt... /usr/bin/msgfmt
>
> checking for xgettext... /usr/bin/xgettext
>
> checking if C++ programs can be compiled... yes
>
> checking for strlcat... no
>
> checking if strlcat needs custom prototype... yes - in libkdefakes
>
> checking for strlcpy... no
>
> checking if strlcpy needs custom prototype... yes - in libkdefakes
>
> checking for main in -lutil... yes
>
> checking for main in -lcompat... no
>
> checking for crypt in -lcrypt... yes
>
> checking for socklen_t... yes
>
> checking for dnet_ntoa in -ldnet... no
>
> checking for dnet_ntoa in -ldnet_stub... no
>
> checking for inet_ntoa... yes
>
> checking for connect... yes
>
> checking for remove... yes
>
> checking for shmat... yes
>
> checking for sys/types.h... (cached) yes
>
> checking for stdint.h... (cached) yes
>
> checking sys/bitypes.h usability... yes
>
> checking sys/bitypes.h presence... yes
>
> checking for sys/bitypes.h... yes
>
> checking for poll in -lpoll... no
>
> checking Carbon/Carbon.h usability... no
>
> checking Carbon/Carbon.h presence... no
>
> checking for Carbon/Carbon.h... no
>
> checking CoreAudio/CoreAudio.h usability... no
>
> checking CoreAudio/CoreAudio.h presence... no
>
> checking for CoreAudio/CoreAudio.h... no
>
> checking if res_init needs -lresolv... yes
>
> checking for res_init... yes
>
> checking if res_init needs custom prototype... no
>
> checking for killpg in -lucb... no
>
> checking for int... yes
>
> checking size of int... 4
>
> checking for short... yes
>
> checking size of short... 2
>
> checking for long... yes
>
> checking size of long... 4
>
> checking for char *... yes
>
> checking size of char *... 4
>
> checking for dlopen in -ldl... (cached) yes
>
> checking for shl_unload in -ldld... no
>
> checking for size_t... yes
>
> checking size of size_t... 4
>
> checking for unsigned long... yes
>
> checking size of unsigned long... 4
>
> checking sizeof size_t == sizeof unsigned long... yes
>
> checking for PIE support... yes
>
> checking if enabling -pie/fPIE support... yes
>
> checking crt_externs.h usability... no
>
> checking crt_externs.h presence... no
>
> checking for crt_externs.h... no
>
> checking for _NSGetEnviron... no
>
> checking for vsnprintf... yes
>
> checking for snprintf... yes
>
> checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
>
> checking for IceConnectionNumber in -lICE... yes
>
> checking for libXext... yes
>
> checking for pthread_create in -lpthread... yes
>
> checking for extra includes... no
>
> checking for extra libs... no
>
> checking for libz... -lz
>
> checking for libpng... -lpng -lz -lm
>
> checking for libjpeg6b... no
>
> checking for libjpeg... -ljpeg
>
> checking for perl... /usr/bin/perl
>
> checking for Qt... configure: error: Qt (>= Qt 3.2 and < 4.0) (headers
> and libraries) not found. Please check your installation!
>
> For more details about this problem, look at the end of config.log.

[Kdiff3-user] Newbie - installation trouble, help required.

[Vinodh R. (vrajaram) <vra...@ci...>]

Hi 

 

I am trying to install kdiff3 on my linux server, for the first time.
Ran into install issue, hope someone can point out my mistakes. Please
let me know if information provided below is insufficient. 

 

blr-mcp-bld-02-62> uname -a

Linux blr-mcp-bld-02 2.6.9-42.7.ELsmp #1 SMP Tue Sep 5 18:29:39 EDT 2006
i686 i686 i386 GNU/Linux

 

Qt version 3.3 is available here at, I have set QTDIR as below.

 

blr-mcp-bld-02-63> env | grep QTD

10:QTDIR=/usr/lib/qt-3.3

blr-mcp-bld-02-64> cd /usr/lib/qt-3.3/

blr-mcp-bld-02-65> ls

bin  etc  lib  plugins

blr-mcp-bld-02-66>

 

 

I copied the tar and executed the command as below. Installation fails
on checking for QT. 

 

blr-mcp-bld-02-60> pwd

/users/vrajaram/tmpsrc/kdif/kdiff3-0.9.92

blr-mcp-bld-02-61> ./configure --prefix=/usr

checking build system type... i686-pc-linux-gnu

checking host system type... i686-pc-linux-gnu

checking target system type... i686-pc-linux-gnu

checking for a BSD-compatible install... /usr/bin/install -c

checking for -p flag to install... yes

checking whether build environment is sane... yes

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking for kde-config... /usr/bin/kde-config

checking where to install... /usr (as requested)

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 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 whether gcc is blacklisted... no

checking whether g++ supports -Wmissing-format-attribute... yes

checking whether gcc supports -Wmissing-format-attribute... yes

checking whether g++ supports -Wundef... yes

checking whether g++ supports -Wno-long-long... yes

checking whether g++ supports -Wno-non-virtual-dtor... yes

checking whether g++ supports -fno-reorder-blocks... yes

checking whether g++ supports -fno-exceptions... yes

checking whether g++ supports -fno-check-new... yes

checking whether g++ supports -fno-common... yes

checking whether g++ supports -fexceptions... yes

checking whether system headers can cope with -O2 -fno-inline...
irrelevant

checking how to run the C++ preprocessor... g++ -E

checking whether g++ supports -O0... yes

checking whether g++ supports -Wl,--no-undefined... yes

checking whether g++ supports -Wl,--allow-shlib-undefined... yes

not using lib directory suffix

checking for a sed that does not truncate output... /bin/sed

checking for grep that handles long lines and -e... /router/bin/grep

checking for egrep... /router/bin/grep -E

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 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 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 static flag  works... yes

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 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 for shl_load... no

checking for shl_load in -ldld... no

checking for dlopen... no

checking for dlopen in -ldl... yes

checking whether a program can dlopen itself... yes

checking whether a statically linked program can dlopen itself... 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++ 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

checking whether stripping libraries is possible... yes

checking for shl_load... (cached) no

checking for shl_load in -ldld... (cached) no

checking for dlopen... (cached) no

checking for dlopen in -ldl... (cached) yes

checking whether a program can dlopen itself... (cached) yes

checking whether a statically linked program can dlopen itself...
(cached) yes

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 supports -c -o file.o... yes

checking whether the g77 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

checking whether stripping libraries is possible... yes

checking for msgfmt... /usr/bin/msgfmt

checking for gmsgfmt... /usr/bin/msgfmt

checking for xgettext... /usr/bin/xgettext

checking if C++ programs can be compiled... yes

checking for strlcat... no

checking if strlcat needs custom prototype... yes - in libkdefakes

checking for strlcpy... no

checking if strlcpy needs custom prototype... yes - in libkdefakes

checking for main in -lutil... yes

checking for main in -lcompat... no

checking for crypt in -lcrypt... yes

checking for socklen_t... yes

checking for dnet_ntoa in -ldnet... no

checking for dnet_ntoa in -ldnet_stub... no

checking for inet_ntoa... yes

checking for connect... yes

checking for remove... yes

checking for shmat... yes

checking for sys/types.h... (cached) yes

checking for stdint.h... (cached) yes

checking sys/bitypes.h usability... yes

checking sys/bitypes.h presence... yes

checking for sys/bitypes.h... yes

checking for poll in -lpoll... no

checking Carbon/Carbon.h usability... no

checking Carbon/Carbon.h presence... no

checking for Carbon/Carbon.h... no

checking CoreAudio/CoreAudio.h usability... no

checking CoreAudio/CoreAudio.h presence... no

checking for CoreAudio/CoreAudio.h... no

checking if res_init needs -lresolv... yes

checking for res_init... yes

checking if res_init needs custom prototype... no

checking for killpg in -lucb... no

checking for int... yes

checking size of int... 4

checking for short... yes

checking size of short... 2

checking for long... yes

checking size of long... 4

checking for char *... yes

checking size of char *... 4

checking for dlopen in -ldl... (cached) yes

checking for shl_unload in -ldld... no

checking for size_t... yes

checking size of size_t... 4

checking for unsigned long... yes

checking size of unsigned long... 4

checking sizeof size_t == sizeof unsigned long... yes

checking for PIE support... yes

checking if enabling -pie/fPIE support... yes

checking crt_externs.h usability... no

checking crt_externs.h presence... no

checking for crt_externs.h... no

checking for _NSGetEnviron... no

checking for vsnprintf... yes

checking for snprintf... yes

checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include

checking for IceConnectionNumber in -lICE... yes

checking for libXext... yes

checking for pthread_create in -lpthread... yes

checking for extra includes... no

checking for extra libs... no

checking for libz... -lz

checking for libpng... -lpng -lz -lm

checking for libjpeg6b... no

checking for libjpeg... -ljpeg

checking for perl... /usr/bin/perl

checking for Qt... configure: error: Qt (>= Qt 3.2 and < 4.0) (headers
and libraries) not found. Please check your installation!

For more details about this problem, look at the end of config.log.

 

Re: [Kdiff3-user] Problem Installing kdiff3 on Solaris 8

[Joachim E. <joa...@gm...>]

Hi Pankaj,

> The problem is related with QT. I have installed QT3 using a solaris
> package and that package doesn't have libqt-mt.so file. 
>...
> Is there a way a can compile it without this module file ?

KDiff3 heavily depends on Qt, so there is no way around that.

Seeing that you were able to compile, it means that Qt is installed.
Perhaps the lib has a different name.
Try "ls /usr/local/qt/lib" if there is a libqt*.so.
If not try 
find /usr -name "libqt*"

If you find something, then fix the Makefile in the src-subdir.
Replace "-lqt-mt" with the filename without the "lib" and ".so".

If there is no libqt-file at all then consider reinstalling Qt. (Compiling 
from source.)

Cheers,
Joachim

[Kdiff3-user] Problem Installing kdiff3 on Solaris 8

[Pankaj A. <pan...@ya...>]

 
Hi,
 
I am having problem in installing kdiff3 on solaris 8.
 
I am using it on my windows desktop with no issues.
 
The problem is related with QT. I have installed QT3 using a solaris package and that package doesn't have libqt-mt.so file.
 
I am getting the following error becuase of it.
 
g++  -o kdiff3 main.o  diff.o  difftextwindow.o  kdiff3.o  merger.o  mergeresultwindow.o  optiondialog.o  pdiff.o  directorymergewindow.o  fileaccess.o  smalldialogs.o  kdiff3_shell.o  kdiff3_part.o  gnudiff_analyze.o  gnudiff_io.o  gnudiff_xmalloc.o  common.o  kreplacements.o  ShellContextMenu.o moc_difftextwindow.o  moc_mergeresultwindow.o  moc_kdiff3.o  moc_optiondialog.o  moc_kreplacements.o  moc_directorymergewindow.o  moc_fileaccess.o  moc_kdiff3_shell.o  moc_kdiff3_part.o  moc_smalldialogs.o   -L/usr/lib/ -L/usr/local/qt/lib/ -L/usr/X11R6/lib/ -lqt-mt -lXext -lX11 -lm -lpthread
ld: fatal: library -lqt-mt: not found
ld: fatal: File processing errors. No output written to kdiff3
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target `kdiff3'
 
Is there a way a can compile it without this module file ?
 
Thanks,
 
Pankaj
 
 
 
 


      

[Kdiff3-user] Building kdiff3 in MacPorts on OS X 10.5 Leopard

[John J. B. <joh...@gm...>]

If anyone is having trouble doing this, here is the solution:

<http://blog.johnjosephbachir.org/2008/07/06/how-to-build-kdiff3-in-macports-on-os-x-105-leopard/>

Cheers,
John

--
John Joseph Bachir
http://blog.johnjosephbachir.org
http://lyceum.ibiblio.org
http://dissent.cc
http://jjb.cc

Re: [Kdiff3-user] strange consistent problem with Ubuntu AND OS X binaries

[John J. B. <joh...@gm...>]

Wow-- believe it or not, I didn't see before that the problem goes away if i
turn off word wrapping.

So, you have partially solved my problem for now. thanks!


On Sun, Jul 6, 2008 at 8:25 AM, Joachim Eibl <joa...@gm...> wrote:

> Hi John,
>
> This is a known problem I still have to fix.
> It is not Ubuntu-specific.
>
> If you have enabled word wrap then the output window won't wrap, but
> horizontal scrolling doesn't work anymore.
>
> Regards,
> Joachim
>
> Am Freitag 04 Juli 2008 02:24:42 schrieb John Joseph Bachir:
> > I have had the following problem using both the OS X binary that you
> > distribute, and the one that comes with Ubuntu 8.04:
> >
> > If a line in the output window goes beyond the current width of the
> > output window, I can't see it. I can't scroll the window horizontally,
> > and there is no option to wrap the lines in the output window.
> >
> > The horizontal scroll bar is "full"-- there is no scrolling space on
> > either side of it.
> >
> > It's particularly strange that this is happening with both of these
> > binaries. My friend is using the same Ubuntu binary on the same OS,
> > and NOT having the same problem. We are both using all of the default
> > configs.
> >
> > I am runing Ubuntu in a virtual machine on OS X.
> >
> > The only thing that is the same between both my OS X environment, and
> > my Ubuntu environment, is the screen resolution!
> >
> > In fact, I'm going to go try changing that now. I'll let you know if
> > it's effective.
> >
> > Thanks!
> > John
>
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Kdiff3-user mailing list
> Kdi...@li...
> https://lists.sourceforge.net/lists/listinfo/kdiff3-user
>



-- 
John Joseph Bachir
http://blog.johnjosephbachir.org
http://lyceum.ibiblio.org
http://dissent.cc
http://jjb.cc

Re: [Kdiff3-user] strange consistent problem with Ubuntu AND OS X binaries

[Joachim E. <joa...@gm...>]

Hi John,

This is a known problem I still have to fix.
It is not Ubuntu-specific.

If you have enabled word wrap then the output window won't wrap, but 
horizontal scrolling doesn't work anymore.

Regards,
Joachim

Am Freitag 04 Juli 2008 02:24:42 schrieb John Joseph Bachir:
> I have had the following problem using both the OS X binary that you
> distribute, and the one that comes with Ubuntu 8.04:
>
> If a line in the output window goes beyond the current width of the
> output window, I can't see it. I can't scroll the window horizontally,
> and there is no option to wrap the lines in the output window.
>
> The horizontal scroll bar is "full"-- there is no scrolling space on
> either side of it.
>
> It's particularly strange that this is happening with both of these
> binaries. My friend is using the same Ubuntu binary on the same OS,
> and NOT having the same problem. We are both using all of the default
> configs.
>
> I am runing Ubuntu in a virtual machine on OS X.
>
> The only thing that is the same between both my OS X environment, and
> my Ubuntu environment, is the screen resolution!
>
> In fact, I'm going to go try changing that now. I'll let you know if
> it's effective.
>
> Thanks!
> John

[Kdiff3-user] strange consistent problem with Ubuntu AND OS X binaries

[John J. B. <joh...@gm...>]

I have had the following problem using both the OS X binary that you
distribute, and the one that comes with Ubuntu 8.04:

If a line in the output window goes beyond the current width of the
output window, I can't see it. I can't scroll the window horizontally,
and there is no option to wrap the lines in the output window.

The horizontal scroll bar is "full"-- there is no scrolling space on
either side of it.

It's particularly strange that this is happening with both of these
binaries. My friend is using the same Ubuntu binary on the same OS,
and NOT having the same problem. We are both using all of the default
configs.

I am runing Ubuntu in a virtual machine on OS X.

The only thing that is the same between both my OS X environment, and
my Ubuntu environment, is the screen resolution!

In fact, I'm going to go try changing that now. I'll let you know if
it's effective.

Thanks!
John


-- 
John Joseph Bachir
http://blog.johnjosephbachir.org
http://lyceum.ibiblio.org
http://dissent.cc
http://jjb.cc

Re: [Kdiff3-user] Request for revision control smarts

[Ruslan Z. <ru...@be...>]

SVK has integrated support of KDiff3 and I use it during merges to
resolve conflicts. And it's really helpful, however it's actually
integration from another side. May be it's also a good thing to ask
subversion guys as well.

On Tue, Jan 29, 2008 at 1:39 AM, Scott Gable <gab...@gm...> wrote:
> This is a feature request for kdiff3.
>
> I wish that it had automatic revision control comprehension for subversion
> and other tools. For example with tkdiff if you have edited your local copy
> of foo.c you can simply review your changes by typing:
>    tkdiff foo.c
> Obviously if there is a conflict between your changes and an update to the
> repository you should be able to do a three way compare with the same
> command:
>   kdiff3 foo.c
>
> Thanks.
>
> -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
>  Kdiff3-user mailing list
>  Kdi...@li...
>  https://lists.sourceforge.net/lists/listinfo/kdiff3-user
>
>



-- 
Best regards, Ruslan.

[Kdiff3-user] Some Wikipedia links, OT: best text-based diff tool

[markus8 <ma...@us...>]

Hi All,

just for completeness (first one already sent by WYSOCKI Jean-Eric
<jean-eric.wysocki@eu...>):

  http://en.wikipedia.org/wiki/Comparison_of_file_comparison_tools

and some overviews of comparison and other software tools:

  http://en.wikipedia.org/wiki/Category:File_comparison_tools
  http://en.wikipedia.org/wiki/Category:Free_file_comparison_tools

  http://en.wikipedia.org/wiki/Category:Software_comparisons.

 best regards, markus

Re: [Kdiff3-user] [LIKELY_SPAM] Re: Problem with menu highlighting on Red Hat Linux

[Skilleter, J. <joh...@ec...>]

Hi Joachim,

Thanks for the idea - I looked at the theme settings on my setup (Red
Hat & KDE 3) and found the problem occurs with the theme I was using
(Bluecurve) but not others, so I've switched themes and I'm happy again.

Regards

John=20

-----Original Message-----
From: kdi...@li...
[mailto:kdi...@li...] On Behalf Of Joachim
Eibl
Sent: 29 January 2008 20:22
To: kdi...@li...
Subject: [LIKELY_SPAM] Re: [Kdiff3-user] Problem with menu highlighting
on Red Hat Linux

Hi

Since nobody else wrote, I just want to recommend experimenting with
your themes.

On my system (KDE, Opensuse) everything looks fine.

Perhaps you want to send a screenshot, so I can get a better idea.

Joachim



Am Dienstag 08 Januar 2008 16:03:29 schrieb Skilleter, John:
> I've come across an annoying problem with kdiff3 on Red Hat Linux; A=20
> number of the menu items in the GUI which turn options on or off do=20
> not indicate the current state of the option correctly. This seems to=20
> apply to all on/off menu entries which have icons on the left hand=20
> side of the menu. Those without icons show a tick when the option is=20
> turned on or nothing when it is turned off. Those without icons do not

> change appearance.
>
> On kdiff3 on Windows the behaviour is subtly different in that options

> which are enabled are highlighted with a paler background under the=20
> icon or the tick, but this isn't happening under Linux and it is all=20
> too easy to run a diff, not realise that the 'Show files only in A' or

> 'Show files only in B' options are turned on because there's nothing=20
> to indicate it in the menu and miss something of vital importance!
>
> I've tried it on a couple of PC's, one with KDE and one with Gnome=20
> (both running the same Red Hat) and got the same result - Anyone=20
> happen to have any idea whether this a bug/limitation of the software,

> or our particular Linux setup?
>
> Thanks
>
> John Skilleter



------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Kdiff3-user mailing list
Kdi...@li...
https://lists.sourceforge.net/lists/listinfo/kdiff3-user

[Kdiff3-user] Paul K Scrutton is out of the office.

[Paul K S. <pks...@us...>]

I will be out of the office starting  01/25/2008 and will not return until
02/04/2008.

I will not have my work laptop with me during that time.
Please contact my manager Cindy Walter for urgent requests during this
time.

Re: [Kdiff3-user] Request for revision control smarts

[Joachim E. <joa...@gm...>]

Hi Scott,

> I wish that it had automatic revision control comprehension for subversion
> and other tools. For example with tkdiff if you have edited your local copy
> of foo.c you can simply review your changes by typing:
>   tkdiff foo.c

Perhaps some script might be helpful too. See here:
http://sourceforge.net/tracker/index.php?func=detail&aid=977230&group_id=58666&atid=488550

> Obviously if there is a conflict between your changes and an update to the
> repository you should be able to do a three way compare with the same
> command:

Currently I wouldn't know how to implement this. Can you give details on how 
to find what the base would be?

Joachim

Re: [Kdiff3-user] Problem with menu highlighting on Red Hat Linux

[Joachim E. <joa...@gm...>]

Hi

Since nobody else wrote, I just want to recommend experimenting with your 
themes.

On my system (KDE, Opensuse) everything looks fine.

Perhaps you want to send a screenshot, so I can get a better idea.

Joachim



Am Dienstag 08 Januar 2008 16:03:29 schrieb Skilleter, John:
> I've come across an annoying problem with kdiff3 on Red Hat Linux; A
> number of the menu items in the GUI which turn options on or off do not
> indicate the current state of the option correctly. This seems to apply
> to all on/off menu entries which have icons on the left hand side of the
> menu. Those without icons show a tick when the option is turned on or
> nothing when it is turned off. Those without icons do not change
> appearance.
>
> On kdiff3 on Windows the behaviour is subtly different in that options
> which are enabled are highlighted with a paler background under the icon
> or the tick, but this isn't happening under Linux and it is all too easy
> to run a diff, not realise that the 'Show files only in A' or 'Show
> files only in B' options are turned on because there's nothing to
> indicate it in the menu and miss something of vital importance!
>
> I've tried it on a couple of PC's, one with KDE and one with Gnome (both
> running the same Red Hat) and got the same result - Anyone happen to
> have any idea whether this a bug/limitation of the software, or our
> particular Linux setup?
>
> Thanks
>
> John Skilleter

[Kdiff3-user] Request for revision control smarts

[Scott G. <gab...@gm...>]

This is a feature request for kdiff3.

I wish that it had automatic revision control comprehension for subversion
and other tools. For example with tkdiff if you have edited your local copy
of foo.c you can simply review your changes by typing:
  tkdiff foo.c
Obviously if there is a conflict between your changes and an update to the
repository you should be able to do a three way compare with the same
command:
  kdiff3 foo.c

Thanks.