Bug 885474] make bails with *** INTERNAL: readdir: Bad file descriptor

I was looking for this bug on make project tracker, but couldn't find it. Is this a generic make bug or is it distro-specific to Fedora? https://bugzilla.redhat.com/show_bug.cgi?id=885474 Thanks, -Philip ___ Bug-make mailing list Bug-make@gnu.org htt

Re: Detecting parallel builds

On 4/9/11 5:48 PM, David Boyce wrote: > On Sat, Apr 9, 2011 at 2:32 PM, Philip Prindeville > wrote: >> [philipp@builder ~/openwrt2]$ make -j5 -f /tmp/Makefile >> MAKEFLAGS= >> MFLAGS= >> MAKE=make >> PBUILD= >> MAKEFLAGS=w >> MFLAGS=-w >> M

Re: Detecting parallel builds

On 4/9/11 5:48 PM, David Boyce wrote: > On Sat, Apr 9, 2011 at 2:32 PM, Philip Prindeville > wrote: >> [philipp@builder ~/openwrt2]$ make -j5 -f /tmp/Makefile >> MAKEFLAGS= >> MFLAGS= >> MAKE=make >> PBUILD= >> MAKEFLAGS=w >> MFLAGS=-w >> M

Re: Detecting parallel builds

On 4/9/11 5:44 AM, David Boyce wrote: > On Fri, Apr 8, 2011 at 7:58 PM, Philip Prindeville > wrote: >> Didn't hear back, so I assume there is no easy way to detect (currently) a >> parallel build. > > There was a response by Edward Welbourne - didn't y

Re: Detecting parallel builds

Hi, Didn't hear back, so I assume there is no easy way to detect (currently) a parallel build. With that in mind, could an enhancement be added to facilitate this? Thanks, -Philip On 3/27/11 5:59 PM, Philip Prindeville wrote: > Hi. > > I looked for an answer to this but came

Detecting parallel builds

Hi. I looked for an answer to this but came up short. I'm trying to find an easy way to detect inside of a makefile if we're running as a parallel make or not. If we are, then I want to turn off "progress meters" on 'wget' because they end up getting interlaced with everything else's output

Re: Override... but not really

On 8/9/10 6:07 PM, Paul Smith wrote: On Mon, 2010-08-09 at 14:00 -0700, Philip Prindeville wrote: The offender I'm staring at right now is ppp-2.4.5. I'll try to autoconfiscate it (autoconf + obsfucate?) later. I wasn't suggesting you should autoconfiscate it. I was

Re: Override... but not really

On 8/9/10 1:46 PM, Paul Smith wrote: On Mon, 2010-08-09 at 12:41 -0700, Philip Prindeville wrote: Alas much of this is beyond my control, and it's not a single project: it's a Linux distro having a couple of hundred projects, many of which have several directories deep of makefile ne

Re: Override... but not really

On 8/9/10 12:12 PM, Paul Smith wrote: On Mon, 2010-08-09 at 11:54 -0700, Philip Prindeville wrote: I guess I was thinking that variables are exported between makes the same way that environments variables are passed between processes. Well, certainly variables CAN be exported by make (see the

Re: Override... but not really

On 8/9/10 10:25 AM, Paul Smith wrote: On Mon, 2010-08-09 at 10:00 -0700, Philip Prindeville wrote: Is this expected behavior? Yes. $ cat makefile1 override CFLAGS+=-DB $(info makefile1: CFLAGS=$(CFLAGS)) all: make -f makefile2 $ cat makefile2 $(info makefile2: CFLAGS=$(CFLAGS

Re: Override... but not really

rting itself makes this a little tricky. Looking for some insight. Thanks. On 8/9/10 10:00 AM, Philip Prindeville wrote: Is this expected behavior? $ cat makefile1 override CFLAGS+=-DB $(info makefile1: CFLAGS=$(CFLAGS)) all: make -f makefile2 $ cat makefile2 $(info makefile2: CFLAGS=$(

Override... but not really

Is this expected behavior? $ cat makefile1 override CFLAGS+=-DB $(info makefile1: CFLAGS=$(CFLAGS)) all: make -f makefile2 $ cat makefile2 $(info makefile2: CFLAGS=$(CFLAGS)) override CFLAGS+=-DC $(info makefile2: CFLAGS=$(CFLAGS)) all: @echo foo $ make -f makefile1 CFLAGS=