public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: problem using gcc-core for compile qemu
Date: Fri, 8 Jan 2021 06:52:22 +0100	[thread overview]
Message-ID: <ea1fab30-88b1-3096-8080-9876cef32116@gmail.com> (raw)
In-Reply-To: <cd43634f0573a04bb44d5b9d9165f49feb4839de.camel@gmail.com>

On 07.01.2021 23:33, juan carlos rebate rodriguez via Cygwin wrote:
> El jue, 07-01-2021 a las 15:39 +0100, Marco Atzeri via Cygwin escribió:
>> If the upstream developers have not bothered to use a serious
>> configure system,, I doubt there is a easy solution.
>>
>> Questions:
>>
>> Are you trying to build for Cygwin or for Windows in general ?
>> why you can not use the Windows binaries ?
> 
> 
> I try to build for standard windows, for this reason I use gcc-core and
> not cygwin-gcc, if I can use normal windows binaries, what I cannot is
> use mingw because it is not able to find resources in the system while
> gcc does can, I can't use virtualbx because what I need is to emulate
> the aarch64 architecture, I don't want to use binaries compiled by
> others, one of the reasons is that those binaries don't include sd-card
> emulation support, but if those binaries are compiled by me I can
> include what I want, if I install this library through the cygwin
> package manager and then use gcc-core it is able to search for it, it
> is not my desire to get into the swamp and have to modify the
> configuration script, the An easier solution would be to try to trick
> mingw into looking for external libraries without having to modify
> their paths, since when editing them the compilation process slows down
> even more than it already is

Juan Carlos,
you are misunderstanding what gcc-core is.
gcc-core includes only the compiler that targets Cygwin itself.

To compile for Windows on Cygwin you need to use a cross-compiler.
The 64 bit one is in:

$ cygcheck -l mingw64-i686-gcc-core | grep usr/bin
/usr/bin/i686-w64-mingw32-cpp.exe
/usr/bin/i686-w64-mingw32-gcc.exe
/usr/bin/i686-w64-mingw32-gcc-10.exe
/usr/bin/i686-w64-mingw32-gcc-ar.exe
/usr/bin/i686-w64-mingw32-gcc-nm.exe
/usr/bin/i686-w64-mingw32-gcc-ranlib.exe
/usr/bin/i686-w64-mingw32-gcov.exe
/usr/bin/i686-w64-mingw32-gcov-dump.exe
/usr/bin/i686-w64-mingw32-gcov-tool.exe
/usr/bin/i686-w64-mingw32-lto-dump.exe

however there is another problem for building quemu

---------------------------------------------------
$ PKG_CONFIG_LIBDIR=/usr/x86_64-w64-mingw32/sys-root/mingw ./configure 
--cc=/usr/bin/x86_64-w64-mingw32-gcc.exe 
           Using './build' as the directory for build output

ERROR: glib-2.48 gthread-2.0 is required to compile QEMU
----------------------------------------------------

and the cross gthread package is not present on Cygwin

$ cygcheck -cd |grep mingw64-x86
mingw64-x86_64-binutils                 2.34-1
mingw64-x86_64-bzip2                    1.0.6-4
mingw64-x86_64-gcc-core                 10.2.0-1
mingw64-x86_64-gcc-g++                  10.2.0-1
mingw64-x86_64-gettext                  0.19.8.1-2
mingw64-x86_64-glib2.0                  2.54.3-1
mingw64-x86_64-glib2.0-networking       2.54.1-1
mingw64-x86_64-gmp                      6.1.2-1
mingw64-x86_64-gnutls                   3.5.18-1
mingw64-x86_64-headers                  8.0.0-1
mingw64-x86_64-libffi                   3.2.1-2
mingw64-x86_64-libgcrypt                1.8.2-1
mingw64-x86_64-libgpg-error             1.28-1
mingw64-x86_64-libidn2                  2.0.4-1
mingw64-x86_64-libproxy                 0.4.14-1
mingw64-x86_64-libtasn1                 4.13-1
mingw64-x86_64-libunistring             0.9.6-1
mingw64-x86_64-nettle                   3.4-1
mingw64-x86_64-p11-kit                  0.23.10-1
mingw64-x86_64-pcre                     8.44-1
mingw64-x86_64-runtime                  8.0.0-1
mingw64-x86_64-win-iconv                0.0.6-2
mingw64-x86_64-windows-default-manifest 6.4-1
mingw64-x86_64-winpthreads              8.0.0-1
mingw64-x86_64-xz                       5.2.3-1
mingw64-x86_64-zlib                     1.2.11-1

I suggest you to try using MingW64 enviroment for compiling QEMU

http://mingw-w64.org/

Regards
Marco

  reply	other threads:[~2021-01-08  5:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07  3:23 Juan carlos Rebate
2021-01-07  3:37 ` Eliot Moss
2021-01-07 13:43   ` Eliot Moss
2021-01-07 14:39 ` Marco Atzeri
2021-01-07 14:53   ` Csaba Raduly
2021-01-07 16:18     ` Marco Atzeri
2021-01-07 17:00       ` Eliot Moss
2021-01-07 22:33   ` juan carlos rebate rodriguez
2021-01-08  5:52     ` Marco Atzeri [this message]
2021-01-08  6:55       ` Marco Atzeri
2021-01-08  8:42     ` Arthur Norman
2021-01-08 13:06       ` Eliot Moss
2021-01-08 13:19         ` Marco Atzeri
2021-01-08 20:54       ` juan carlos rebate rodriguez
2021-01-08 22:32         ` Lee
2021-01-08 22:33         ` Brian Inglis
2021-01-07 17:21 ` Brian Inglis

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=ea1fab30-88b1-3096-8080-9876cef32116@gmail.com \
    --to=marco.atzeri@gmail.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).