Re: Problems Building lang/go120 - /tmp full?

[Brad Spencer <brad%anduin.eldar.org@localhost>]

yancm%sdf.org@localhost writes:

>> yancm%sdf.org@localhost writes:
>>

[snip]

>> # setenv TMPDIR /var/tmp
>> # cd /usr/pkgsrc/lang/go
>> # make
>>
>> and it is in /etc/mk.conf
>>
>> TMPDIR=/var/tmp
>>
>> In a lot of ways, this really isn't much different than what the C
>> compilers do, just look in /tmp or /var/tmp while compiling stuff you
>> will see files ending in .s and the like there, except that go generates
>> a much larger intermediate set of files when it compiles itself.  I have
>> run /tmp out of space, when it is set to be very small, even when using
>> gcc.
>>
>>
>> Unrelated to this, probably, I also use MAKE_JOBS=1 in /etc/mk.conf
>> being rather pessimistic about some things.
>>
>>
>> Simular operations may also be needed when compiling rust from source.
>
> Adding setenv TMPDIR=/usr/pkgsrc/tmp (in my case) worked.
> I've built go117, 118, 119, rust and gcc many times before, without this
> issue... my /tmp is currently limited to 256M... but maybe go120 really
> needs more for some reason...
>
> Thank you for your help!
> --gene


Good..  glad it worked for you...  I don't remember exactly, but I think
go wants something north of 1GB to 2GB of intermediate temp space and I
have vague memories of rust wanting something simular.  Everything
around here has /tmp as its own filesystem and is never allowed to be
anything close to that large (much less than 256MB in most cases).  I
have not noticed GCC, or at least the older GCC, requiring anything like
this.

On a simular topic, there are packages out there that will require a lot
of PKGSRC work space.  Those that I know of are qemu, rust from source,
and wip/minio and I am sure that there are others like firefox and the
like.  The rust-from-source build, in particular, will want 20GB at
least of space for PKGSRC work.  It may be helpful to remember that
WRKOBJDIR can be set in /etc/mk.conf to put the work directories
someplace other than /usr/pkgsrc.  This location can be clean out,
i.e. newfs'ed for example, or zfs snapshot'ed when empty and rolled
back, from time to time during a bulk build session.



-- 
Brad Spencer - brad%anduin.eldar.org@localhost - KC8VKS - http://anduin.eldar.org