gcc - ld: final link failed: No space left on device

[DeIM]

I'm trying compile gcc and I get

Code: Select all

/usr/lib/gcc/i686-pc-linux-gnu/10.3.0/../../../../i686-pc-linux-gnu/bin/ld: final link failed: No space left on device

I thought it meant space in /vat/tmp/portage so I mounted big enough space to it (hundreds of GiB)
but no change.

So question is where does linking stores data?

Thanks in advance

[DaggyStyle]

I'm trying compile gcc and I get

Code: Select all

/usr/lib/gcc/i686-pc-linux-gnu/10.3.0/../../../../i686-pc-linux-gnu/bin/ld: final link failed: No space left on device

I thought it meant space in /vat/tmp/portage so I mounted big enough space to it (hundreds of GiB)
but no change.

So question is where does linking stores data?

Thanks in advance

check if there are enough inodes in the fs

[DeIM]

I used nfs mount to tmpfs and after "No space problem" nfs mount to btrfs disk (620G of free space).
Previous emerge of gcc worked fine with /var/tmp/portage on tmpfs over nfs even with ~7.5G space on it.
For the record, this is sys-devel/gcc-10.3.0-r2 stable emerge.

[DaggyStyle]

I used nfs mount to tmpfs and after "No space problem" nfs mount to btrfs disk (620G of free space).
Previous emerge of gcc worked fine with /var/tmp/portage on tmpfs over nfs even with ~7.5G space on it.
For the record, this is sys-devel/gcc-10.3.0-r2 stable emerge.

why are you using tmpfs over nfs?
I'd recommend using local cold storage

[DeIM]

Thanks for reply.
Particularly this PC is older 32bit Eeepc. I switched HDD for 30GB SDD, changed RAM for 2GB and using nfs mount to local server (portage and /var/tmp/portage). I just want to maximally defend SSD from degrading. Build time is no concern.
It just worked before and I don't know what device could be out of space.

[mike155]

The message

Code: Select all

final link failed: No space left on device

does not necessarily mean that there's no space. It probably just means: something went wrong.

If you really want to know what is going on: build the package with "ebuild compile". After the error message, run the ebuild command again, but with "strace -f". Find the error in the strace output.

On the other hand, DaggyStlye is right. It's probably not the smartest idea to mount an NFS volume to "/var/tmp/portage". Any chance to use local disk space?

[DaggyStyle]

external usb drives are cheep today, if you can afford one, I'd recommend
another possibility is to setup a binhost

[Irre]

I'm trying compile gcc and I get

Code: Select all

/usr/lib/gcc/i686-pc-linux-gnu/10.3.0/../../../../i686-pc-linux-gnu/bin/ld: final link failed: No space left on device

I thought it meant space in /vat/tmp/portage so I mounted big enough space to it (hundreds of GiB)
but no change.

So question is where does linking stores data?

Thanks in advance

attach /var/tmp to a device not /vat/ ...

[DeIM]

attach /var/tmp to a device not /vat/ ...

Sorry it's just typo /vat/ doesn't exists.

But after attaching external HDD it completed wo errors.
I still doubt why other ebuilds could be compiled that way - even previous versions of gcc.

Are there any concern about not to mount /var/tmp/portage over nfs?
Is it just possibility of network problems or something else - like file locking?