public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Andrea Bernardini <andrebask@gmail.com>
To: kawa@sourceware.org
Subject: Re: kawa 2.2 last call
Date: Sat, 15 Oct 2016 22:28:00 -0000	[thread overview]
Message-ID: <CAPFJfssXPY+djuO6Voaz6OOHL+176f+dm8qm0ci=9Z_P78K4Pw@mail.gmail.com> (raw)
In-Reply-To: <1b573d7a-c4eb-e51c-d394-c22e7372c977@bothner.com>

Super-odd, It seems that the file is replaced during compilation

andrebask:build$ grep -n writeTo `find . -name "ByteVector.java"`
86:    public void writeTo(OutputStream out)
88:        writeTo(0, size(), out);
90:    public void writeTo(int start, int count, OutputStream out)
andrebask:build$ ./autogen.sh
andrebask:build$ ./configure --prefix=/usr --with-java-source=8
checking whether to enable maintainer-specific portions of Makefiles... no
[...]
andrebask:build$ make

[...]
[Same error]

andrebask:build$ grep -n writeTo `find . -name "ByteVector.java"`
86:    public void writeTo(int start, int count, OutputStream out)

On 15 October 2016 at 23:10, Per Bothner <per@bothner.com> wrote:
>
>
> On 10/15/2016 02:49 PM, Per Bothner wrote:
>>
>> Indeed, I get the same problem with a fresh check-out.
>>
>> But it depends on whether I'm doing:
>>
>>    svn -q checkout svn+ssh://bothner@sourceware.org/svn/kawa/trunk kawa
>>
>> or:
>>
>>    svn -q checkout svn://sourceware.org/svn/kawa/trunk kawa
>>
>> Maybe a problem with sourceware.org?  Let me check into it ...
>
>
> I'm mystified - it seems to have fixed itself:
>
> [bothner@toshie tmp]1263$ svn -q checkout
> svn://sourceware.org/svn/kawa/trunk kawa
> [bothner@toshie tmp]1264$ cd kawa
> [bothner@toshie kawa]1265$ grep writeTo **/ByteVector.java
>     public void writeTo(OutputStream out)
>         writeTo(0, size(), out);
>     public void writeTo(int start, int count, OutputStream out)
>
> If the result from the above grep shows 3 lines, then we're good.
> If it shows only a single line, then it's an old (bad) version.
>
> I'll mention the issue to the sourceware overseers; maybe they can guess
> what happened.
>
> --
>         --Per Bothner
> per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2016-10-15 22:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 20:59 Per Bothner
2016-10-14 23:39 ` David Pirotte
2016-10-14 23:45   ` Per Bothner
2016-10-15  0:17     ` David Pirotte
2016-10-15  0:38       ` Per Bothner
2016-10-15 20:56 ` Sudarshan S Chawathe
2016-10-15 21:03   ` Andrea Bernardini
2016-10-15 21:14     ` Per Bothner
2016-10-15 21:32       ` David Pirotte
2016-10-15 21:49       ` Per Bothner
2016-10-15 22:10         ` Per Bothner
2016-10-15 22:28           ` Andrea Bernardini [this message]
2016-10-15 23:05             ` Per Bothner
2016-10-15 23:19               ` Per Bothner
2016-10-15 23:39                 ` Andrea Bernardini
2016-10-15 23:41                 ` David Pirotte
2016-10-16  1:04                   ` Per Bothner
2016-10-16  2:37                   ` David Pirotte
2016-10-16 13:46                     ` Debian Jessie success report. " Sudarshan S Chawathe
2016-10-16  0:09                 ` Sudarshan S Chawathe
2016-10-16  1:17                   ` Per Bothner
2016-10-16  1:51                     ` Per Bothner
2016-10-15 22:40           ` Sudarshan S Chawathe
2016-10-15 21:10   ` Per Bothner
2016-10-15 21:22     ` Per Bothner
2016-10-15 21:58       ` Sudarshan S Chawathe
2016-10-15 22:23       ` makeinfo (version?) problem. " Sudarshan S Chawathe
2016-10-15 22:29         ` Per Bothner
2016-10-16 15:54 ` 'images' directory for Info docs. " Sudarshan S Chawathe
2016-10-16 19:41   ` Per Bothner

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='CAPFJfssXPY+djuO6Voaz6OOHL+176f+dm8qm0ci=9Z_P78K4Pw@mail.gmail.com' \
    --to=andrebask@gmail.com \
    --cc=kawa@sourceware.org \
    /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).