public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: cygport cross compilation
Date: Wed, 19 Mar 2014 18:05:00 -0000	[thread overview]
Message-ID: <5329DC45.7070806@users.sourceforge.net> (raw)
In-Reply-To: <5329C6AE.7080803@cornell.edu>

On 2014-03-19 11:32, Ken Brown wrote:
> I've just started experimenting with using cygport for cross compiling,
> and I've come across two issues:
>
> 1. This is just a request: The latest cygport for Fedora appends i686 or
> x86_64 to the name of the working directory.  I would find it convenient
> if cygport did the same thing on Cygwin, at least if the --32 or --64
> option is specified.

Actually, that is experimental code (based on a request from another 
cygport user) that was accidentally shipped when I had to reroll the 
source tarball for compatibility with F20/UnversionedDocDirs.  Would 
people like to see this done always, never, or only when cross-building?

> 2. I tried to do a build for x86-cygwin on x86_64-cygwin, but the
> compiler didn't work:
>
> $ cat test.c
> int
> main ()
> {
>    return 0;
> }
>
> $ i686-pc-cygwin-gcc test.c
> /tmp/ccaAaoj6.s: Assembler messages:
> /tmp/ccaAaoj6.s:9: Error: invalid instruction suffix for `push'

WFM.  Are you missing cygwin32-binutils?


Yaakov

  reply	other threads:[~2014-03-19 18:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 16:32 Ken Brown
2014-03-19 18:05 ` Yaakov (Cygwin/X) [this message]
2014-03-19 18:28   ` Corinna Vinschen
2014-03-19 18:39     ` Ken Brown
2014-03-19 18:50   ` Ken Brown
2014-03-27 18:50   ` [RFC] cygport: arch-specific workdir (was: cygport cross compilation) Yaakov (Cygwin/X)
2014-03-27 20:01     ` [RFC] cygport: arch-specific workdir Achim Gratz
2014-03-27 21:02       ` Ken Brown
2014-03-27 23:47     ` David Stacey
2014-03-28 17:20     ` David Rothenberger
2014-04-27 20:22     ` Yaakov (Cygwin/X)
2014-05-04 16:41       ` Achim Gratz

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=5329DC45.7070806@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --cc=cygwin-apps@cygwin.com \
    /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).