#440 Core dump in FreeBSD-CURRENT/i386 during build

build problems
closed-works-for-me
clisp (525)
6
2008-07-17
2008-01-11
No

Hello.

I'm the FreeBSD port maintainer of clisp, and it core dumps in FreeBSD-CURRENT/i386 (in amd64 built fine), even with "--disable-mmap" (which is the option used in amd64).

Previously the 2.41 version was failing in FreeBSD 7 (to be released soon) because of GCC 4.2, and using 3.4 worked fine. After the 2.43 update, it built fine with GCC 4.2, so I don't think that's the problem (also it builds on amd64).

A user sent me a backtrace, build log and system information. They are attached. Any help will be appreciated.

Thanks and Best Regards,
Ale

Discussion

  • Alejandro Pulver

    GDB backtrace

     
  • Alejandro Pulver

    Build log and system information

     
    Attachments
  • Alejandro Pulver

    Logged In: YES
    user_id=1757602
    Originator: YES

    File Added: typescript

     
  • Sam Steingold

    Sam Steingold - 2008-01-11

    Logged In: YES
    user_id=5735
    Originator: NO

    please try
    ./configure --with-debug CFLAGS="" --build build-g

    if it works, I suspect that this bug is related to
    https://sourceforge.net/tracker/index.php?func=detail&aid=1836142&group_id=1355&atid=101355

    ps. it would be nice if you could get rid of "--disable-mmap" on amd64. linux does not need, and bsd should not need it either.

     
  • Alejandro Pulver

    Logged In: YES
    user_id=1757602
    Originator: YES

    I've tried building as you said, and it built but a configure test failed later. The log is attached.

    Also, the amd64 with mmap log is attached (fails to allocate memory).
    File Added: clisp-2.43.log.bz2

     
  • Alejandro Pulver

    Build log with debug enabled

     
    Attachments
  • Alejandro Pulver

    amd64 log with mmap enabled

     
    Attachments
  • Alejandro Pulver

    Logged In: YES
    user_id=1757602
    Originator: YES

    File Added: clisp-2.43.log.bz2

     
  • Bruno Haible

    Bruno Haible - 2008-02-24
    • milestone: 100334 --> build problems
    • priority: 5 --> 6
     
  • Bruno Haible

    Bruno Haible - 2008-02-24

    Logged In: YES
    user_id=5923
    Originator: NO

    Your assumption that clisp 2.43 builds fine with GCC 4.2 is unfortunately wrong.
    Please try clisp 2.43.1 instead, at
    http://www.haible.de/bruno/clisp/clisp-2.43.1.tar.gz
    How is the build going with this version?

     
  • Alejandro Pulver

    Logged In: YES
    user_id=1757602
    Originator: YES

    The port is currently at version 2.44, should it work with GCC 4.x (see below)?

    The strange thing is that it builds with GCC 4.2 on FreeBSD/amd64, but not i386. See the following (FreeBSD < 7 has GCC 3.4 and >= 8 has GCC 4.2; note that it builds fine on FreeBSD/i386 >= 7 because it uses GCC 3.4 from the ports collection, not base system, but that's not required for amd64):

    http://portsmon.freebsd.org/portoverview.py?category=lang&portname=clisp&wildcard=

     
  • Sam Steingold

    Sam Steingold - 2008-07-10

    Logged In: YES
    user_id=5735
    Originator: NO

    any news?
    did you try the recently released 2.46? (not that it requires a separate ffcall install)

     
  • Alejandro Pulver

    Logged In: YES
    user_id=1757602
    Originator: YES

    Version 2.44 works on FreeBSD amd64 and i386, versions 6, 7 and 8. I don't know about the other platforms.

    I'll update it soon to 2.46, but I guess this bug report can be closed.

     
  • Sam Steingold

    Sam Steingold - 2008-07-17
    • status: open --> closed-works-for-me
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks