From: "Csaba Ráduly" <rcsaba@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Building Bedrockdb in cygwin
Date: Tue, 14 May 2019 22:17:00 -0000 [thread overview]
Message-ID: <fd99afdd-2c4e-b6fb-3f33-b1fc1996f130@gmail.com> (raw)
In-Reply-To: <DB7PR01MB53860C5864E27ED6D90AC6F9DE080@DB7PR01MB5386.eurprd01.prod.exchangelabs.com>
On 14/05/2019 19:11, Jose Isaias Cabrera wrote:
(snip)
> However, having jumped that huddle, I encountered a new one, which is probably easier to deal with. The make command does a lot of work, but once it's going to start compiling, I get,
>
> [good stuff clipped]
> CC util/pem2der.c
> CC util/strerror.c
> CC x509/cert_app.c
> CC x509/crl_app.c
> CC x509/cert_req.c
> CC x509/cert_write.c
> CC x509/req_app.c
> make[2]: Leaving directory '/home/e608313/Bedrock/mbedtls/programs'
> make[1]: Leaving directory '/home/e608313/Bedrock/mbedtls'
> g++-6 -g -std=c++14 -fpic -O2 -Wall -Werror -Wformat-security -DGIT_REVISION=ce62c88 -I/home/e608313/Bedrock -I/home/e608313/Bedrock/mbedtls/include -MMD -MF libstuff/libstuff.d -MT libstuff/libstuff.h.gch -c libstuff/libstuff.h
> make: g++-6: Command not found
> make: *** No rule to make target 'libstuff/libstuff.d', needed by '.build/libstuff/libstuff.d'. Stop.
>
> So, it appears that I need something called g++-6. I have both gcc and g++
>
> $ ls /usr/bin/g++*
> /usr/bin/g++.exe*
>
> So, the question is, what is g++-6, and how to I get it? I tried to find it with cygwin's setup, but it's not on the distro. I tried to duckduckgo it, but I didn't get anything useful. Thoughts? Thanks
g++-6 is version 6 of the C++ compiler in the GNU Compiler Collection.
Cygwin's gcc and g++ is version 7.4.0:
$ g++.exe -dumpversion
7.4.0
Bedrockdb's makefile begins with:
# Set the compiler, if it's not set by the environment.
ifndef GXX
GXX = g++-6
endif
ifndef CC
CC = gcc-6
endif
so the C++ compiler (GXX) is set to g++-6 unless GXX is set explicitly.
You need to run make like this:
CC=gcc GXX=g++ make <whatever arguments you gave to make, if any>
This will force make to use g++ instead of g++-6
Hope this helps,
Csaba
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformat way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-05-14 22:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 19:00 Jose Isaias Cabrera
2019-05-13 18:17 ` Jose Isaias Cabrera
2019-05-13 18:48 ` Jack
2019-05-13 19:01 ` Jose Isaias Cabrera
2019-05-13 19:09 ` Achim Gratz
2019-05-13 19:24 ` Jose Isaias Cabrera
2019-05-13 19:21 ` Jack
2019-05-13 20:15 ` Jose Isaias Cabrera
2019-05-13 20:23 ` Jack
2019-05-13 20:37 ` Jose Isaias Cabrera
2019-05-13 21:26 ` Jack
2019-05-13 21:58 ` Jose Isaias Cabrera
2019-05-14 3:29 ` Brian Inglis
2019-05-14 13:51 ` Jose Isaias Cabrera
2019-05-14 16:18 ` Brian Inglis
2019-05-14 16:27 ` Jose Isaias Cabrera
2019-05-14 17:11 ` Jose Isaias Cabrera
2019-05-14 22:17 ` Csaba Ráduly [this message]
2019-05-15 12:24 ` Jose Isaias Cabrera
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=fd99afdd-2c4e-b6fb-3f33-b1fc1996f130@gmail.com \
--to=rcsaba@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).