public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Trouble with running cygwin dll on Vortex86MX+ CPU
Date: Fri, 04 Apr 2014 11:37:00 -0000	[thread overview]
Message-ID: <20140404113738.GF2508@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20140404T113717-470@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]

On Apr  4 09:44, Colin wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> 
> > > In discussing this with the embedded PC supplier, he suggests that the 
> > > cygwin1.dll is exiting because it doesn't recognise the CPU. Is this 
> > > explanation plausible? And if it is, is there a solution available, or 
> > > must I give up on using cygwin for this application?
> > 
> > As far as the pre-built Cygwin goes, I fear that you can't do a lot.
> > You could try to build Cygwin in i486 mode, and if that works, you have
> > to make sure to build applications against the newly built crt0.o and
> > libcygwin.a.  But that's not all to keep in mind.  When building
> > applications, parts of GCC are linked in as well, namely crtbegin.o and
> > crtend.o, and sometimes cyggcc_s-1.dll.  All these may or may not use
> > post-i486 opcodes, so if push comes to shove you'd end up having to
> > rebuild GCC for i486 as well.
> > 
> > I'm not trying to discourage you, but you might have a lot of
> > experimenting to do to get this working.
> > 
> > Corinna
> > 
> Thanks Corinna for this information. Now I understand the underlying issue 
> and can decide how to move forward. 
> 
> Given that my application is not so big, I suspect that the pragmatic 
> course will be to re-code it for Win32. 

Alternatively, even though I hate to point people to older versions
of Cygwin, you could try the old Cygwin 1.5.25.  I'm not quite sure,
but I think it was compiled for i586 or even i386.  It's not as
feature-rich as Cygwin 1.7 but it worked, and maybe the set of
POSIX functions is sufficient for you.  See the Cygwin time machine
at http://www.fruitbat.org/Cygwin/index.html#cygwincirca

If you want to go even further back in time, then MSYS may be the
right thing for you.  It's a rip-off of Cygwin 1.3.22 with a few
patches to supposedly building native executables a bit better.
Just make sure to grab the old MSYS, not the more recent MSYS2.
See http://www.mingw.org/wiki/MSYS


HTH,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-04-04 11:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 19:20 Colin
2014-04-03 21:22 ` René Berber
2014-04-04  8:07   ` Colin
2014-04-04  8:34 ` Corinna Vinschen
2014-04-04  9:44   ` Colin
2014-04-04 11:37     ` Corinna Vinschen [this message]
2014-04-07 11:08       ` Colin
2014-04-07 11:23         ` Corinna Vinschen
2014-04-07 16:30           ` Larry Hall (Cygwin)
2014-04-07 21:10             ` Colin
2014-04-07 22:12               ` Larry Hall (Cygwin)
2014-04-07 22:49                 ` Peter A. Castro
2014-04-08  1:28                   ` Larry Hall (Cygwin)
2014-04-08  1:50                     ` Christopher Faylor
2014-04-08  1:59                       ` Larry Hall (Cygwin)
2014-04-15 21:52                         ` Peter A. Castro
2014-04-16 13:21                           ` Achim Gratz
2014-04-16 16:02                             ` Peter A. Castro
2014-04-16 16:20                               ` Achim Gratz
2014-04-08  2:14                       ` Peter A. Castro
2014-04-07 23:26                 ` Duncan Roe
2014-04-14  8:37                 ` Colin
2014-04-04  8:40 ` Yaakov (Cygwin/X)
2014-04-04  9:57   ` Colin

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=20140404113738.GF2508@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@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).