I committed a fix for this.

Sorry about the build break.

----- Rom

-----Original Message-----
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of 
Stephen Maclagan
Sent: Monday, October 05, 2015 7:03 PM
To: Richard Haselgrove <r.haselgr...@btopenworld.com>; David Anderson 
<da...@ssl.berkeley.edu>; boinc_dev@ssl.berkeley.edu
Subject: Re: [boinc_dev] Default process priority

Tried building Boinc 7.6 from the Boinc 7.6 head, it fails with:

stephen@stephen-MM061:~/boinc76$ make
cd . && sh generate_svn_version.sh
make  all-recursive
make[1]: Entering directory `/home/stephen/boinc76'
Making all in m4
make[2]: Entering directory `/home/stephen/boinc76/m4'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/stephen/boinc76/m4'
Making all in api
make[2]: Entering directory `/home/stephen/boinc76/api'
  CXX      boinc_api.lo
  CXX      graphics2_util.lo
  CXX      reduce_main.lo
  CXXLD    libboinc_api.la
  CXX      libboinc_graphics2_la-gutil.lo
  CXX      libboinc_graphics2_la-gutil_text.lo
  CXX      libboinc_graphics2_la-reduce_lib.lo
  CXX      libboinc_graphics2_la-graphics2.lo
  CXX      libboinc_graphics2_la-graphics2_unix.lo
  CXXLD    libboinc_graphics2.la
  CXX      boinc_opencl.lo
  CXXLD    libboinc_opencl.la
rm -f libboinc_api.a
/bin/ln .libs/libboinc_api.a .
rm -f libboinc_graphics2.a
/bin/ln .libs/libboinc_graphics2.a .
rm -f libboinc_opencl.a
/bin/ln .libs/libboinc_opencl.a .
make[2]: Leaving directory `/home/stephen/boinc76/api'
Making all in lib
make[2]: Entering directory `/home/stephen/boinc76/lib'
  CXX      libboinc_la-app_ipc.lo
  CXX      libboinc_la-base64.lo
  CXX      libboinc_la-cc_config.lo
  CXX      libboinc_la-cert_sig.lo
  CXX      libboinc_la-coproc.lo
  CXX      libboinc_la-diagnostics.lo
diagnostics.cpp:707:6: warning: unused parameter 'siginfo' [-Wunused-parameter] 
 void boinc_catch_signal(int signal, struct siginfo *siginfo, void *sigcontext) 
{
      ^
diagnostics.cpp:707:6: warning: unused parameter 'sigcontext' 
[-Wunused-parameter]
diagnostics.cpp: In function 'void boinc_catch_signal(int, siginfo*, void*)':
diagnostics.cpp:734:73: warning: ignoring return value of 'ssize_t write(int, 
const void*, size_t)', declared with attribute warn_unused_result 
[-Wunused-result]
     (void) write(fileno(stderr),"Stack trace (",strlen("Stack trace ("));
                                                                         ^
diagnostics.cpp:743:49: warning: ignoring return value of 'ssize_t write(int, 
const void*, size_t)', declared with attribute warn_unused_result 
[-Wunused-result]
     (void) write(fileno(stderr),p+1,strlen(p+1));
                                                 ^
diagnostics.cpp:744:65: warning: ignoring return value of 'ssize_t write(int, 
const void*, size_t)', declared with attribute warn_unused_result 
[-Wunused-result]
     (void) write(fileno(stderr)," frames):",strlen(" frames):"));
                                                                 ^
diagnostics.cpp:746:40: warning: ignoring return value of 'ssize_t write(int, 
const void*, size_t)', declared with attribute warn_unused_result 
[-Wunused-result]
     (void) write(fileno(stderr),mbuf,1);
                                        ^
  CXX      libboinc_la-filesys.lo
filesys.cpp: In function 'int boinc_copy(const char*, const char*)':
filesys.cpp:602:42: warning: ignoring return value of 'int chown(const char*, 
__uid_t, __gid_t)', declared with attribute warn_unused_result [-Wunused-result]
     chown(newf, sbuf.st_uid, sbuf.st_gid);
                                          ^
  CXX      libboinc_la-gui_rpc_client.lo
  CXX      libboinc_la-gui_rpc_client_ops.lo
  CXX      libboinc_la-gui_rpc_client_print.lo
  CXX      libboinc_la-hostinfo.lo
  CXX      libboinc_la-md5.lo
  CXX      libboinc_la-md5_file.lo
  CXX      libboinc_la-mem_usage.lo
  CXX      libboinc_la-mfile.lo
  CXX      libboinc_la-miofile.lo
  CXX      libboinc_la-msg_log.lo
  CXX      libboinc_la-network.lo
  CXX      libboinc_la-notice.lo
  CXX      libboinc_la-opencl_boinc.lo
  CXX      libboinc_la-parse.lo
  CXX      libboinc_la-prefs.lo
  CXX      libboinc_la-procinfo.lo
  CXX      libboinc_la-proc_control.lo
  CXX      libboinc_la-proxy_info.lo
  CXX      libboinc_la-shmem.lo
shmem.cpp: In function 'int create_shmem_mmap(const char*, size_t, void**)':
shmem.cpp:340:27: warning: ignoring return value of 'ssize_t write(int, const 
void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
         write(fd, "\0", 1);
                           ^
  CXX      libboinc_la-str_util.lo
  CXX      libboinc_la-url.lo
  CXX      libboinc_la-util.lo
  CXX      libboinc_la-procinfo_unix.lo
  CXX      libboinc_la-synch.lo
  CXX      libboinc_la-unix_util.lo
  CXXLD    libboinc.la
  CXX      libboinc_crypt_la-crypt.lo
crypt.cpp: In function 'int scan_key_hex(FILE*, KEY*, int)':
crypt.cpp:220:29: warning: ignoring return value of 'int fscanf(FILE*, const 
char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
         fscanf(f, "%2x", &n);
                             ^
  CXXLD    libboinc_crypt.la
rm -f libboinc.a
/bin/ln .libs/libboinc.a .
rm -f libboinc_crypt.a
/bin/ln .libs/libboinc_crypt.a .
make[2]: Leaving directory `/home/stephen/boinc76/lib'
Making all in client
make[2]: Entering directory `/home/stephen/boinc76/client'
  CXX      boinc_client-acct_mgr.o
  CXX      boinc_client-acct_setup.o
  CXX      boinc_client-app.o
  CXX      boinc_client-app_config.o
  CXX      boinc_client-app_control.o
app_control.cpp: In member function 'bool ACTIVE_TASK::finish_file_present()':
app_control.cpp:619:31: warning: ignoring return value of 'char* fgets(char*, 
int, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
     fgets(buf, sizeof(buf), f);
                               ^
app_control.cpp:620:31: warning: ignoring return value of 'char* fgets(char*, 
int, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
     fgets(buf, sizeof(buf), f);
                               ^
app_control.cpp:621:33: warning: ignoring return value of 'char* fgets(char*, 
int, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
     fgets(buf2, sizeof(buf2), f);
                                 ^
app_control.cpp: In member function 'bool 
ACTIVE_TASK::temporary_exit_file_present(double&, char*, bool&)':
app_control.cpp:647:30: warning: ignoring return value of 'char* fgets(char*, 
int, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
     (void) fgets(buf, 256, f);     // read the \n
                              ^
app_control.cpp:648:30: warning: ignoring return value of 'char* fgets(char*, 
int, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
     (void) fgets(buf, 256, f);
                              ^
app_control.cpp: In member function 'void ACTIVE_TASK::read_task_state_file()':
app_control.cpp:1594:34: warning: ignoring return value of 'size_t fread(void*, 
size_t, size_t, FILE*)', declared with attribute warn_unused_result 
[-Wunused-result]
     (void) fread(buf, 1, 4096, f);
                                  ^
  CXX      boinc_client-app_start.o
app_start.cpp: In member function 'int ACTIVE_TASK::start(bool)':
app_start.cpp:1075:49: warning: ignoring return value of 'FILE* freopen(const 
char*, const char*, FILE*)', declared with attribute warn_unused_result 
[-Wunused-result]
         (void) freopen(STDERR_FILE, "a", stderr);
                                                 ^
app_start.cpp: In function 'void run_test_app()':
app_start.cpp:1337:29: warning: ignoring return value of 'char* getcwd(char*, 
size_t)', declared with attribute warn_unused_result [-Wunused-result]
     getcwd(buf, sizeof(buf));   // so we can see where we're running
                             ^
  CXX      boinc_client-async_file.o
  CXX      boinc_client-check_state.o
  CXX      boinc_client-client_msgs.o
  CXX      boinc_client-client_state.o
client_state.cpp: In function 'void set_client_priority()':
client_state.cpp:395:26: error: a function-definition is not allowed here 
before '{' token  int CLIENT_STATE::init() {
                          ^
client_state.cpp:2253:1: error: expected '}' at end of input  }  ^
client_state.cpp: At global scope:
client_state.cpp:285:13: warning: 'void check_too_large_jobs()' defined but not 
used [-Wunused-function]  static void check_too_large_jobs() {
             ^
client_state.cpp:384:13: warning: 'void set_client_priority()' defined but not 
used [-Wunused-function]  static void set_client_priority() {
             ^
make[2]: *** [boinc_client-client_state.o] Error 1
make[2]: Leaving directory `/home/stephen/boinc76/client'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/stephen/boinc76'
make: *** [all] Error 2
stephen@stephen-MM061:~/boinc76$ 


