public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vityan at vityan dot sytes.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/47164] New: libffi fails to build for alternate target in multilib configuration
Date: Tue, 04 Jan 2011 05:31:00 -0000	[thread overview]
Message-ID: <bug-47164-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: libffi fails to build for alternate target in multilib
                    configuration
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libffi
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: vityan@vityan.sytes.net
              Host: i686-w64-mingw32
            Target: i686-w64-mingw32,x86_64-w64-mingw32
             Build: i686-pc-mingw32(msys)


Created attachment 22894
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22894
libffi multilib support fix for MingW64

Then multilib is enabled for toolchain(--enable-multilib) libffi fails to build
for alternative(secondary) target.
The issue caused by libffi's configury system only handling the main
host/target without any respect to multilib.

For x86_64-w64-mingw32 i've forced to manually import files from libffi
3.0.10-cvs into libffi/src/x86/ from GCC tree but this is out of scope of
current issue.

This issue is global for many targets.
I've made a patch fixing this issue for i686-*-mingw32,x86_64-*-mingw32 targets
with multilib configuration.


                 reply	other threads:[~2011-01-04  5:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-47164-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).