On 6/18/19 1:05 AM, Chris Johns wrote: > On 17/6/19 5:48 pm, Jiri Gaisler wrote: >> I don't know if it is of any help, > but I managed to build gdb-8.2.1 >> on MacOSX 10.10 using gcc-9. The trick > was to install gcc with >> 'brew install gcc', and then configure and compile > with CC=gcc-9 >> and CXX=g++-9 . I'm doing this in a KVM virtual machine, but > I >> don't think it matters. The resulting gdb binary worked fine. I am >> > now trying to build the whole tool-chain with RSB ... > > Thanks, it is great > to know this can be done. > > What I am not sure about is how to build with > Xocde's clang on a > "latest" or "current" system or with gcc on older > systems we know > have problems. Do we need to add to darwin.py a way to > specify > versions of MacOS and clang which are known to be broken and to > > automatically switch to gcc if present or raise an error if gcc is > not > found? The problem I had was that darwin.py hard-codes the compiler to /usr/bin/cc for darwin versions above 13. On macOSX 10.10 (darwin 14.5), this will not work as clang in 10.10 will fail to compile gdb. I commented out the problematic code in darwin.py, so that the configure scripts pics up the compiler of choice from $CC instead. > > > My policy for MacOS is building current RSB tools on current MacOS + > > > > Xcode versions. I do not have the time or means to support testing > two > > > separate packaging systems and their updates. I have found in the > past > > > a library installed for some other package may break a build of > our > > > tools. Sometimes the presence of a library can trigger a > different > > > configure path and this exposes things not normally seen. > > It would be > > > good to support older MacOS versions if we have active > users. Can we > > > say for a clang < 10 we attempt to use gcc? I will need > some help with > > > selecting the versions we need.
Fair enough. I don't really use MacOSX, I just used it to test if sis could be compiled OK. I also tried to compile RSB on 10.10 but it fails because the openssl libraries are too old, and an SSL error occurs when RSB fetches patches from github.. (!). Switching to an external helper such as curl would solve this problem. Jiri.
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users