[csw-maintainers] zeromq build failing on i386: Too many open files (signaler.cpp:300)

Dagobert Michelsen dam at opencsw.org
Thu Jul 5 11:31:04 CEST 2012


Hi Romeo,

Am 05.07.2012 um 10:37 schrieb Romeo Theriault:
> On Wed, Jun 20, 2012 at 8:12 PM, Dagobert Michelsen <dam at opencsw.org> wrote:
>> Does this mean the build depends on your home directory? That would be bad.
>> I suggest using
>>  file/bash_profile
>>  DISTFILES += bash_profile
>>  BASH_ENV=$(WORKSRC)/bash_profile
>> to make the recipe portable.
> 
> I'm just getting back to this after a vacation. I found that I needed
> to use the $(WORKDIR) variable to get the correct directory containing
> the file I need to source. So I'm doing this in my Makefile:
> 
> DISTFILES  += set-ulimit-for-build-test
> EXTRA_TEST_ENV += BASH_ENV=$(WORKDIR)/set-ulimit-for-build-test
> 
> So the BASH_ENV is now being expanded like so, during the testing phase:
> 
> BASH_ENV=work/solaris9-i386/build-isa-i386/set-ulimit-for-build-test
> 
> The problem is that bash cannot find the 'set-ulimit-for-build-test'
> file since it doesn't know where the "work" directory is. If I set
> this instead:
> 
> EXTRA_TEST_ENV +=
> BASH_ENV=~/opencsw/zeromq/trunk/$(WORKDIR)/set-ulimit-for-build-test
> 
> it works as expected but I'm having to hard-code the
> "~/opencsw/zeromq/trunk/" part of the path.
> 
> Do you have any suggestions on how I might be able to get this to work
> without hard-coding "~/opencsw/zeromq/trunk/" ?

Try
  EXTRA_TEST_ENV += BASH_ENV=$(abspath $(WORKDIR)/set-ulimit-for-build-test)


Best regards

  -- Dago



-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896



More information about the maintainers mailing list