aMule Forum
English => Compilation problems => Topic started by: OldFrog on December 01, 2005, 07:46:24 PM
-
I compiled wxWidgets CVS of this morning with the --enable-largefile option, yet, when I compiled aMule CVS of this morning, I got this message :
checking for wxWidgets version >= 2.6.0... sed: -e expression #1, char 93: unknown option to `s'
sed: -e expression #1, char 93: unknown option to `s'
yes (version 2.7.0)
configure: WARNING: wxWidgets >=2.5.0: Using wx-config --libs net,base
sed: -e expression #1, char 93: unknown option to `s'
sed: -e expression #1, char 93: unknown option to `s'
checking that wxWidgets has support for large files... no
configure: error:
Support for large files in wxWidgets is required by aMule.
To continue you must recompile wxWidgets with support for
large files enabled.
-
Seems more like a bug in wx-checking, which then caused the large-file test to fail. Also, welcome from the future. ;)
Edit:
Could you try posting the output of running the wx-config file you used with the parameter "--cflags", and with the parameter "--cxxflags".
-
Using wxCVS from nov 1st, I get for both parms :
wx-config --cflags
-I/usr/lib/wx/include/gtk2-unicode-release-2.7 -I/usr/include/wx-2.7 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1
Using wxCVS from Dec 1st
wx-config --cxxflags
-I/usr/lib/wx/include/gtk2-unicode-release-2.7 -I/usr/include/wx-2.7 @WXCONFIG_CPPFLAGS@ @WXCONFIG_CXXFLAGS@
Hmm, these are RPMs I built myself, maybe looks like the better wxGTK.spec was too "better".
-
Yeah, I can fix the sed statement, but with those messed up flags, it's still going to fail.
-
Tried again with a simple ./configure --enable-unicode and make and make install, still the same punishment. Looks like there's something going wrong in the configuration script of wxWidgets for now. Ok, never mind, I can wait.
Back to wxGtk cvs from Nov 1st :rolleyes:
# RCS-ID: $Id: wx-config.in,v 1.128 2005/11/30 06:35:59 RL Exp
wx-config.in has changed, I guess there maybe a temporary mismatch with configure. Ok, I'll wait.
-
There is an ongoing discussion about CFLAGS on wx-dev, might be related.
-
Originally posted by Kry
There is an ongoing discussion about CFLAGS on wx-dev, might be related.
Thanks for concern. Actually, I'm too lazy now to follow all discussions on all software I'm playing with (Ahem, except aMule, of course :] :P )
-
Of course. Just giving a possible explanation.
I ahve to mention I use wx-cvs and it works perfectly here.
-
Usually I do too. But did you use wx-CVS since november 30th ? This is when the CFLAG and CXXFLAG configuration changed in wx-config.in.
[EDIT] Solved on CVS of 2005-12-02. May be me too. Don't ask ;( :rolleyes:
-
I use wx-cvs from every hour, give or take some minutes :P