Hello, After several attempts of passing that command in the wrong build directory, I finally was able to find the right build directory, and here's what I found in ida.log: https://pastebin.com/hPMmFCyj
I really can't make out what's going on or what to do next. Please help On Fri, Jul 30, 2021 at 8:57 PM Joel Sherrill <j...@rtems.org> wrote: > On Fri, Jul 30, 2021 at 1:32 PM Ida Delphine <idad...@gmail.com> wrote: > > > > Just installed swig and now met with another error. Can't find what is > really wrong. > > RTEMS Source Builder - Set Builder, 6 (c938bd7cbe16) > > Build Set: 6/rtems-llvm > > Build Set: devel/swig.bset > > Build Set: devel/autotools-internal.bset > > config: devel/autoconf-2.69-1.cfg > > package: autoconf-2.69-x86_64-linux-gnu-1 > > building: autoconf-2.69-x86_64-linux-gnu-1 > > sizes: autoconf-2.69-x86_64-linux-gnu-1: 7.493MB (installed: 0.000B) > > cleaning: autoconf-2.69-x86_64-linux-gnu-1 > > config: devel/automake-1.12.6-1.cfg > > package: automake-1.12.6-x86_64-linux-gnu-1 > > building: automake-1.12.6-x86_64-linux-gnu-1 > > sizes: automake-1.12.6-x86_64-linux-gnu-1: 8.085MB (installed: 0.000B) > > cleaning: automake-1.12.6-x86_64-linux-gnu-1 > > config: devel/libtool-2.4.2-1.cfg > > package: libtool-2.4.2-x86_64-linux-gnu-1 > > building: libtool-2.4.2-x86_64-linux-gnu-1 > > sizes: libtool-2.4.2-x86_64-linux-gnu-1: 12.775MB (installed: 0.000B) > > cleaning: libtool-2.4.2-x86_64-linux-gnu-1 > > cleaning: autoconf-2.69-x86_64-linux-gnu-1 > > cleaning: automake-1.12.6-x86_64-linux-gnu-1 > > cleaning: libtool-2.4.2-x86_64-linux-gnu-1 > > Build Sizes: usage: 12.775MB total: 79.327MB (sources: 79.308MB, > patches: 19.412KB, installed 0.000B) > > Build Set: Time 0:00:17.154758 > > config: devel/swig-4.0.1.cfg > > package: swig-4.0.1-x86_64-linux-gnu-1 > > building: swig-4.0.1-x86_64-linux-gnu-1 > > sizes: swig-4.0.1-x86_64-linux-gnu-1: 106.899MB (installed: 0.000B) > > cleaning: swig-4.0.1-x86_64-linux-gnu-1 > > cleaning: swig-4.0.1-x86_64-linux-gnu-1 > > Build Set: Time 0:01:27.065144 > > config: tools/rtems-llvm-8.0.1.cfg > > package: rtems-llvm-8.0.1-x86_64-linux-gnu-1 > > building: rtems-llvm-8.0.1-x86_64-linux-gnu-1 > > error: building rtems-llvm-8.0.1-x86_64-linux-gnu-1 > > Build FAILED > > See error report: rsb-report-rtems-llvm-8.0.1-x86_64-linux-gnu-1.txt > > error: building rtems-llvm-8.0.1-x86_64-linux-gnu-1 > > Build Set: Time 0:04:53.632167 > > Build FAILED > > The error report: https://pastebin.com/nFYzqWqY > > I don't see any compiler errors. I see warnings and if they built with > -Werror, > then it would fail. > > I think there is a way to force a cmake build to show the command invoked. > This > has lots of details: > > > https://stackoverflow.com/questions/2670121/using-cmake-with-gnu-make-how-can-i-see-the-exact-commands > > I think you can manually go down into the build directory which is left > after the build failure, and type "make VERBOSE=1" >ida.log 2>&1" > > Then the file ida.log should show all the commands. > > The URL above shows how to do it via cmake. But in this case, I think > going into the RSB build/ directory and doing the make by hand will > give us the next bit of into -- does it compile with -Werror. > > > > > On Fri, Jul 30, 2021 at 2:24 PM Joel Sherrill <j...@rtems.org> wrote: > >> > >> On Fri, Jul 30, 2021 at 12:46 AM Ida Delphine <idad...@gmail.com> > wrote: > >> > > >> > Hello everyone, > >> > I have been trying to build llvm using the command > >> > ../source-builder/sb-set-builder --prefix=$HOME/development/rtems/6 > 6/rtems-llvm > >> > Here's the error report > >> > https://pastebin.com/vAXgwXMW > >> > >> It would have been helpful to have put the error lines in the email > >> and a link to the full log. > >> > >> -- Could NOT find libedit (missing: libedit_INCLUDE_DIRS > libedit_LIBRARIES) > >> -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) > >> CMake Error at > /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 > >> (message): > >> Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR) > >> Call Stack (most recent call first): > >> /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 > >> (_FPHSA_FAILURE_MESSAGE) > >> /usr/share/cmake-3.16/Modules/FindSWIG.cmake:64 > >> (FIND_PACKAGE_HANDLE_STANDARD_ARGS) > >> tools/lldb/scripts/CMakeLists.txt:18 (find_package) > >> > >> > Please what am I missing? > >> > >> Based on google results and other people having the same issue, you may > not > >> have swig installed. It is something to install with npm from what I > >> see. Other people > >> have it but need to set some variables to let cmake know where it is. > >> > >> Hopefully installing it will help. Chris should comment on this from > >> an RSB perspective. > >> > >> --joel > >> > >> > > >> > _______________________________________________ > >> > devel mailing list > >> > devel@rtems.org > >> > http://lists.rtems.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
