The Thinly Sliced Developments
#11
RE: The Thinly Sliced Developments
Didbs version 0.0.2.

Git location:

https://github.com/danielhams/didbs

Direct release package:

https://github.com/danielhams/didbs/arch...0.2.tar.gz

This release adds some new packages but the main update is that it should enable running/building on hosts where there are already nekoware packages installed and in the path.

As before, you'll need a fair chunk of disk, MIPS4 CPU, 7.4.4m compilers. systune ncargs 131072.

I'm looking for feedback now - particularly if it isn't working for you.

Suggested approach (do everything as your user, I do not recommend use of root or installing into /usr/local or other existing directories. If you have to do things as root, I consider that a bug!):

* Create a directory like /usr/didbs
* chown myuser:people /usr/didbs # (have to do this as root, of course)
* gunzip 0.0.2.tar
* tar xf 0.0.2.tar
* cd didbs-0.0.2
* nedit defaultenv.vars
* Set the DIDBS_JOBS to CPU+1, or just one if RAM is < 512Mb, save, exit
* ./bootstrap.pl -p /usr/didbs/packages -b /usr/didbs/build -i /usr/didbs -v # (this sets up paths)
* ./bootstrap.pl # (This builds the stage0 pieces)
* ./bootstrap.pl # (This builds the stage1 then release packages)

Packages included here:


Code:
autoconf-2.69
automake-1.16.1
bash-3.2.57
bison-2.7.1
bzip2-1.0.6
cmake-2.8.12.2
coreutils-8.30
curl-7.61.0
diffutils-3.6
emacs-23.3
findutils-4.6.0
gawk-3.1.8
gettext-0.19.8.1
git-2.17.0
gmp-6.1.2
gnutls-3.1.5
grep-3.1
gzip-1.9
jpeg-9c
less-530
libXpm-3.5.12
libarchive-3.3.2
libiconv-1.15
libpng-1.6.34
libtool-2.4.6
libxml2-2.9.8
m4-1.4.18
make-3.82
mpfr-4.0.1
nc110
ncurses-6.1
neofetch-5.0.0
nettle-3.4
openssh-7.7p1
openssl-1.1.0h
perl-5.22.4
pkg-config-0.29.2
readline-7.0
rsync-3.1.3
rxvt-unicode-9.22
sed-4.5
tar-1.30
tcsh-6.20.00
texinfo-6.5
tiff-4.0.9
unrar
unzip60
uuid-1.6.2
vim81
wget-1.19.5
xli-2005-02-27
xosview-1.20
xz-5.2.4
zlib-1.2.11

If all successful (fingers crossed) and you want to try and use the packages it has built above, do the following (bash example):

Code:
export PATH=/usr/didbs/bin:$PATH
export LD_LIBRARYN32_PATH=/usr/didbs/lib:$LD_LIBRARYN32_PATH
export PKG_CONFIG_PATH=/usr/didbs/lib/pkgconfig:$PKG_CONFIG_PATH

For the moment the berkeley-db and python2 builds are broken, I'm not willing to support those yet.

Mr TS.
mrthinlysliced
Octane

Posts: 76
Threads: 5
Joined: May 2018
Find Reply
10-06-2018, 10:20 AM
#12
RE: The Thinly Sliced Developments
ok I gave this a shot on my 400mhz R12k o2, the stage1 ended with an error - here is what I did:


Code:
-bash-4.3$ grep PATH ~/.profile

#setup PATH
export PATH=/usr/local/bin:/usr/nekoware/bin:${PATH}
export LD_LIBRARY_PATH=/usr/local/lib:/usr/nekoware/lib
export LD_LIBRARYN32_PATH=/usr/local/lib:/usr/local/lib32:/usr/nekoware/lib
-bash-4.3$ export PATH=/usr/local/bin:/usr/didbs/bin:/usr/nekoware/bin:${PATH}
-bash-4.3$ cd /tmp
-bash-4.3$ ls -l didbs-0.0.2.tar.gz
-rw-r--r-- 1 user user 3441820 Oct 19 21:00 didbs-0.0.2.tar.gz
-bash-4.3$ gtar zxf didbs-0.0.2.tar.gz
-bash-4.3$ cd didbs-0.0.2   
-bash-4.3$ nedit defaultenv.vars #changed to CPU+1
-bash-4.3$./bootstrap.pl -p /usr/didbs/packages -b /usr/didbs/build -i /usr/didbs -v
-bash-4.3$ time ./bootstrap.pl

<snip>

