Before I start getting back into my AmigaOS development, I wanted to amalgamate all of my projects together into one place on my QNAP NAS Server, whether they be Amiga, Mac, Windows or Web based projects.

This way they're all backed up at regular intervals and I can access source code over the network and if need be, over the internet via SVN.

Now, with everything now in place, I'm trying to compile a simple AmigaOS project over a network share which I've mounted with SMBFS on OS4.1 Update 2.

However, I've come across a problem with GCC which spurts out the following if I try to compile:


Assember messages:
Fatal Error: can't write test.o: No space left on device
Fatal Error: can't close test.o: No such file or directory


So, there's 891Gb left on the server, which leads me to believe the system (either GCC or SMBFS) is falling over because it's over 4Gb.

Does anyone have any experience of dealing with such a situation or am I stuck to checking out over SVN on my local network and recommitting when done?

Does SMBFS need a re-write for OS4.1 to use larger file systems or is GCC at fault here?

Thanks in advance for any help!

Cheers,
Daniel

_________________
This fire is burnin' and it's out of control
It's not a problem you can stop, It's rock n' roll - GN'F'N'R

@Slash

Can you write other data? I.e. Is your CIFS export configured correctly?

_________________
Sam440ep-flex 733 MHz/1 GB RAM/Radeon 9250/AmigaOS4.1 Update 2
borked A1200/Blizzard1260+SCSI-IV/Z4+MediatorZIV/Deneb/Voodoo3/CatweaselMk3
more borked A1200/MBX1200z/Indivision
A500/clockport/RRNet
A600/A603

@Slash

That looks exactly like what happens on Linux when I try and compile!

But in that case I only had 500MB left IIRC. Check if you can see how much free space it thinks there is.

Another thing is where the /tmp directory is located. And how much space it has to offer. Perhaps try and copy a file there of a sizeable portion and see what happens.

It needs to enough space in /tmp to store files while compiling.

OK, I've figured out why it was outputting these messages, it was all down to including the debug flag:

-gstabs

Commenting this out will result in GCC working correctly as expected over the network and shared linux drive.

Anyone know why that would be?

Daniel

_________________
This fire is burnin' and it's out of control
It's not a problem you can stop, It's rock n' roll - GN'F'N'R

@Slash

What step did it fail, compile or link? -gstabs is known to dramatically increase the size of all the binaries with all the added debug data, so that is likely what is causing something to fail at some point.

@swoodall

It failed during the compile stage, even with a simple program such as:

int main(void)
{
return 1;
}

I'm having further problems during linking now though, with SMBFS crashing but I don't suspect GCC for those failings.

_________________
This fire is burnin' and it's out of control
It's not a problem you can stop, It's rock n' roll - GN'F'N'R