public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Petr.Salinger at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/50532] New: [patch] libffi needs FFI_MMAP_EXEC_WRIT on kfreebsd-amd64
Date: Tue, 27 Sep 2011 11:56:00 -0000	[thread overview]
Message-ID: <bug-50532-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50532

             Bug #: 50532
           Summary: [patch] libffi needs FFI_MMAP_EXEC_WRIT on
                    kfreebsd-amd64
    Classification: Unclassified
           Product: gcc
           Version: 4.6.1
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P3
         Component: libffi
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: Petr.Salinger@seznam.cz


libffi crashes under kfreebsd-amd64 in trampoline. 
As the GNU/kFreeBSD uses the same kernel as plain FreeBSD, it suffices 

--- src/libffi/configure.ac
+++ src/libffi/configure.ac
@@ -313,7 +313,7 @@
 fi

 case "$target" in
-     *-apple-darwin10* | *-*-freebsd* | *-*-openbsd* | *-pc-solaris*)
+     *-apple-darwin10* | *-*-freebsd* | *-*-kfreebsd* | *-*-openbsd* |
*-pc-solaris*)
        AC_DEFINE(FFI_MMAP_EXEC_WRIT, 1,
                  [Cannot use malloc on this target, so, we revert to
                    alternative means])

See also original Debian bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642928

Many thanks

        Petr


             reply	other threads:[~2011-09-27 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 11:56 Petr.Salinger at seznam dot cz [this message]
2011-09-27 12:12 ` [Bug libffi/50532] " Petr.Salinger at seznam dot cz
2021-09-15  9:03 ` pinskia at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-50532-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).