Re: [EMAIL PROTECTED]: lyx-1.5.3 failed on i386 5]
Hello! We are getting failure reports from the automated builds of LyX-1.5.3 on some branches of FreeBSD. The most recent failure is logged here: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.5.2007123019/lyx-1.5.3.log it ends with: c++ -DHAVE_CONFIG_H -I. -I../../../src -DQT_CLEAN_NAMESPACE -DQT_GENUINE_STR -DQT_NO_STL -DQT_NO_KEYWORDS -Winvalid-pch --include=./pch.h -I../../../src -I../../../src/frontends -I../../../images -DQT_SHARED -I/usr/local/include/QtCore -I/usr/local/include/QtGui -I/usr/local/include -I../../../src/frontends/controllers -I/usr/local/include -O -pipe -MT GuiApplication.lo -MD -MP -MF .deps/GuiApplication.Tpo -c GuiApplication.cpp -o GuiApplication.o GuiApplication.cpp: In member function `void lyx::frontend::GuiApplication::commitData(QSessionManager&)': GuiApplication.cpp:350: error: invalid use of undefined type `struct QSessionManager' /usr/local/include/QtGui/qapplication.h:63: error: forward declaration of `struct QSessionManager' GuiApplication.cpp:351: error: invalid use of undefined type `struct QSessionManager' /usr/local/include/QtGui/qapplication.h:63: error: forward declaration of `struct QSessionManager' gmake[7]: *** [GuiApplication.lo] Error 1 gmake[7]: Leaving directory `/work/a/ports/print/lyx15/work/lyx-1.5.3/src/frontends/qt4' gmake[6]: *** [all-recursive] Error 1 I can not reproduce this problem on my own system, but I have both Qt3 and Qt4 installed, as well as a number of other packages, wherease the automated build happens in a "pristine" environment, which only has the explicitly-declared dependencies preinstalled: EXTRACT_DEPENDS=perl-5.8.8_1.tbz BUILD_DEPENDS=aiksaurus-1.2.1_2.tbz amspsfnt-1.0_5.tbz aspell-0.60.5_2.tbz boost-1.34.1.tbz cm-super-0.3.3_1.tbz cmpsfont-1.0_6.tbz compositeproto-0.4.tbz damageproto-1.1.0_2.tbz dvipsk-tetex-5.95a_2.tbz expat-2.0.0_1.tbz fixesproto-4.0.tbz fontcacheproto-0.1.2.tbz fontconfig-2.4.2_2,1.tbz fontsproto-2.0.2.tbz freetype2-2.3.5.tbz gd-2.0.35,1.tbz gettext-0.16.1_3.tbz ghostscript-gpl-8.60.tbz glib-2.14.4.tbz gmake-3.81_2.tbz gsfonts-8.11_4.tbz inputproto-1.4.2.1.tbz jpeg-6b_4.tbz kbproto-1.0.3.tbz libFS-1.0.0.tbz libICE-1.0.4,1.tbz libSM-1.0.3,1.tbz libX11-1.1.3,1.tbz libXScrnSaver-1.1.2.tbz libXTrap-1.0.0.tbz libXau-1.0.3_2.tbz libXaw-1.0.4,1.tbz libXcomposite-0.4.0,1.tbz libXcursor-1.1.9.tbz libXdamage-1.1.1.tbz libXdmcp-1.0.2.tbz libXevie-1.0.2.tbz libXext-1.0.3,1.tbz libXfixes-4.0.3.tbz libXfont-1.3.1_1,1.tbz libXfontcache-1.0.4.tbz libXft-2.1.12.tbz libXi-1.1.3,1.tbz libXinerama-1.0.2,1.tbz libXmu-1.0.3,1.tbz libXp-1.0.0,1.tbz libXpm-3.5.7.tbz libXprintAppUtil-1.0.1.tbz libXprintUtil-1.0.1.tbz libXrandr-1.2.2.tbz libXrender-0.9.4.tbz libXres-1.0.3_2.tbz libXt-1.0.5.tbz libXtst-1.0.3.tbz libXv-1.0.3,1.tbz libXvMC-1.0.4.tbz libXxf86dga-1.0.2.tbz libXxf86misc-1.0.1.tbz libXxf86vm-1.0.1.tbz libdmx-1.0.2.tbz libfontenc-1.0.4.tbz libiconv-1.11_1.tbz liboldX-1.0.1.tbz libwww-5.4.0_4.tbz libxkbfile-1.0.4.tbz libxkbui-1.0.2.tbz open-motif-2.2.3_5.tbz pcre-7.4.tbz perl-5.8.8_1.tbz pixman-0.9.6.tbz pkg-config-0.22_1.tbz png-1.2.23_1.tbz printproto-1.0.3.tbz python25-2.5.1_1.tbz qt4-corelib-4.3.1_1.tbz qt4-gui-4.3.1.tbz qt4-moc-4.3.1.tbz qt4-uic-4.3.1.tbz randrproto-1.2.1.tbz recordproto-1.13.2.tbz renderproto-0.9.3.tbz scrnsaverproto-1.1.0.tbz t1lib-5.1.1_2,1.tbz teTeX-3.0_2.tbz teTeX-base-3.0_12.tbz teTeX-texmf-3.0_5.tbz tex-texmflocal-1.9.tbz texi2html-1.76_1,1.tbz trapproto-3.4.3.tbz videoproto-2.2.2.tbz xbitmaps-1.0.1.tbz xdvik-tetex-22.84.10_1.tbz xextproto-7.0.2.tbz xf86dgaproto-2.0.3.tbz xf86miscproto-0.9.2.tbz xf86vidmodeproto-2.2.2.tbz xineramaproto-1.1.2.tbz xorg-libraries-7.3_1.tbz xproto-7.0.10_1.tbz xtrans-1.0.4.tbz -mi ## The information contained in this communication is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you are not a named addressee, please notify the sender immediately and delete this email from your system. If you have received this communication, and are not a named recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. ##
wish: parallel build
Hello! I tried to do a parallel build of lyx-1.4.5.1 with gmake -j4 but it failed due to some race condition. With more and more computers having multiple processors, it would be extremely useful to have all dependencies properly listed in the makefile so that make could perform such builds without tripping over... Thanks, -mi
Re: any known problems with gcc-4.2?
On понеділок 12 листопад 2007, Helge Hafting wrote: = Hard to say. I use gcc-4.2 to compile lyx-1.6svn on linux. = Lyx-1.6svn segfaults occationally, but that is expected for = development versions. = = If you want a stable LyX, consider 1.5.2 which is newer than 1.4.4 Thanks, we have a separate port of 1.5.2, which is believed to still be experimental (and it requires Qt4). I'll try to update the port of the stable 1.4 branch to 1.4.5.1 and see, if this resolves Dmitriy's problem. -mi
any known problems with gcc-4.2?
Hello! A user of FreeBSD-7.0-BETA2 has just reported a problem with lyx seg-faulting at start-up: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/117963 (the crash is inside calloc() suggesting a memory corruption). It seems to work for me here, on FreeBSD-6.2. The most pronounced difference between the OS-releases is the version of the compiler tool-chain. On 7.x we use gcc-4.2 and on 6.x it is still 3.4.6. Were there any known problems with lyx-1.4.4 and gcc-4.2 or do I need to dig deeper into it? Thanks! -mi
Spellchecker for Russian documents
Whenever I try to spell-check a document in Russian, I get an error message: Error: Spellchecker error The spellchecker could not be started No word lists can be found for the language "ru_RU". Dialog "spellchecker" failed to translate the data string passed to show() I have aspell installed -- along with the Russian dictionary. I suspect, language should be "ru", rather than "ru_RU" -- the files, which get added by the Russian dictionary for aspell are: /opt/lib/aspell-0.60/ru.dat /opt/lib/aspell-0.60/ru_affix.dat /opt/share/aspell/ru-ye.multi /opt/share/aspell/ru-ye.rws /opt/share/aspell/ru-yeyo.multi /opt/share/aspell/ru-yo.multi /opt/share/aspell/ru-yo.rws /opt/share/aspell/ru.multi Quite possibly, using "ru" instead of "ru_RU" would also fix an error message, that always greets me, when I start lyx: Locale ru_RU could not be set Thanks! -mi
When an image-converter is missing...
Hello! I have document with about 50 sections, each of which begins with a JPG-picture for its first letter. I had the misfortune of trying to obtain a DVI preview without ImageMagick installed... LyX's scripts/convertDefault.py tries to use ImageMagick's convert utility to convert images into EPS format suitable for DVI, etc. I had to click "Ok" 50 times (once for each embedded JPG)... The modal window appeared in addition to the repeated messages on stderr. Maybe, some logic should be put in place, to ensure, the same error is not shown more than once during the same operation. Or, maybe, all such errors should in some sort of a log somewhere -- viewable, but not requiring individual acknowledgement (in a modal window). Yours, -mi P.S. How do I configure the conversion to use GraphicsMagick instead? ``convert'' would be called ``gm convert'' in GraphicsMagick -- the arguments are identical.
Strange TOC problem going from 1.4.4 to 1.5.0rc2
Hello! I had a file with non-default settings for TOC/numbering. The Sections are marked to be non-numbered in it, but included in TOC. After loading the file in lyx-1.5.0rc2, and trying to preview it (as DVI), I noticed, that the TOC is completely empty. Two pages are marked as TOC (I use Fancy layout), but are otherwise blank. Going into the TOC settings, I found, that ALL elements (down to subparagraphs) were set to be included into the TOC... After lowering the "Include in TOC" bar, so that only nothing lower than Sections "Appears in TOC", I got the properly generated TOC in the DVI. -mi
1.4.x vs. 1.5.x roadmap (Re: LyX-1.4.4 fails to build against boost-1.34)
On п'ятниця 06 липень 2007, you wrote: = = > You may wish to release a 1.4.5 or 1.4.4.1. Even if 1.5.0 is _ready_, it = > has = > too many invasive changes (such as removal of many front-ends) to be = > immediately adopted... = = I plan to release LyX 1.4.5 about at the same time as 1.5.0 (because it will = contain code to read LyX 1.5.0 files). I'll look at your changes. Ok, I'll update the existing port to 1.4.5, when that appears. But do you intend to keep maintaining the two branches for a while? If so, I'll, probably, make a separate port of lyx15 -- for the adventerous. Otherwise, if there will be not 1.4.x releases beyond 1.4.5, I'll just skip the 1.5.0 and update the existing port to for 1.5.1 with all the new bugs ironed out :) Thanks! -mi
LyX-1.4.4 fails to build against boost-1.34
Hello!
Boost-1.34 is not only released now, it is also _required_ for the upcoming
LyX-1.5.0. Unfortunately, the current release of LyX (1.4.4) fails to build
against it.
I'm attaching the patch I plan to add to FreeBSD's print/lyx port to make the
source compatible with both Boost-1.33.1 and 1.34.
In addition, the `-fno-exceptions' has to be removed from configure, if
Boost-1.34 is detected.
You may wish to release a 1.4.5 or 1.4.4.1. Even if 1.5.0 is _ready_, it has
too many invasive changes (such as removal of many front-ends) to be
immediately adopted...
Thanks. Yours,
-mi
P.S. Boost people should really be ashamed of themselves for introducing API
incompatibilities like this -- especially, in a _minor_ number release...
--- src/support/path.h Mon Oct 6 11:43:21 2003
+++ src/support/path.h Fri Jul 6 14:23:38 2007
@@ -55,5 +55,5 @@
// we add this macro:
///
-#ifndef PATH_C
+#if 0
#define Path(x) unnamed_Path;
#endif
--- src/support/fs_extras.C Sat May 7 10:31:16 2005
+++ src/support/fs_extras.C Fri Jul 6 14:39:58 2007
@@ -94,11 +94,20 @@
#ifdef BOOST_POSIX
+#include
int const infile = ::open(source.string().c_str(), O_RDONLY);
if (infile == -1) {
boost::throw_exception(
+#if BOOST_VERSION < 103400
filesystem_error(
"boost::filesystem::copy_file",
source, target,
-fs::detail::system_error_code()));
+fs::detail::system_error_code())
+#else
+ filesystem_path_error(
+"boost::filesystem::copy_file",
+source, target,
+fs::lookup_errno(errno))
+#endif
+ );
}
@@ -108,8 +117,16 @@
::close(infile);
boost::throw_exception(
+#if BOOST_VERSION < 103400
filesystem_error(
"boost::filesystem::copy_file",
source, target,
-fs::detail::system_error_code()));
+fs::detail::system_error_code())
+#else
+ filesystem_path_error(
+"boost::filesystem::copy_file",
+source, target,
+fs::lookup_errno(errno))
+#endif
+ );
}
@@ -120,8 +137,16 @@
::close(infile);
boost::throw_exception(
+#if BOOST_VERSION < 103400
filesystem_error(
"boost::filesystem::copy_file",
source, target,
-fs::detail::system_error_code()));
+fs::detail::system_error_code())
+#else
+ filesystem_path_error(
+"boost::filesystem::copy_file",
+source, target,
+fs::lookup_errno(errno))
+#endif
+ );
}
@@ -150,8 +175,16 @@
if (in == -1 || out == -1)
boost::throw_exception(
+#if BOOST_VERSION < 103400
filesystem_error(
"boost::filesystem::copy_file",
source, target,
-fs::detail::system_error_code()));
+fs::detail::system_error_code())
+#else
+ filesystem_path_error(
+"boost::filesystem::copy_file",
+source, target,
+fs::lookup_errno(errno))
+#endif
+ );
#endif
#ifdef BOOST_WINDOWS
--- src/client/client.C Wed Apr 12 05:37:33 2006
+++ src/client/client.C Fri Jul 6 15:47:26 2007
@@ -94,5 +94,10 @@
for (; beg != end; ++beg) {
if (prefixIs(beg->leaf(), "lyx_tmpdir" + pid)) {
+#include
+#if BOOST_VERSION < 103400
fs::path lyxsocket = *beg / "lyxsocket";
+#else
+ fs::path lyxsocket = beg->path() / "lyxsocket";
+#endif
if (fs::exists(lyxsocket)) {
dirlist.push_back(lyxsocket);
Re: issues installing/running lyx-1.5.0rc2
On понеділок 02 липень 2007, Mikhail Teterin wrote: = 5. A large file, which I last saved with LyX-1.4.4, causes LyX-1.5.0 = to crash (SIGSEGV) right at the opening. This may be due to my using = JPEG images in the file (for the first letter of every chapter). I = suppose, this is a bug in the new image-caching feature :( = = Rebuilding with debugging now to, maybe, provide more information. After rebuilding with `-g' (and without -O2) the problem is gone :( Valgrind and/or Purify test is needed, but neither tool is available on my platform... Yours, -mi P.S. The file in question is in Russian (KOI8-R), which also may be the source of trouble -- in addition or instead of the image-caching.
issues installing/running lyx-1.5.0rc2
1. Transform name -- although I did not request *any* transformation through configure's arguments, both the executables and the manual pages got installed with the prefix ``amd64-portbld-freebsd6.2-''. I had add the explicit --program-transform-name="" to configure's arguments. This was not a problem with LyX-1.4.4 2. Parallel install -- this is broken, because multiple things race to check for and create the directories (under $PREFIX/share/lyx). Never tried with earlier versions of LyX. 3. Manual pages -- these get installed under PREFIX/share/man, which is wrong. If PREFIX is not /usr (and it should not be, because lyx is not part of the OS, although Linux folks don't seem to care for such things), the right place for man-pages is under PREFIX/man (no "share" in between). I now have to add an explicit --mandir flag to configure. This was not an issue with LyX-1.4.4. 4. The following two lines cause the new LyX to complain: LyX: Unknown tag `\popup_font_encoding' [around line 23 of file ~/.lyx/preferences] LyX: Unknown tag `\screen_font_encoding' [around line 25 of file ~/.lyx/preferences] 5. A large file, which I last saved with LyX-1.4.4, causes LyX-1.5.0 to crash (SIGSEGV) right at the opening. This may be due to my using JPEG images in the file (for the first letter of every chapter). I suppose, this is a bug in the new image-caching feature :( Rebuilding with debugging now to, maybe, provide more information. -mi
issues building LyX-1.5.0rc2 on FreeBSD
Hello! I maintain the port of LyX on FreeBSD and was checking, how the new version is built, so I can update the port quicker, when you make the final release of 1.5.0 (it is currently at 1.4.4). Here are the problems I had to work around: 1. Boost -- it seems, that some of the recent changes in LyX code require the most recent Boost-1.34 (lookup_errno, for example). Our devel/boost port is not yet updated to version 1.34, but that's coming soon (I had to use a patch released by the boost port's maintainer). This was not an issue with LyX-1.4.4, where our port was also ignoring the version of Boost bundled with LyX (I strongly oppose such bundling of 3rd-party software personally.). 2. -lc -- explicitly linking with libc is wrong, AFAIK, but the configure-generated Makefiles do this. This was an issue with earlier LyX versions as well. 3. Qt4 -- the abandonment of other front-ends (especially -- of Qt3) is a bit disruptive, because Qt3 (and gtk) are already found on most desktops as almost everyone uses either GNOME or KDE. Qt4 is "the wave of the future", so I'm not really complaining here. But, for a while Qt4 and Qt3 will often be found _on the same machine_. Currently, I have to patch LyX' src/frontends/qt4/Makefile to make sure, the -I/usr/local/include is _the last_ of the QT4_INCLUDES, _and_ insert the -I/usr/local/include/Qt at the beginning. Unfortunately, specifying the correct location with ``--with-qt4-includes'' does not have any effect. I never tried using Qt4 with earlier LyX versions. 4. Parallel builds. Specifying `-j4' to the top-level gmake breaks build. Adding the flag to AM_MAKEFLAGS (so that it is passed to all sub-makes) works. LyX takes a while to build, but more and more machines offer multiple CPU cores, so supporting parallel builds would be quite useful. Never tried it with previous LyX versions -- may not be a new problem. 5. tests -- when doing `gmake check' one of the three tests fails: PASS: test_convert FAIL: test_filetools PASS: test_lstrings 1 of 3 tests failed Please report to lyx-devel@lists.lyx.org Here are the differences between the output of filetools and the pre-recorded regfiles/filetools: ./bar/ ./bar/ ./foo/bar/ ./foo/bar/ ././bar/./bar/ ././foo/bar/./foo/bar/ /bar/ /bar/ /foo/bar/ /foo/bar/ ./foo/bar/ ./foo/bar/ ././foo/bar/./foo/bar/ /foo/bar/ /foo/bar/ Not sure, what the right fix is -- in my opinion, both are wrong :-) The normalized path should not include the leading "./" at all: "foo/bar/" should be the answer. Is the path-normalization performed by Boost?.. All tests were passing in LyX 1.4.4. I will now try to use the freshly-built 1.5.0rc2 (with post-build self-testing disabled). If I don't report anything, it must be all good :-) Thank you! Yours, -mi
Changes in the installed files from 1.4.1 to 1.4.2
Hello!
I'm about to update the FreeBSD port print/lyx from 1.4.1 to 1.4.2. I notice,
that the following files are no longer installed (relative to the ${PREFIX}):
share/lyx/configure
share/lyx/doc/LaTeXConfig.lyx
share/lyx/lyxrc.defaults
share/lyx/packages.lst
share/lyx/scripts/TeXFiles.sh
share/lyx/textclass.lst
and these new files are now added:
share/lyx/images/math/overset.xpm
share/lyx/images/math/underset.xpm
share/lyx/layouts/ijmpc.layout
share/lyx/configure.py
share/lyx/scripts/TeXFiles.py
share/lyx/scripts/clean_dvi.py
share/lyx/templates/ijmpc.lyx
Some of the additions are obvious replacements to the removed ones (like
configure), but I'm unsure about others. Could someone, please, confirm, that
I'm building/installing correctly? Thanks!
-mi
Re: new lyx port does not link -- gettext (-lintl is missing)
> >>>>> "Mikhail" == Mikhail Teterin <[EMAIL PROTECTED]> writes: > > Mikhail> It appears, the configure script does check for -lint, and > Mikhail> finding it installed on the system already rightfully chooses > Mikhail> not to use the included one. Unfortunately, it then does not > Mikhail> set the INTLLIB to anything, which means lyx_LDADD in > Mikhail> src/Makefile does not mention the -lintl at all and the > Mikhail> following linker error is seen. > > Mikhail> g++295 -O2 -fexpensive-optimizations -pipe -mcpu=i686 A > Mikhail> dirty fix is to add the -lintl to the lyx_LDADD line in > Mikhail> src/Makefile after configure. A clean fix is too complicated > Mikhail> I'm afraid of the configure.in/configure mess. > > Thanks for the report. It will be fixed in next release. A simple > workaround is to configure with --with-included-gettext. Yikes! If every app does that, only harddrive manufacturers will prosper. If you'd like my opinion, stop repackaging the ``included-gettext'' altogether, and simply insist on its presense -- just like xforms, ispell, etc. -mi
new lyx port does not link -- gettext (-lintl is missing)
>Submitter-Id: current-users >Originator: Mikhail Teterin >Organization: Virtual Estates, Inc. >Confidential: no >Synopsis: new lyx port does not link -- gettext (-lintl is missing) >Severity: critical >Priority: medium >Category: ports >Release:FreeBSD 3.4-STABLE i386 >Class: sw-bug >Environment: >Description: It appears, the configure script does check for -lint, and finding it installed on the system already rightfully chooses not to use the included one. Unfortunately, it then does not set the INTLLIB to anything, which means lyx_LDADD in src/Makefile does not mention the -lintl at all and the following linker error is seen. g++295 -O2 -fexpensive-optimizations -pipe -mcpu=i686 -march=i686 -L/usr/X11R6/lib -o lyx BufferView.o Bullet.o Chktex.o DepTable.o FontInfo.o FontLoader.o ImportLaTeX.o ImportNoweb.o LaTeX.o LaTeXFeatures.o LaTeXLog.o Literate.o LyXAction.o LyXSendto.o LyXView.o PaperLayout.o ParagraphExtra.o Spacing.o TableLayout.o bmtable.o buffer.o bufferlist.o bufferparams.o bullet_forms.o bullet_forms_cb.o chset.o combox.o credits.o credits_form.o debug.o filedlg.o form1.o intl.o kbmap.o lastfiles.o latexoptions.o layout.o layout_forms.o lyx.o lyx_cb.o lyx_gui.o lyx_gui_misc.o lyx_main.o lyx_sendfax.o lyx_sendfax_main.o lyx_sty.o lyxdraw.o lyxfont.o lyxfr0.o lyxfr1.o lyxfunc.o lyxlex.o lyxlookup.o lyxrc.o lyxserver.o lyxvc.o main.o menus.o minibuffer.o paragraph.o print_form.o screen.o sp_form.o spellchecker.o table.o tex-accent.o tex-strings.o texoptions.o texrow.o text.o text2.o toolbar.o trans.o trans_mgr.o undo.o vc-backend.o vspace.o mathed/.libs/libmathed.a insets/.libs/libinsets.a! support/.libs/libsupport.a -lxforms -lXpm -lSM -lICE -liberty -lc -lm -L/usr/X11R6/lib -lX11 BufferView.o: In function `BufferView::resizeCurrentBuffer(void)': BufferView.o(.text+0x96c): undefined reference to `gettext' BufferView.o: In function `BufferView::gotoError(void)': BufferView.o(.text+0xe5b): undefined reference to `gettext' BufferView.o(.text+0xef9): undefined reference to `gettext' Chktex.o: In function `Chktex::scanLogFile(TeXErrors &)': Chktex.o(.text+0x5b3): undefined reference to `gettext' FontLoader.o: In function `FontLoader::doLoad(LyXFont::FONT_FAMILY, LyXFont::FONT_SERIES, LyXFont::FONT_SHAPE, LyXFont::FONT_SIZE)': FontLoader.o(.text+0xad3): undefined reference to `gettext' LaTeX.o(.text+0x591): more undefined references to `gettext' follow main.o: In function `main': main.o(.text+0x98): undefined reference to `bindtextdomain' main.o(.text+0xa8): undefined reference to `textdomain' menus.o: In function `Menus::openByName(lyxstring const &)': menus.o(.text+0x292): undefined reference to `gettext' menus.o(.text+0x2c3): undefined reference to `gettext' menus.o(.text+0x2f4): undefined reference to `gettext' menus.o(.text+0x32c): undefined reference to `gettext' menus.o(.text+0x35d): undefined reference to `gettext' menus.o(.text+0x38e): more undefined references to `gettext' follow collect2: ld returned 1 exit status *** Error code 1 Stop. [...] >How-To-Repeat: >Fix: A dirty fix is to add the -lintl to the lyx_LDADD line in src/Makefile after configure. A clean fix is too complicated I'm afraid of the configure.in/configure mess.
