Greetings, and thanks for the patch. I think the -fno-stack-protector is dependent on the security model of the running kernel. True? Perhaps you can describe the conditions under which this is required. If this is a runtime instead of compile time issue, i.e. like the disabling of sbrk randomization we must check for on every startup, then I think this should be handled differently to preserve the ability to move images across different systems. The rest is all good -- thanks so much!, and will go in asap.
Take care, Blake McBride <[email protected]> writes: > Greetings, > > The following changes were necessary to get GCL to build on the above > mentioned machine. The first error is new for me. The second one has > been an issue for years. After these changes everything built and ran > fine. > > 1. Fix configuration failure due to unexpected path for ld: > > --- configure~ 2011-07-05 14:09:46.000000000 -0500 > +++ configure 2011-07-05 15:53:05.553382999 -0500 > @@ -8120,7 +8120,7 @@ > heap_ceiling=0x0 > else > if test -d /proc/self ; then > - heap_ceiling=0x`/bin/cat /proc/self/maps | grep "/lib/ld" | cut > -f1 -d- | head -1` > + heap_ceiling=0x`/bin/cat /proc/self/maps | grep "/lib.*/ld" | cut > -f1 -d- | head -1` > else > #echo -e "#include <stdio.h>\n int main() {printf(\"foo\");return 0;}" >foo.c > #$CC foo.c -o foo > > > 2. After running configure modify makedefs as follows: (This has > been a problem for years.) > > --- makedefs~ 2011-07-05 15:54:41.401036915 -0500 > +++ makedefs 2011-07-05 15:57:59.727036589 -0500 > @@ -46,9 +46,9 @@ > > NOTIFY=yes > CC=gcc > -CFLAGS= -fsigned-char -pipe -Wall -O3 -fomit-frame-pointer -I$(GCLDIR)/o > -FINAL_CFLAGS= -fsigned-char -pipe -Wall > -NIFLAGS= -fsigned-char -pipe -Wall -I$(GCLDIR)/o > +CFLAGS= -fsigned-char -pipe -Wall -O3 -fomit-frame-pointer > -I$(GCLDIR)/o -fno-stack-protector > +FINAL_CFLAGS= -fsigned-char -pipe -Wall -fno-stack-protector > +NIFLAGS= -fsigned-char -pipe -Wall -I$(GCLDIR)/o -fno-stack-protector > O3FLAGS=-Os -fomit-frame-pointer > O2FLAGS=-O > > > 3. "make install" will fail and no gcl will be built if pdflatex is > not installed on the machine performing the build. If pdflatex is not > present it should just skip the docs. > > Thanks. > > Blake McBride > > _______________________________________________ > Gcl-devel mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gcl-devel > > > > -- 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
