Игорь Пашев <pashev.i...@gmail.com> writes: | Thanks, Gabriel. | | Ok, I will ask Konstantinos again for build logs :-) | And if he is correct, I think I will use a patch specially for Debian.
it would still be better is such patch is in upstream so that you don't have to maintain it separately. Let me know if he is willing to test a patch. -- Gaby | | 2012/9/15 Gabriel Dos Reis <g...@integrable-solutions.net>: | > On Sat, Sep 15, 2012 at 6:09 AM, Игорь Пашев <pashev.i...@gmail.com> wrote: | >> Here is a Debian bug: | >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687608 | >> | >> <<on most other platforms, -m32/-m64 are not available as compiler | >> flags. So configure fails.>> | >> | >> I think it is safe to remove those flags. As for Debian and Gentoo | >> lisps are compiled with default compiler, so it is safe to use default | >> compiler for OA. In difficult cases user (packager) can set CC of CFLAGS | >> for configure: | >> | >> ./configure CC='gcc -m32' | > | > Hi Igor, | > | > thanks for forwarding the report. | > | > Unfortunately, Konstantinos is not right in his statement. | > I don't know how he measured "on most other platforms", | > but the flags is necessary for the following reasons: there | > are many important platforms (for OpenAxiom) that are bi-arch, e.g. | > can run both 32-bit and 64-bit programs. Solaris, and earlier versions of | > Mac OS X, Windows 7 on 64-bit archi, and certain linux distros come to mind. | > On these systems the available Lisp system may be built with | > a certain CPU precision that is not the default of the C++ compiler. | > For example, on Windows 7 (and Mac OS X notably), the Lisp system | > may be built as a 32-bit application (think SBCL), whereas the C++ compiler | > defaults to 64-bit; or the Lisp system may be built as 64-bit application | > (think CCL) whereas the C++ compiler defaults to 32-bit. Since we link | > part of the C++ libraries into the Lisp image, we do need to have both | > components built with the same CPU precision. | > | > Consequently, we can't just drop the -m flags. | > | > What might makes sense to do is to test at configure time whether | > the available compiler understands the flags. Unfortunately, I do not | > have access to the machine that is causing trouble for Konstantinos. | > Is he or you willing to test a patch and report? | > | > -- Gaby | | ------------------------------------------------------------------------------ | How fast is your code? | 3 out of 4 devs don\\\'t know how their code performs in production. | Find out how slow your code is with AppDynamics Lite. | http://ad.doubleclick.net/clk;262219672;13503038;z? | http://info.appdynamics.com/FreeJavaPerformanceDownload.html | _______________________________________________ | open-axiom-devel mailing list | open-axiom-devel@lists.sourceforge.net | https://lists.sourceforge.net/lists/listinfo/open-axiom-devel ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ open-axiom-devel mailing list open-axiom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
