[email protected] wrote: > Hi, > > I got around the Python problems...but got new compilation hazards...: > > > .... > cd /var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4_build/common > && /usr/bin/x86_64-pc-linux-gnu-g++ -DGLM_FORCE_CTOR_INIT -DHAVE_STDINT_H > -DKICAD_SCRIPTING -DKICAD_SCRIPTING_ACTION_MENU -DKICAD_SCRIPTING_MODULES > -DKICAD_SCRIPTING_PYTHON3 -DKICAD_SCRIPTING_WXPYTHON > -DKICAD_SCRIPTING_WXPYTHON_PHOENIX -DKICAD_SPICE -DKICAD_USE_OCE > -DUSE_WX_OVERLAY -DWXUSINGDLL -DWX_COMPATIBILITY -D_FILE_OFFSET_BITS=64 > -D__WXGTK__ > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/include > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/. > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/./dialogs > > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/./widgets > > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/./dialog_about > -I/usr/include/cairo -I/usr/include/pixman-1 > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/../3d-viewer > > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/../pcbnew > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4_build > -I/usr/include/python3.7m > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/scripting > -I/usr/lib64/oce-0.18/../../include/oce > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/bitmaps_png/include > > -I/var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/polygon/include > -isystem /usr/lib64/wx/include/gtk3-unicode-3.0-gtk3 -isystem > /usr/include/wx-3.0-gtk3 -DNDEBUG -DNDEBUG -Wall -O2 -pipe -march=native > -Wsuggest-override -Werror=vla -pthread -Wshadow -fPIC -fvisibility=hidden > -fvisibility-inlines-hidden -std=gnu++11 -o > CMakeFiles/common.dir/prependpath.cpp.o -c > /var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/prependpath.cpp > /var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/lib_tree_model.cpp: > In member function ‘void LIB_TREE_NODE::AssignIntrinsicRanks(bool)’: > /var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/lib_tree_model.cpp:78:14: > error: ‘sort’ is not a member of ‘std’; did you mean ‘sqrt’? > 78 | std::sort( sort_buf.begin(), sort_buf.end(), > | ^~~~ > | sqrt > /var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/lib_tree_model.cpp: > In member function ‘void LIB_TREE_NODE::SortNodes()’: > /var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4/common/lib_tree_model.cpp:90:10: > error: ‘sort’ is not a member of ‘std’; did you mean ‘sqrt’? > 90 | std::sort( Children.begin(), Children.end(), > | ^~~~ > | sqrt > [ 43%] Building CXX object common/CMakeFiles/common.dir/printout.cpp.o > cd /var/tmp/portage/sci-electronics/kicad-5.1.4/work/kicad-5.1.4_build/common > && /usr/bin/x86_64-pc-linux-gnu-g++ -DGLM_FORCE_CTOR_INIT -DHAVE_STDINT_H > -DKICAD_SCRIPTING -DKICAD_SCRIPTING_ACTION_MENU -DKICAD_SCRIPTIN > ... > > Since the compilation process had run for a while, the logfiles are > longish. If wanted I will post them here...but if someone else already > won this battle and knows how to fix it I don't want to pollute the > gentoo mailinglist with logfiles... > > > Is there a fix known for this? > > Cheers! > Meino >
I have a newer version of Kicad here so I'm not sure if your version will build here or not. This is the version, USE flags and python version as well. I'm on gcc-9.3. [ebuild R ~] sci-electronics/kicad-5.1.5-r1::gentoo USE="examples github ngspice oce openmp python -doc -occ" PYTHON_SINGLE_TARGET="python3_7 -python3_6" On the logs. Search the log for "error 1" and that is usually reasonably close to the failure. Sometimes it can go back a ways. How far back depends on settings and the package itself. Example, if you have four cores/threads in your CPU, it won't go back as far as say a 8, 12 core/thread CPU. I tend to go to error 1 and then go up about 20 lines. I have a 8 core CPU here. So, find error 1, go up several lines and start the copy there and go to the end. That makes it include the needed info in most all cases but keeps the email size reasonable. If more info is needed, someone can ask. This generally applies to any compile failure by the way. If my emerge info doesn't help, maybe the part about the log will, if no one comes along with a better idea. ;-) Dale :-) :-)
