From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: 64bit lapack-3.7.0-1.tar.xz - Empty
Date: Mon, 03 Apr 2017 15:44:00 -0000 [thread overview]
Message-ID: <76251bb5-9303-6456-11b4-755032891880@gmail.com> (raw)
In-Reply-To: <2b672a97-dc43-492f-48d0-c1fabdb7d56c@gmail.com>
On 03/04/2017 17:07, cyg Simple wrote:
> On 4/3/2017 11:00 AM, Marco Atzeri wrote:
>> On 03/04/2017 16:53, cyg Simple wrote:
>>> The file is lapack-3.7.0-1.tar.xz 32 bytes with no contents. I've tried
>>> two different mirrors. There are also no dependencies applied.
>>>
>>> Reverting back to lapack-3.6.1-1.tar.xz proves that it is empty as well
>>> with the same no dependency rules.
>>>
>>
>>
>> source only. all the contents is in:
>>
>> $ cygcheck -cd |grep lapack
>> liblapack-devel 3.7.0-1
>> liblapack-doc 3.7.0-1
>> liblapack0 3.7.0-1
>>
>
> Then these should be installed dependents of the chosen lapack. Source
> only means nothing when you can choose the binary download.
>
there are today no packages depending from lapack.
I miss the relevance of your last comment; there are
~ 473 empty binary package in the distribution.
Please note that lapack is empty but the debug file for the three
binaries is called lapack-debuginfo anyway as the upstream source file
is called lapack.
Regards
Marco
--
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:[~2017-04-03 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 14:52 cyg Simple
2017-04-03 15:00 ` Marco Atzeri
2017-04-03 15:07 ` cyg Simple
2017-04-03 15:44 ` Marco Atzeri [this message]
2017-04-04 12:43 ` cyg Simple
2017-04-04 13:04 ` Marco Atzeri
2017-04-04 17:03 ` cyg Simple
2017-04-04 17:19 ` Yaakov Selkowitz
2017-04-04 19:17 ` Marco Atzeri
2017-04-05 17:10 ` cyg Simple
2017-04-07 11:44 ` Jon Turney
2017-04-07 13:43 ` cyg Simple
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=76251bb5-9303-6456-11b4-755032891880@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).