@deadwood

Whilst compiling on native 64-bit AROS, I encountered a compilation error; see the screenshot for ‘ftp_main.o’

This error does not appear when I compile the source code on 32-bit AROS!

midwan, the author of Dopus5 v101, told me that he does not encounter this error; he follows your instructions for compiling on Linux

I don't see the error on this screenshot - the outpus is just a warning. You'd have to capture to a file the complete output of compiling ftp_main.c and share that output.

I’m not quite sure what I’m supposed to do, what do you mean by ‘capture’?
The problem is that after that message, the compilation stops and the subsequent source files aren’t compiled!

Question: why are the Dopus5 builds I’ve compiled much larger than those compiled by midwan?

Why can't you just comment out the debug.h include if it's only used for debugging. Maybe it's not needed.

@AMIGASYSTEM

Either mark all the text in the AROSShell and copy it to file or find some way to redirect what GCC is printing to file (I don't know how to do it in AROSShell).

Size -> you might be compiling with debug symbols. Check your makefile if the '-g' switch is added to GCC command line.

The new version is out also for AROS

https://www.amiga...49-EN.html

@Amiwell

That isn’t a new version; it’s the same Dopus5 v101 version that I posted links to a few days ago on GitHub, where the developer is updating it to fix some issues reported by users, including the 64-bit version of AROS.

--- Italiano --

Quella non è una nuova versione, è la stessa versione Dopus5 v101 che ho postato i link giorni fa da GitUub, dove lo sviluppatore sta aggiornando fixando alcuni problemi riscontrati dagli utenti inclusa la versione 64Bit di AROS.

https://github.co...us5/issues

Ftp wont compile some of the tcp includes where removed (you can grab them from latest nighty and than it should compile), To to catche errors or warning log file from aros shell , fallow the example
Goto dopus5 sourcecode folder where makefile is than bingup cli/shell prompt type

sh than enter
make >ram:build_log.txt 2>&1 than enter
or
make aros >ram:build_log.txt 2>&1 than enter

you should be able to grab the log file from ram:

ok

Unfortunately, I haven’t been able to resolve the ‘ftp_main.o’ error or produce smaller binaries, so I’ll wait for the official Midwan builds. Thanks for your help.

@deadwood ‘

I tried compiling the Dopus5 source code using AROS One 64-bit v1.0; with this distribution, the error ‘ftp_main. o" no longer appeared; the compilation was almost complete, ending with an error (perhaps just a message), but all the Dopus5 files were successfully compiled, much as had happened with the 32-bit version of AROS One.

Now I don’t know if there have been any particular changes in the recent Development folder or if something is missing.

As for the size of the binaries, even when adding the -g parameter to GCC, the size of the binaries is double that of the binaries compiled by midwan!

In either U2 or U3 I hid some of the network headers that I considered private. Would be interested to know which header you need for the ftp_main.c.

I’ve no idea where to find the required network headers; if you could give me the names and paths, I could run a few tests. I’ve attached the source code for ftp-module, perhaps we can work out what it’s looking for!