Greetings! I forgot to mention that if you do end up working with a binary compiled with a gcc that supports different switches, you can always set the switches back to whatever you'd like:
>(setq compiler:*cc* "gcc -c -g -Wall -fsigned-char >-Wno-unused-but-set-variable -pipe -g ") >(setq compiler::*opt-three* "-O2") >(si::save-system "my-gcl") Take care, Camm Maguire <[email protected]> writes: > Greetings, and thanks so much for trying out the (soon to be released) > 2.6.12pre currently in Debian sid. > > Debian policy specifies default gcc compiler flags to offer some degree > of security protection in shipped binaries. These include the stack > protector flags, which are only supported in more recent versions of gcc > (e.g. the one in the Debian sid distribution), and which attempt to > detect and prevent certain stack overflow attacks. (It was actually > tricky to get GCL, prelink, unexec, and these flags to play well > together :-)). > > So in sum, I don't have much choice regarding the gcl shipped in Debian, > but of course users building from source can use whatever gcc and flags > they desire. These extra protections do not noticeably impact > performance. There should, BTW, be a slight performance gain in > 2.6.12pre over 2.6.11 on the maxima testsuite. > > Take care, > > Volker van Nek <[email protected]> writes: > >> Am 03.10.2014 um 05:08 schrieb Raymond Toy: >>>>>>>> "Volker" == Volker van Nek <[email protected]> writes: >>> >>> Volker> Hi Camm, >>> Volker> this afternoon I installed Maxima 5.34.1 with GCL 2.6.12 >>> packaged from >>> Volker> debian sid at work on a 32 bit machine and now at home I did >>> the same on >>> Volker> 64 bit. In both cases I observed a problem when compiling. >>> >>> Volker> Thanks for any hints. >>> >>> Seems like whoever built gcl used a different version of the compiler >>> that what you have on your system. >> >> If I remember right I had the same problem when compiling Maxima with a >> packaged GCL 2.6.11 from debian sid. The same error. >> gcc: error: unrecognized command line option ‘-fstack-protector-strong’ >> >> And then I also built GCL from sources. >> >> It seems that this compiler option - compiler version? - breaks the >> debian GCL builds (at least for some users). >> >> Volker >> >>> >>> FWIW, I built gcl from sources on an Ubuntu system. Compiles and runs >>> maxima just fine. >>> >>> Ray >>> >>> >>> ------------------------------------------------------------------------------ >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Maxima-discuss mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/maxima-discuss >>> >> >> >> ------------------------------------------------------------------------------ >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >> _______________________________________________ >> Maxima-discuss mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/maxima-discuss >> >> >> >> -- Camm Maguire [email protected] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gcl-devel