Claggy

> Date: Wed, 30 Sep 2015 15:51:08 +0000
> From: r.haselgr...@btopenworld.com
> To: da...@ssl.berkeley.edu; boinc_dev@ssl.berkeley.edu
> Subject: Re: [boinc_dev] Default process priority
> 
> Well, yes, that's where I got the names from. But it does make one wonder 
> which of email, github, BOINC message boards, googlegroups, twitter, 
> facebook, ..., ..., hold the master ring for that "subtle, planned, evolved" 
> design process that BOINC needs. If everyone just bolts on their own "my 
> project needs..." without reference to anyone else, aren't we going to end up 
> in the house of babel?
> 
> I was going to refresh my memory of the current 'contact us' recommendations, 
> but I'm currently getting "connection refused" from the BOINC home page.
> 
> 
> 
> > On Wednesday, 30 September 2015, 16:42, David Anderson 
> > <da...@ssl.berkeley.edu> wrote:
> > >T hey both interacted via Github:
> > https://github.com/BOINC/boinc/issues/1128
> > It should be possible to message them that way.
> > -- D
> > 
> > 
> > On 9/30/2015 2:51 AM, Richard Haselgrove wrote:
> >>  Thanks - that at least keeps the previous values, and I see that 
> >> the two
> > groups can be set (or not set) independently. I've updated the Wiki 
> > to match.
> >> 
> >>  Does anybody know whether either Daniel Hendrycks (original trac 
> >> request)
> > or Aen Bleidd (patch contributor) is in a position to follow this 
> > discussion - I can't match either of them to an email address on the 
> > subscriber list, and I don't know which project(s) they might be active at.
> >> 
> >>  We might be able to mention that Daniel's original problem could 
> >> have
> > been solved by using Process Lasso - that's what I use for the one 
> > and only Einstein@Home application version which runs best at 
> > REALTIME priority (I wouldn't wan't to switch the whole of BOINC to 
> > that, for obvious reasons).
> >> 
> >> 
> >> 
> >>>  On Wednesday, 30 September 2015, 6:35, David Anderson
> > <da...@ssl.berkeley.edu> wrote:
> >>>>  How about if you can specify two priorities in cc_config.xml:
> >>>  <process_priority> for CPU-intensive apps,and  
> >>> <process_priority_special>for others (GPU, NCI, wrapper).
> >>>  -- David
> >>> 
> >>> 
> >>>  On 9/29/2015 2:32 PM, Richard Haselgrove wrote:
> >>>>    The trouble with this global starting point is that - if 
> >>>> selected
> > - it
> >>>  knocks out the subtle, planned, evolved behaviour which BOINC 
> >>> already
> > has for
> >>>  managing priority.
> >>>>    We currently have special priority cases (in the sense of OS 
> >>>> run
> > priority -
> >>>  point taken, and well made) for NCI apps, GPU apps, and wrapper apps. 
> > All of
> >>>  those go out of the window if the user chooses a Default Process
> > Priority. This
> >>>  feels like a special case for the benefit of users who run one 
> >>> project
> > only
> >>>  under BOINC, and as such rather mitigates against the vision of 
> >>> BOINC
> > as a
> >>>  project-neutral (and multi-project) infrastructure.
> >>>> 
> >>>> 
> >>>>>    On Tuesday, 29 September 2015, 21:00, David Anderson
> >>>  <da...@ssl.berkeley.edu> wrote:
> >>>>>>    We could increase the resolution;
> >>>>>    a global setting is a good starting point.
> >>>>> 
> >>>>>    Just so everyone knows:
> >>>>>    this involves the OS priority at which tasks run,
> >>>>>    not BOINC's prioritization of tasks (i.e. which ones run
> > first).
> >>>>> 
> >>>>>    -- David
> >>>>> 
> >>>>>    On 9/29/2015 1:10 AM, Richard Haselgrove wrote:
> >>>>>>      Is it really appropriate for the new Default process
> > priority
> >>>  switch to
> >>>>>    operate at the cc_config level?
> >>>>>>      I'd have thought it was a more natural fit for
> > app_config, so
> >>>  that the
> >>>>>    user could adjust the relative priority of different
> > projects,
> >>>  different
> >>>>>    applications, and even different app_versions.
> >>>>>>      _______________________________________________
> >>>>>>      boinc_dev mailing list
> >>>>>>     boinc_dev@ssl.berkeley.edu
> >>>>>>     http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> >>>>>>      To unsubscribe, visit the above URL and
> >>>>>>      (near bottom of page) enter your email address.
> >>>>>    _______________________________________________
> >>>>>    boinc_dev mailing list
> >>>>>   boinc_dev@ssl.berkeley.edu
> >>>>>   http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> >>>>>    To unsubscribe, visit the above URL and
> >>>>>    (near bottom of page) enter your email address.
> >>>>> 
> >>>  _______________________________________________
> >>>  boinc_dev mailing list
> >>>  boinc_dev@ssl.berkeley.edu
> >>>  http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> >>>  To unsubscribe, visit the above URL and  (near bottom of page) 
> >>> enter your email address.
> >>> 
> > 
> _______________________________________________
> boinc_dev mailing list
> boinc_dev@ssl.berkeley.edu
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and (near bottom of page) enter 
> your email address.
                                          
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to