From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: Cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: [ITP] procps-ng
Date: Tue, 22 Mar 2016 16:03:00 -0000 [thread overview]
Message-ID: <CAGHJv4d5xgVX5Z8FKQh4CKbzH=WXCVSd=2-8sgN6jaazgFR94g@mail.gmail.com> (raw)
In-Reply-To: <56F15DB2.7090107@gmail.com>
On 22 March 2016 at 10:58, Marco Atzeri wrote:
>
> On 22/03/2016 14:46, Corinna Vinschen wrote:
>>
>> - On x86_64 the libprocps-ng4 and libprocps-ng-devel packages are missing.
>
> Are you sure ?
>
> $ tar -tf libprocps-ng4/libprocps-ng4-3.3.10-1.tar.xz
> usr/bin/cygprocps-4.dll
> usr/share/man/man3/
> usr/share/man/man3/openproc.3.gz
> usr/share/man/man3/readproc.3.gz
> usr/share/man/man3/readproctab.3.gz
>
>
> $ tar -tf ./libprocps-ng-devel/libprocps-ng-devel-3.3.10-1.tar.xz
> usr/include/
> usr/include/proc/
> usr/include/proc/alloc.h
> ..
> usr/lib/pkgconfig/libprocps.pc
Yes, the libprocps-ng4 and libprocgs-ng-devel directories are missing
in the x86_64 directory. They are present in the i686 directory.
Cheers,
Chris
--
Chris Sutcliffe
next prev parent reply other threads:[~2016-03-22 15:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:18 Wayne Porter
2016-03-16 20:48 ` Warren Young
2016-03-16 20:51 ` Yaakov Selkowitz
2016-03-19 0:25 ` Wayne Porter
2016-03-20 20:55 ` Corinna Vinschen
2016-03-20 21:41 ` Wayne Porter
2016-03-20 21:47 ` Wayne Porter
2016-03-21 9:40 ` Corinna Vinschen
2016-03-21 10:54 ` Wayne Porter
2016-03-21 12:05 ` Corinna Vinschen
2016-03-21 13:06 ` Corinna Vinschen
2016-03-21 21:01 ` Wayne Porter
2016-03-22 12:32 ` Corinna Vinschen
2016-03-22 13:46 ` Marco Atzeri
2016-03-22 15:14 ` Corinna Vinschen
2016-03-22 15:16 ` Marco Atzeri
2016-03-22 16:03 ` Chris Sutcliffe [this message]
2016-03-22 18:06 ` Wayne Porter
2016-03-22 18:12 ` Chris Sutcliffe
2016-03-22 21:00 ` Wayne Porter
2016-03-24 13:29 ` Corinna Vinschen
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='CAGHJv4d5xgVX5Z8FKQh4CKbzH=WXCVSd=2-8sgN6jaazgFR94g@mail.gmail.com' \
--to=ir0nh34d@gmail.com \
--cc=cygwin-apps@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).