From: Marco Atzeri <marco.atzeri@gmail.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Build of glm-0.9.7.6-1-src.tar.xz does not work.
Date: Sun, 23 Aug 2020 20:28:08 +0200 [thread overview]
Message-ID: <e33e9ccd-5575-2a9b-a3a0-79a15aaec190@gmail.com> (raw)
In-Reply-To: <7d476d33-243f-426a-33f5-fdbd57452da4@gmail.com>
On 23.08.2020 18:03, Marco Atzeri wrote:
> On 23.08.2020 17:30, Jon Turney wrote:
>> On 22/08/2020 06:00, Marco Atzeri via Cygwin wrote:
>>> On 21.08.2020 10:35, Carlo B. via Cygwin wrote:
>>>> Hello,
>>>> I tried to rebuild glm-0.9.7.6-1-src.tar.xz but the "install" command
>>>> does not work.
>>>> I'm getting this error message:
>>>>
>>>>>>> Installing glm-0.9.7.6-1.noarch
>>>> make: *** Nessuna regola per generare l'obiettivo «install». Arresto.
>>>> *** ERROR: make install DESTDIR failed
>>>>
>>>> Translated in english, it should be something like this:
>>>> "No rules to generate target <<install>>. Stop."
>>>>
>> [...]
>>>
>>> the error is caused by the build system using now cmake+ninja for
>>> the execution
>>>
>>> while mingw64-i686-glm and mingw64-x86_64-glm builds stay on the
>>> previous cmake+make
>>>
>> I am a bit confused by this. What causes the default generator used
>> by cmake to change? Having old .cygports break due to that seems bad.
>>
>
> not sure.
> I guess that if ninja is available the glm cmake settings
> give it a precedence.
>
> It is also possible that the latest cmake is behaving differently
> than previous one.
it seems a cmake change, building without ninja now produces
>>> Compiling glm-0.9.7.6-1.noarch
CMake Error: CMake was unable to find a build program corresponding to
"Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a
different build tool.
-- Configuring incomplete, errors occurred!
> Regards
> Marco
>
>
next prev parent reply other threads:[~2020-08-23 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 8:35 Carlo B.
2020-08-22 5:00 ` Marco Atzeri
2020-08-23 15:30 ` Jon Turney
2020-08-23 16:03 ` Marco Atzeri
2020-08-23 18:28 ` Marco Atzeri [this message]
2020-08-25 20:06 ` Carlo B.
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=e33e9ccd-5575-2a9b-a3a0-79a15aaec190@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).