(10-03-2018, 11:13 AM)gijoe77 Wrote: BTW here is my build enviroment
Code:
export CC=gcc
export CXX=g++
export CFLAGS="-std=gnu99 -g -O1 -mips4"
export CXXFLAGS="-g -O1 -mips4"
export CPPFLAGS="-I/usr/local/include -I/usr/local/include/openssl -I/usr/local/include/ncurses -I/usr/nekoware/include"
export LDFLAGS=" -L/usr/local/lib -L/usr/local/lib32 -L/usr/nekoware/lib -lssl -lcrypt -lcurses -ltermcap"
export LD_LIBRARYN32_PATH=/usr/local/lib:/usr/local/lib32:/usr/nekoware/lib
./configure --prefix=/usr/local
gmake
Hey gijoe,
That's looking in the right direction, but you can streamline it a bit (and be more correct).
For the "CPPFLAGS" - you should "-I" include the root of the directory where include files will be looked for - in the case of openssl and ncurses, packages normally try and
Code:
#include <openssl/ssh.h>
so it's not necessary to include each individual subdirectory, only each root where includes are found.
So I'd tweak the CPPFLAGS to be:
Code:
export CPPFLAGS="-I/usr/local/include -I/usr/nekoware/include"
For the LDFLAGS you could explicitly include the libraries with "-l" parameters - but the autoconf "configure" script will normally figure out which libraries need to be pulled in.
So I'd tweak that to be:
Code:
export LDFLAGS=" -L/usr/local/lib -L/usr/local/lib32 -L/usr/nekoware/lib"
This _does_ mostly only apply to things using autoconf - for projects with raw makefile or their own way of configuring/setting up (looking at you, perl), you may indeed need to be specific about adding libraries in the LDFLAGS or by editing makefiles.
One other variable that can help out in discovering libraries + package locations - PKG_CONFIG_PATH (from pkgconfig).
Given what you've written above, I'd set it something like this:
Code:
export PKG_CONFIG_PATH="/usr/local/lib/pkgconfig:/usr/nekoware/lib/pkgconfig"
I realise this is quite a learning curve .-)
Hopefully this week I'll have a new release of "didbs" (this fixes issues running on machines where nekoware already installed) - I'd like to ask you to be a guinea pig for it (just run + report errors) - my goal is then I can point you at didbs and say "run didbs with these flags to see what environment I set up for package X".
Still a bit of work to do there for me before we are there, but with your help maybe I can learn enough to start on an irisware bootstrap proof-of-concept (I haven't forgotten Raion!).
Cheers