Issues at understanding the "how to"

[rmleonard]

I believe I have all of the pieces to make this work, but I don't seem to have enough understanding of what all of the pieces are.... (which translates to.... I can't get it to compile)

I have the basic compiler call methodology working....(I can cross-compile/build a helloworld app that runs on the Seagate central)

I can follow directions well enough to compile/build 'midnite commander' for the central...
http://network.lamantinclub.com/61-how-to-build-mc-midnight-commander-for-nas-seagate-central

What I want to do is build nfs4 server for the device....

I've found the 4 bin files needed to create a nfs3 server ... and I have it working fine...
I am fairly certain that nfs4 should run fine (I have several "seagate go flex" units running debian Jessie serving up nfs4 shares without a problem.)

So, back to this issue,
I have the Seagate tarball of sources...
I have the scripts from here...

On my Linux boxen-
$ uname -a
Linux homeserver 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

running 16.04.2 ubuntu

My working "project" directory is
~/Builds/armel/prj_x
This is the value for 'pwd' in the toolchain_configuration script

At the moment
arm-linux-gnueabi-gcc points at arm-linux-gnueabi-gcc-5 (4.7 is also installed)

What should my src directory look like and what _should_I have actually extracted from the Seagate tarball?

Thank you!
Rich Leonard
rmleonard at gmail

[harlequin]

Hey there,

inside the script open-seagate-central/toolchain/maketoolchain.sh are messages implemented which are showing you which packages have to be extracted.

Just try to run the script and look into the output