Package stage0perl is now in state INSTALLED
Creating installed file: /usr/didbs/build/stage0/build/stage0perl.installed
Processed 9 packages.
Stage STAGE0 completed.
Touching stage complete file - touch /usr/didbs/build/stage0/stage.finished

real    139m14.116s
user    66m1.383s
sys     32m37.130s

-bash-4.3$ time ./bootstrap.pl

<snip>
  c99   -mips4 -L/usr/local/lib         -o vim objects/arabic.o objects/beval.o objects/buffer.o objects/blowfish.o objects/crypt.o objects/crypt_zip.o objects/dict.o objects/diff.o objects/digraph.o objects/edit.o objects/eval.o objects/evalfunc.o objects/ex_cmds.o objects/ex_cmds2.o objects/ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/farsi.o objects/fileio.o objects/fold.o objects/getchar.o objects/hardcopy.o objects/hashtab.o  objects/if_cscope.o objects/if_xcmdsrv.o objects/list.o objects/mark.o objects/memline.o objects/menu.o objects/misc1.o objects/misc2.o objects/move.o objects/mbyte.o objects/normal.o objects/ops.o objects/option.o objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/pty.o objects/quickfix.o objects/regexp.o objects/screen.o objects/search.o objects/sha256.o objects/spell.o objects/spellfile.o objects/syntax.o objects/tag.o objects/term.o objects/terminal.o objects/ui.o objects/undo.o objects/userfunc.o objects/version.o objects/window.o objects/gui.o objects/gui_motif.o objects/gui_x11.o objects/gui_beval.o objects/gui_xmdlg.o objects/gui_xmebw.o objects/term_encoding.o objects/term_keyboard.o objects/term_mouse.o objects/term_parser.o objects/term_pen.o objects/term_screen.o objects/term_state.o objects/term_unicode.o objects/term_vterm.o          objects/netbeans.o objects/channel.o  objects/charset.o objects/json.o objects/main.o objects/memfile.o objects/message.o  -lXmu -lXext -lXm -lXt -lSM -lICE -lXpm -lXt -lX11 -lw -ldl  -lm -ltermlib -lelf -lnsl -lsocket            
ld32: WARNING 84 : /usr/lib32/libw.so is not used for resolving any symbol.
ld32: WARNING 84 : /usr/lib32/libdl.so is not used for resolving any symbol.
ld32: WARNING 84 : /usr/lib32/libelf.a is not used for resolving any symbol.
ld32: WARNING 84 : /usr/lib32/libsocket.so is not used for resolving any symbol.
ld32: ERROR   33 : Unresolved text symbol "XmeRenderTableGetDefaultFont" -- 1st referenced by objects/gui_motif.o.
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "XmeDrawShadows" -- 1st referenced by objects/gui_xmebw.o.
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "XmeDrawHighlight" -- 1st referenced by objects/gui_xmebw.o.
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "XmeClearBorder" -- 1st referenced by objects/gui_xmebw.o.
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: INFO    152: Output file removed because of error.
make[1]: *** [vim] Error 2
make[1]: Leaving directory `/usr/didbs/build/vim/vim81/src'
make: *** [first] Error 2
Failed during build: No such file or directory
No such file or directory at DidbsBuilder.pm line 60.

real    353m12.735s
user    148m15.020s
sys     102m15.581s
-bash-4.3$ 


so this goes back to a post I made in the past (https://forums.irix.cc/thread-486.html) about it appears installing Maya (or something) linked an older version of libXm.so.  I figure I will just link the newer one and see what happens!  I did fix this issue with my build of vim by using the "--enable-gui=no" flag (auto is the default I believe).  I'm willing to bet I won't be the only one with this issue, but whatevs, that's what I get for installing Maya 1.0 or whatever I was doing Smile

Anyway I unlinked the older libXm.so.1 and linked the newer/correcter(?) libXm.so.2, and I'm letting it go again, I'll report back in a bunch of hours
(This post was last modified: 10-22-2018, 01:16 AM by gijoe77.)
gijoe77
Tezro

Posts: 468
Threads: 27
Joined: Jun 2018
Find Reply
10-22-2018, 01:03 AM
#13
RE: The Thinly Sliced Developments
ok, so I ran into an issue with cmake - not really sure why its failing, I also never tried to build cmake before so I never troubleshoot it or looked at it before.  Let me know what I can check to get a better idea why this is failing...


Code:
#fixed libXm.so to fix vim gui
-bash-4.3$ time ./bootstrap.pl

<snip>

--- C++ prelinker: CMakeFiles/CTestLib.dir/CTest/cmCTestTestHandler.cxx.o ---
/usr/bin/CC -DEFAULT:abi=n32:isa=mips4:proc=r10k -DEFAULT:abi=n32:isa=mips4:proc=r10k -DEFAULT:abi=n32:isa=mips4:proc=r10k -DEFAULT:abi=n32:isa=mips4:proc=r10k -DEFAULT:abi=n32:isa=mips4:proc=r10k -DCMAKE_BUILD_WITH_CMAKE -DCURL_STATICLIB -DLIBARCHIVE_STATIC -mips4 -O1 -LANG:std -Wl,-woff84 -no_auto_include -LANG:std -I/usr/didbs/build/cmake/cmake-2.8.12.2/Utilities -I/usr/didbs/build/cmake/cmake-2.8.12.2/Source -I/usr/didbs/build/cmake/cmake-2.8.12.2/Utilities/cmcompress -I/usr/didbs/build/cmake/cmake-2.8.12.2/Source/CTest -I/usr/didbs/build/cmake/cmake-2.8.12.2/Source/CursesDialog/form -c -n32 /usr/didbs/build/cmake/cmake-2.8.12.2/Source/CTest/cmCTestTestHandler.cxx -o CMakeFiles/CTestLib.dir/CTest/cmCTestTestHandler.cxx.o
[ 95%] Built target CTestLib
make: *** [all] Error 2
Failed during build: No such file or directory
No such file or directory at DidbsBuilder.pm line 60.

real    119m52.969s
user    67m43.430s
sys     23m41.033s
-bash-4.3$
looking through the logs I also saw this:

Code:
--- C++ prelinker: CMakeFiles/CTestLib.dir/cmCTest.cxx.o ---
 /usr/bin/CC -DEFAULT:abi=n32:isa=mips4:proc=r10k -DCMAKE_BUILD_WITH_CMAKE -DCURL_STATICLIB -DLIBARCHIVE_STATIC -mips4 -O1 -LANG:std -Wl,-woff84 -no_auto_include -LANG:std -I/usr/didbs/build/cmake/cmake-2.8.12.2/Utilities -I/usr/didbs/build/cmake/cmake-2.8.12.2/Source -I/usr/didbs/build/cmake/cmake-2.8.12.2/Utilities/cmcompress -I/usr/didbs/build/cmake/cmake-2.8.12.2/Source/CTest -I/usr/didbs/build/cmake/cmake-2.8.12.2/Source/CursesDialog/form -c -n32 /usr/didbs/build/cmake/cmake-2.8.12.2/Source/cmCTest.cxx -o CMakeFiles/CTestLib.dir/cmCTest.cxx.o
ld32: ERROR   33 : Unresolved text symbol "w32attron" -- 1st referenced by CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o.
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "w32attroff" -- 1st referenced by CMakeFiles/ccmake.dir/CursesDialog/cmCursesLongMessageForm.cxx.o.
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "initscr32" -- 1st referenced by CMakeFiles/ccmake.dir/CursesDialog/ccmake.cxx.o.
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "w32attrset" -- 1st referenced by CursesDialog/form/libcmForm.a(frm_driver.c.o).
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "w32insch" -- 1st referenced by CursesDialog/form/libcmForm.a(frm_driver.c.o).
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: ERROR   33 : Unresolved text symbol "w32addch" -- 1st referenced by CursesDialog/form/libcmForm.a(frm_driver.c.o).
        Use linker option -v to see when and which objects, archives and dsos are loaded.  
ld32: INFO    152: Output file removed because of error.
make[2]: *** [bin/ccmake] Error 2
make[1]: *** [Source/CMakeFiles/ccmake.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

I have the full logs if you want to look at them, let me know
(This post was last modified: 10-22-2018, 11:28 AM by gijoe77.)
gijoe77
Tezro

Posts: 468
Threads: 27
Joined: Jun 2018
Find Reply
10-22-2018, 10:59 AM
#14
RE: The Thinly Sliced Developments
Hey gijoe,

Thanks for giving the tyres a kick, it is appreciated.

RE: motif library

Can I ask what you mean when you say: "Anyway I unlinked the older libXm.so.1 and linked the newer/correcter(?) libXm.so.2"?

Do you mean you manually unlinked the system libXm.so and linked it to a newer or older version - or you have multiple libXm.so on the filesystem and you forced linking of one version?

For my curiosity let's see what libraries+versions you have - can you run:


Code:
find / -name "libXm.so*" -exec ls -lart {} \; 2>/dev/null


Here's what I see on my box (6.5.30f, 7.4.4m compilers + patches, no third party software, no manual fiddling of links or versions):


Code:
[dan@leafy ~]$ find /usr -name "libXm.so*" -exec ls -l {} \; 2>/dev/null
-r--r--r-- 1 root sys 2633452 Jul 24 14:12 /usr/lib/libXm.so.1
lrwxr-xr-x 1 root sys 17 Jul 20 22:45 /usr/lib/libXm.so -> ../lib/libXm.so.1
-r--r--r-- 1 root sys 3123944 Jul 24 14:12 /usr/lib32/libXm.so.1
-r--r--r-- 1 root sys 4290724 Jul 24 14:12 /usr/lib32/libXm.so.2
lrwxr-xr-x 1 root sys 19 Jul 20 22:45 /usr/lib32/libXm.so -> ../lib32/libXm.so.1
-r--r--r-- 1 root sys 3473432 Jun 10 18:54 /usr/lib64/libXm.so.1
-r--r--r-- 1 root sys 4770856 Jun 10 18:55 /usr/lib64/libXm.so.2
lrwxr-xr-x 1 root sys 19 Jul 20 22:45 /usr/lib64/libXm.so -> ../lib64/libXm.so.1
lrwxr-xr-x 1 root sys 20 Jun 10 17:46 /usr/Motif-1.2/lib/libXm.so -> ../../lib/libXm.so.1
lrwxr-xr-x 1 root sys 22 Jun 10 17:46 /usr/Motif-1.2/lib32/libXm.so -> ../../lib32/libXm.so.1
lrwxr-xr-x 1 root sys 22 Jun 10 17:47 /usr/Motif-1.2/lib64/libXm.so -> ../../lib64/libXm.so.1
lrwxr-xr-x 1 root sys 22 Jun 10 17:46 /usr/Motif-2.1/lib32/libXm.so -> ../../lib32/libXm.so.2
lrwxr-xr-x 1 root sys 22 Jun 10 17:47 /usr/Motif-2.1/lib64/libXm.so -> ../../lib64/libXm.so.2
-rwxr-xr-x 1 root sys 4802960 Jun 11 17:04 /usr/WorkShop/usr/lib/WorkShop/Motif/libXm.so.1
-rwxr-xr-x 1 root sys 6986400 Jul 24 14:12 /usr/WorkShop/usr/lib/WorkShop/Motif32/libXm.so.1
-rwxr-xr-x 1 root sys 4406564 Jul 24 14:12 /usr/WorkShop/usr/lib/WorkShop/6.5/Motif/libXm.so.1
-rwxr-xr-x 1 root sys 6015000 Jul 24 14:12 /usr/WorkShop/usr/lib/WorkShop/6.5/Motif32/libXm.so.1
lrwxr-xr-x 1 root sys 10 Jun 10 17:58 /usr/dt/lib32/libXm.so -> libXm.so.1
-rwxr-xr-x 1 root sys 3026752 Jul 24 14:12 /usr/dt/lib32/libXm.so.1

Indeed it might be tricky to get right if you didn't change the system libraries + it's picking up the wrong one.

RE: Issues building / checking cmake

Only think I can think of from my quick look at the logs - did you maybe run out of disk space?

Something missing from this bootstrap.pl script - once the stage0 stuff is built it should probably delete the "build" area used for those packages. I'll think about adding that to the script in future.

If you want to recover this space, you can safely "rm -rf /usr/didbs/build/stage0/build/".

For the cmake issue, I'll dive in a bit deeper tonight or tomorrow when I have a bit of time -> if you have the patience and don't mind - something like


Code:
./bootstrap.pl 1>cmakebuildissue.log 2>&1

And then pastebin/upload that file somewhere (it's probably huge, don't bring the Raion Wrath and put it here .-)

Cmake is a pain, they have their own build system and internal build bootstrapping that might make this tricky.


Thanks again,

Mr TS
mrthinlysliced
Octane

Posts: 76
Threads: 5
Joined: May 2018
Find Reply
10-22-2018, 03:54 PM
#15
RE: The Thinly Sliced Developments
for the libXm.so problem, basically I started with looking for this missing symbol and what lib it's part of:


Code:
ld32: ERROR   33 : Unresolved text symbol "XmeRenderTableGetDefaultFont" -- 1st referenced by objects/gui_motif.o

the way I went about it was like this (and this is what showed me its supposed to be located in libXm.so):

Code:
-bash-4.2$ nm -Bo /lib/*.so* > /tmp/symbols
-bash-4.2$ nm -Bo /lib32/*.so*  >> /tmp/symbols
-bash-4.2$ nm -Bo /usr/lib/*.so* >> /tmp/symbols
-bash-4.2$ nm -Bo /usr/lib32/*.so* >> /tmp/symbols
-bash-4.2$ nm -Bo /usr/local/lib/*.so*  >> /tmp/symbols
-bash-4.2$ nm -Bo /usr/local/lib32/*.so* >> /tmp/symbols
-bash-4.2$ nm -Bo /usr/nekoware/lib/*.so* >> /tmp/symbols

-bash-4.2$ mv /tmp/symbols ./symbols.so.all.txt

-bash-4.2$ grep XmeRenderTableGetDefaultFont symbols.so.all.txt
/usr/lib32/libSgm.so.2: 023af9f0 U XmeRenderTableGetDefaultFont
/usr/lib32/libXm.so.2: 00000000 U .text.XmeRenderTableGetDefaultFont
/usr/lib32/libXm.so.2: 018fd530 T XmeRenderTableGetDefaultFont
-bash-4.2$

-bash-4.2$ ls -la /usr/lib32/libXm.so*
lrwxr-xr-x 1 root sys      19 Jun  8 19:12 /usr/lib32/libXm.so -> ../lib32/libXm.so.1
-r--r--r-- 1 root sys 3126652 Apr 30 04:30 /usr/lib32/libXm.so.1
-r--r--r-- 1 root sys 4268716 Mar 15  2018 /usr/lib32/libXm.so.2

so my system is using libXm.so.1, but the missing symbol is in libXm.so.2.  The earlier post I mentioned I went into more detail, but basically I said screw it and unlinked libXm.so.1 and linked /usr/lib32/libXm.so -> ../lib32/libXm.so.2, vim gui problem solved.  I'm not sure if anything is broken yet (and I forget the elfdump command or whatever to see the lib version - had it saved in my nekochan email grrrrrr), but I at least know how to fix it.  I personally prefer the non-gui version of vim, but I digress...
Anyway here are my systems libXm's:

Code:
-bash-4.3# find / -name "libXm.so" -exec ls -lart {} \; 2>/dev/null
lrwxr-xr-x 1 root sys 17 Jun  8 18:27 /usr/lib/libXm.so -> ../lib/libXm.so.1
lrwxr-xr-x 1 root sys 19 Oct 20 15:54 /usr/lib32/libXm.so -> ../lib32/libXm.so.2
lrwxr-xr-x 1 root sys 20 Jun  8 19:27 /usr/Motif-1.2/lib/libXm.so -> ../../lib/libXm.so.1
lrwxr-xr-x 1 root sys 22 Jun  8 19:25 /usr/Motif-1.2/lib32/libXm.so -> ../../lib32/libXm.so.1
lrwxr-xr-x 1 root sys 22 Jun  8 18:28 /usr/Motif-2.1/lib32/libXm.so -> ../../lib32/libXm.so.2
-bash-4.3# 

-bash-4.3# nm -Bo /usr/Motif-1.2/lib32/libXm.so | grep XmeRenderTableGetDefaultFont
-bash-4.3# nm -Bo /usr/Motif-2.1/lib32/libXm.so | grep XmeRenderTableGetDefaultFont
/usr/Motif-2.1/lib32/libXm.so: 00000000 U .text.XmeRenderTableGetDefaultFont
/usr/Motif-2.1/lib32/libXm.so: 018fd530 T XmeRenderTableGetDefaultFont
-bash-4.3# 

seems that symbol is also in the the Motif-2.1 libs, interesting.  I didn't think to search for all copies of libXm.so.
>RE: Issues building / checking cmake
>Only think I can think of from my quick look at the logs - did you maybe run out of disk space?

Def didn't run out of space, I have a 500GB SSD in this little slow poke :Smile I'm currently sitting on ~300GB free.

I'll run "./bootstrap.pl 1>cmakebuildissue.log 2>&1" and get the file to you in a few hours
gijoe77
Tezro

Posts: 468
Threads: 27
Joined: Jun 2018
Find Reply
10-22-2018, 05:02 PM
#16
RE: The Thinly Sliced Developments
ok here is what I did:


Code:
-bash-4.3$ time ./bootstrap.pl 1>cmakebuildissue.log 2>&1

real    103m15.449s
user    59m32.977s
sys     18m1.624s
-bash-4.3$ nedit cmakebuildissue.log
-bash-4.3$ ls -lh cmakebuildissue.log
-rw-r--r-- 1 develop user 450K Oct 21 09:41 cmakebuildissue.log
-bash-4.3$ xz cmakebuildissue.log
-bash-4.3$ ls -lh cmakebuildissue.log*
-rw-r--r-- 1 develop user 23K Oct 21 09:41 cmakebuildissue.log.xz
-bash-4.3$ pwd
/tmp/didbs-0.0.2
-bash-4.3$ 

I attached the log file here, its tiny!!


Attached Files
.tar cmakebuildissue.log.xz.tar Size: 30 KB  Downloads: 12
(This post was last modified: 10-23-2018, 01:43 AM by gijoe77.)
gijoe77
Tezro

Posts: 468
Threads: 27
Joined: Jun 2018
Find Reply
10-23-2018, 01:40 AM
#17
RE: The Thinly Sliced Developments
Thanks gijoe,

I can't seem to do anything with that I'm afraid. Mind placing it somewhere other than an attachment?

Don't know if you have a github account, one option is to add it to this:

https://github.com/danielhams/didbs/issues/1


Code:
[dan@workhorse Temp]$ ls -alrt ./cmakebuildissue.log.xz.tar
-rw-r--r-- 1 dan dan 30720 Oct 23 11:59 ./cmakebuildissue.log.xz.tar

[dan@workhorse Temp]$ unxz cmakebuildissue.log.xz.tar
unxz: cmakebuildissue.log.xz.tar: File format not recognized
[dan@workhorse Temp]$ tar xf cmakebuildissue.log.xz.tar
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
mrthinlysliced
Octane

Posts: 76
Threads: 5
Joined: May 2018
Find Reply
10-23-2018, 11:04 AM
#18
RE: The Thinly Sliced Developments
(10-23-2018, 11:04 AM)mrthinlysliced Wrote:  Thanks gijoe,

I can't seem to do anything with that I'm afraid. Mind placing it somewhere other than an attachment?

Don't know if you have a github account, one option is to add it to this:

https://github.com/danielhams/didbs/issues/1


Code:
[dan@workhorse Temp]$ ls -alrt ./cmakebuildissue.log.xz.tar
-rw-r--r-- 1 dan dan 30720 Oct 23 11:59 ./cmakebuildissue.log.xz.tar

[dan@workhorse Temp]$ unxz cmakebuildissue.log.xz.tar
unxz: cmakebuildissue.log.xz.tar: File format not recognized
[dan@workhorse Temp]$ tar xf cmakebuildissue.log.xz.tar
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

I'm sort of baffled how github works, but I should probably make an account and figure it all out soon... But for now let me know if this works:

http://www.mediafire.com/file/9uodvmkn4s...og.xz/file
gijoe77
Tezro

Posts: 468
Threads: 27
Joined: Jun 2018
Find Reply
10-23-2018, 02:17 PM
#19
RE: The Thinly Sliced Developments
Thanks, got it!

I'll take a peek.
mrthinlysliced
Octane

Posts: 76
Threads: 5
Joined: May 2018
Find Reply
10-23-2018, 04:51 PM
#20
RE: The Thinly Sliced Developments
Hey GiJoe,

So a few issues I see from that log:

* didbs doesn't properly flush it's output so the "didbs logging" is at the end of a unified log -> I'll fix that at some point

* didbs should internally suppress user set env-vars like LD_LIBRARY_PATH and LD_LIBRARYN64_PATH for correctness -> will be done (add them to suppressenv.vars)

* cmake itself is rather naughty in ignoring the includes + paths you ask it to use (CPPFLAGS or CFLAGS, LD_LIBRARYN32_PATH etc) and goes and finds things under /usr/local/lib -> I have to see if there's a way to stop it hunting around on it's own - otherwise I can't be sure what it's linking against. Even with --no-system-libs it's off checking /usr/local/lib ....)

* getting cmake to link against ncurses doesn't work - so I now see the missing symbols you see -> I'll have to check if there's any special flags needed to get cmake to use ncurses. There seems to be flags that might be able to get this working, didn't have any luck last night.

So - no "fix" for it yet, but it has given me some leads and I'll reproduce your issues and look into it.

Cheers

Mr TS
mrthinlysliced
Octane

Posts: 76
Threads: 5
Joined: May 2018
Find Reply
10-24-2018, 10:46 AM


Forum Jump:


Users browsing this thread: 1 Guest(s)