Re: [gccsdk] wget 1.19.1 tries to write a logfile

2017-08-30 Thread Jeremy Nicoll - ml roinfo 

On 2017-08-29 18:23, Kevin Wells wrote:

In message 
  David Pitt  wrote:


Adding -o null: to the command line stops the unwanted wget-log 
appearing.



Thanks for that, so I guess the fix wil have to come from the upstream?

I don't want to have to update about half a dozen of my applications if
I don;t have to.


Would, say, renaming the binary to 'wget2' and defining an alias for 
wget so
that it executes wget2 with the "-o null:" bit added get around that for 
the

moment?

--
Jeremy Nicoll - my opinions are my own

___
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] wget 1.19.1 tries to write a logfile

2017-08-30 Thread Ralph Corderoy 
Hi Theo,

> It is still worth commenting on upstream bug trackers - they won't
> know what RISC OS is, but if the bug is not a RISC OS specific one
> then the bug report is still relevant.

It might be that RISC OS triggers it in a similar way to the odd set up
on that bug report.

src/log.c:
955 static void
956 check_redirect_output (void)
957 {
958 #ifndef WINDOWS
959   /* If it was redirected already to log file by SIGHUP, SIGUSR1 or -o 
parameter,
960* it was permanent.
961* If there was no SIGHUP or SIGUSR1 and shell is interactive
962* we check if process is fg or bg before every line is printed.*/
963   if (!redirect_request_signal_name && shell_is_interactive && 
!opt.lfilename)
964 {
 →  965   if (tcgetpgrp (STDIN_FILENO) != getpgrp ())
966 {
967   /* Process backgrounded */
  → 968   redirect_output (true,NULL);
969 }

I haven't run this code, but I wonder if 965 is true.  If Kevin is happy
to modify the source and re-build then he might be able to tell that 968
executes.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

___
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

Re: [gccsdk] wget 1.19.1 tries to write a logfile

2017-08-30 Thread Theo Markettos 
On Tue, Aug 29, 2017 at 06:23:02PM +0100, Kevin Wells wrote:
> Thanks for that, so I guess the fix wil have to come from the upstream?

Yes.  We don't generally have the manpower to curate patches that diverge
from upstream, apart from anything necessary to make it build on RISC OS.
We should be able, however, to turn around a new upstream build fairly
rapidly - so at such time that a new version is released we can produce a
new RISC OS build rapidly (though testing it is rather more difficult).

It is still worth commenting on upstream bug trackers - they won't know what
RISC OS is, but if the bug is not a RISC OS specific one then the bug report
is still relevant.  Though it seems there has been no activity on this one
since it was reported in June.

Theo

___
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK