public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Sorin Adrian Savu <sorin@itguy.ro>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Compiling rtorrent-0.9.4-1 with cygport
Date: Fri, 11 Nov 2016 13:57:00 -0000	[thread overview]
Message-ID: <CAFeE7GmtLmMdbx=PGc7T8mPC8Lc+wLvQD4dYT2KjS5q_iq9J+A@mail.gmail.com> (raw)
In-Reply-To: <e37e713d-c09a-540e-b531-4107492a03a1@gmail.com>

On Tue, Nov 8, 2016 at 8:24 PM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
> On 26/10/2016 07:10, Sorin Adrian Savu wrote:
>>
>> Hello!
>>
>> I'm trying to compile rtorrent-0.9.4-1 with cygport to add support for
>> XMLRPC.
>
>
> rtorrent package is currently 0.9.6-1.
> Any reason for 0.9.4 ?

Yes, tracker doesn't accept 0.9.6-1

>
>
>>
>> I've added:
>> CYGCONF_ARGS="--with-xmlrpc-c"
>> in the cygport file.
>>
>> When I try to compile, I get the following error:
>>
>>
>> /usr/src/rtorrent-0.9.4-1.src/rtorrent-0.9.4-1.x86_64/src/rtorrent-0.9.4/src/display/window_file_list.cc:
>> In function ‘std::wstring display::wstring_width(const string&, int)’:
>>
>> /usr/src/rtorrent-0.9.4-1.src/rtorrent-0.9.4-1.x86_64/src/rtorrent-0.9.4/src/display/window_file_list.cc:80:38:
>> error: ‘wcswidth’ was not declared in this scope
>>    int swidth = wcswidth(result, width);
>>                                       ^
>>
>> /usr/src/rtorrent-0.9.4-1.src/rtorrent-0.9.4-1.x86_64/src/rtorrent-0.9.4/src/display/window_file_list.cc:87:18:
>> error: ‘::wcwidth’ has not been declared
>>        int next = ::wcwidth(result[length]);
>>                   ^
>> After some investigation it seems to be related to _XOPEN_SOURCE
>> flag, but when I add that I get other errors.
>>
>> I've tried compiling with the CYGCONF_ARGS commented out and the
>> behavior is the same.
>>
>> Am I missing something ? How can I find out which compile flags were
>> used at the package build time ?
>
>
> You are not missing anything.
> CYGCONF_ARGS was empty for last binary build.
>
> The cygwin headers changed from last time I built the rtorrent package.
> I see the same error today.
>
> Adding
>  CXXFLAGS+=" -D_GNU_SOURCE"
> to the cygport should solve the build problem.

Tested today, and I can confirm it works. Would you mind pointing me
to some documentation/info about what changed in the headers ?

>
> about --with-xmlrpc-c, I think there is no cygwin package to
> support such  configuration.

I've used the source package directly for lib xmlrpc-c

>
> Regards
> Marco
>

Thanks for your time!

--
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

  reply	other threads:[~2016-11-11 12:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26  5:55 Sorin Adrian Savu
2016-11-08 18:25 ` Marco Atzeri
2016-11-11 13:57   ` Sorin Adrian Savu [this message]
2016-11-12 22:55     ` Marco Atzeri

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='CAFeE7GmtLmMdbx=PGc7T8mPC8Lc+wLvQD4dYT2KjS5q_iq9J+A@mail.gmail.com' \
    --to=sorin@itguy.ro \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.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).