Douglas R. Reno wrote:
On Sun, Aug 28, 2016 at 5:25 PM, Bruce Dubbs <[email protected]> wrote:

Paul Hentschel wrote:

I haven't been able to build this package. I keep getting the same error.

/bin/mkdir -p ../etc
:
test "no" = "yes" || \
    test "X" = X ||  -r temacs
test "no" = "yes" || test -z "setfattr" || \
    setfattr -n user.pax.flags -v er temacs
cd ../lisp; make -w update-subdirs
make[2]: Entering directory '/sources/extra/emacs-24.5/lisp'
for file in `find . -type d -print`; do case $file in .*/cedet* | .*/leim*
) ;; *) wins="$wins${wins:+ }$file" ;; esac; done; \
for file in $wins; do \
     ./../build-aux/update-subdirs $file; \
done;
make[2]: Leaving directory '/sources/extra/emacs-24.5/lisp'
if test "no" = "yes"; then \
    rm -f bootstrap-emacs; \
    ln temacs bootstrap-emacs; \
else \
    ./temacs --batch --load loadup bootstrap || exit 1; \
    test "X" = X ||  -zex emacs; \
    mv -f emacs bootstrap-emacs; \
fi
/bin/sh: line 7: 18100 Segmentation fault      (core dumped) ./temacs
--batch --load loadup bootstrap
make[1]: *** [Makefile:816: bootstrap-emacs] Error 1
make[1]: Leaving directory '/sources/extra/emacs-24.5/src'
make: *** [Makefile:387: src] Error 2

Anyone else have a problem building this package? Any ideas on what is
wrong?


I just tried a configure && make and got the same problem.  Probably
gcc6.  We'll have to investigate a fix.

Actually, it was Glibc-2.24's malloc implementation change:

https://sourceware.org/ml/libc-alpha/2016-07/msg00606.html

There's a fix in Emacs git somewhere to fix it. I haven't looked hard
enough to find it yet.

Yes. I was out for a while but ran gdb against temacs in a partial build. In a backtrace I got a ton (over 5000 lines) of messages like:

#135 0x00000000005c936a in calloc (nmemb=<error reading variable: DWARF-2 expression error: Loop detected (257).>, size=size@entry=1) at gmalloc.c:1529

We'll need to find a patch.

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to