Hi Nicholas,

On 25 Jul 17 15:49, Nicholas Boel wrote to Wilfred van Velzen:
  about: "Status check":

 WvV>> Arm... Interesting! 

 WvV>> I'm already compiling for a 64 bit target. But I don't know what
 WvV>> other differences there might exist between the arm and intel
 WvV>> architectures that might cause problems?

 NB> I don't know exactly, but husky stuff, golded, and other things all
 NB> compiled without issue. I do believe there was a small issue or two that
 NB> was fixed early on with Synchronet, and I had to contact a couple authors
 NB> with my compile errors on a couple other pieces of software.

It's already compiling with a current gnu compiler, without errors and
warnings. So I don't expect many of those.

 NB> I'm guessing if there's a lot of intel specific code in it, the more
 NB> problems there will be. 

I try not to write code that's specific for any target. But it still contains a
 lot of decades old legacy code I never touched. So you never know what hidden
problems are lurking... 

 WvV>> Does this machine have a gui environment? (So you could use
 WvV>> codeblocks)

 NB> Not at the moment, and I wasn't really planning on it. However, if it were
 NB> completely necessary, (as in to compile on ARM because you don't have
 NB> access to it) it's not hard at all to install xorg and fluxbox.

 NB> Let's just say I would much rather use Makefiles, but if that is not
 NB> possible at the moment.. I can suffer a bit. 

It shouldn't be too difficult to create the make files, but I don't know when
they will be finished, so if you want to start compiling today, that's your
only option. 

Wilfred.

--- FMail-W32 2.0.1.4
 * Origin:  point@work  (2:280/464.112)