Re: [Oorexx-devel] some questions on making your own build

[Erich S. <eri...@gm...>]

> "svn update“ did not work for me
> POs-MacBook-Pro:oorexxsvn po$ svn update
> Skipped '.'
> svn: E155007: None of the targets are working copies
> Q1: What am I doing wrong?

Hi P.O., you'll need to `cd main/trunk` first. The explanation in the Wiki
is somewhat sloppy here.
`svn update` only work from within a wokring copy.


> Q2: Should I ignore this or try to go after it?

Nothing. These are warnings that we (only) see on the Darwin platform.
I've seen them many times on the Darwin Jenkins Client on our build
machine.  Nevertheless the emitted binaries are valid and working as
expected.
Fixing is not a priority, but it would still be nice if we understood/fixed
the issue.  I haven't done any investigation about CMake polices or
MACOSX_RPATH, so I can't help.


> During CMake I get a number of these kind of warnings/errors:
> -- Looking for sys/ldr.h
> -- Looking for sys/ldr.h - not found
> Q3: Should I ignore these as well?

No, this is normal CMake output, while it tries to figure out which header
files the current platform provides. The CMake code for this is
`check_include_file(sys/ldr.h
HAVE_SYS_LDR_H)`


> Q4: You explained that the first one (it is occuring more than once) was
weird, so ignoring that one - should I try to go after the other ones and
try to silence them? or is it not necessary? the last one should be
relatively easy to fix no?

As above, no priority, but long-term we are aiming for clean builds:
there's an open bug to this regard:[bugs:#1447
<https://sourceforge.net/p/oorexx/bugs/1447/>] Clean builds without
compiler warnings


> How do I make sure they do not get lost?
> If I send it back to you (as you explained) I assume you can see if I did
it right so that you could include it?

If you make a change that you believe should go back into our repo, make
patch (using `svn diff`), attach it to a bug or feature-request, or to the
"patches" category, and a developer will check and submit to the repo if
appropriate