[bug #63330] readdir() error in 4.4 on Solaris 8

Follow-up Comment #5, bug #63330 (project make): That's certainly disturbing and I would very much like to figure out what's wrong. Just to be sure I built and ran the GNU Make regression tests on an NFS-mounted partition and it worked fine, but this was a GNU/Linux client and a NetApp NFS

Re: [bug #63330] readdir() error in 4.4 on Solaris 8

Is make being built with -D_FILE_OFFSET_BITS=64 to use the large-file APIs? If not, then maybe the problem is an inode number that doesn't fit in the old 32-bit ino_t that some struct dirent's were stuck with. Check the output of "ls -l -i" (note the -i option!) to see if there's an inode number

[bug #63330] readdir() error in 4.4 on Solaris 8

Follow-up Comment #4, bug #63330 (project make): It looks like this is somehow related to NFS. I was running the newly-generated make in the root of the source tree, and on an NFS mounted directory it fails immediately. If I copy the tree to a local directory I have no problems.

Re: 4.4: embeds volatile information in MAKEFLAGS

Paul Smith wrote in <05f924d1e2c372b7321b6c3b1863ff864cc433df.ca...@gnu.org>: |On Mon, 2022-11-07 at 21:55 +0100, Steffen Nurpmeso wrote: |>  |However, I don't think that any changes being made for GNU Make 4.4 |>  |compatibility, would render the makefile unusable with GNU Make 4.3 |>  

[bug #63333] Keep running w/o output sync on temp file failure.

URL: Summary: Keep running w/o output sync on temp file failure. Project: make Submitter: dgoncharov Submitted: Mon 07 Nov 2022 10:49:05 PM UTC Severity: 3 - Normal

[bug #63333] Keep running w/o output sync on temp file failure.

Follow-up Comment #3, bug #6 (project make): Thanks Dmitry. I already implemented a change and a test for this but I'll check and see what you've got here too. ___ Reply to this item at:

[bug #63333] Keep running w/o output sync on temp file failure.

Follow-up Comment #2, bug #6 (project make): This patch causes make to print an error message and keep running without output sync on a temp file failure. ___ Reply to this item at:

[bug #63333] Keep running w/o output sync on temp file failure.

Additional Item Attachment, bug #6 (project make): File name: sv6_test.diff Size:2 KB File name: sv6_fix.diff Size:5 KB

[bug #63333] Keep running w/o output sync on temp file failure.

Follow-up Comment #1, bug #6 (project make): Make treats inability to create a temporary file for output sync as fatal and aborts the build. $ cat makefile all:; $(info hello, world) $ mkdir temp $ chmod -w temp $ # this is make from master $ TMPDIR=temp ~/src/make/m64/make -Orecurse

Re: 4.4: embeds volatile information in MAKEFLAGS

On Mon, 2022-11-07 at 14:59 -0500, Paul Smith wrote: > I agree that we should drop down to "jobserver unavailable" here > rather than having a fatal error. I have a change that implements this now.

[bug #63307] make 4.4 passes ignored SIGPIPE on to children

Follow-up Comment #12, bug #63307 (project make): > Should inability to write to stdout cause make to die abnormally? I had the same thought but oddly, I can't seem to generate a use-case where make behaves differently with this FATAL_SIG set for SIGPIPE. It appears that make still performs the

[bug #63307] make 4.4 passes ignored SIGPIPE on to children

Follow-up Comment #11, bug #63307 (project make): [comment #10 comment #10:] > I'm not sure how using a semaphore helps here. We would still have to clean up the semaphore with sem_unlink(). indeed. > The main goal of that change was to allow our cleanup operations to proceed even when SIGPIPE

Re: 4.4: embeds volatile information in MAKEFLAGS

On Mon, 2022-11-07 at 21:55 +0100, Steffen Nurpmeso wrote: >  |However, I don't think that any changes being made for GNU Make 4.4 >  |compatibility, would render the makefile unusable with GNU Make 4.3 >  |(unless they start actually using the new features like the new >  |functions, but I don't

Re: 4.4: embeds volatile information in MAKEFLAGS

Paul Smith wrote in : |On Mon, 2022-11-07 at 21:24 +0100, Steffen Nurpmeso wrote: |> What would interest me now.  Will there be GNU make 4.4.1? |> (On the left and right i see quite some changes of projects to |> become compatible with GNU make 4.4 though, CRUX Linux imported |> a pretty

Re: 4.4: embeds volatile information in MAKEFLAGS

On Mon, 2022-11-07 at 21:24 +0100, Steffen Nurpmeso wrote: > What would interest me now.  Will there be GNU make 4.4.1? > (On the left and right i see quite some changes of projects to > become compatible with GNU make 4.4 though, CRUX Linux imported > a pretty lengthy glibc patch, and on the

Re: 4.4: embeds volatile information in MAKEFLAGS

Hello Paul Smith. Paul Smith wrote in <07e283aabbe6e01cc56a8d9349257ab2f125f114.ca...@gnu.org>: |On Mon, 2022-11-07 at 20:32 +0100, Steffen Nurpmeso wrote: |> mkdir /tmp/t |> cd /tmp/t |> cat > makefile <<'EOT' |> .NOTPARALLEL: |> .WAIT: # Luckily BSD make supports specifying this as

Re: 4.4: embeds volatile information in MAKEFLAGS

On Mon, 2022-11-07 at 20:32 +0100, Steffen Nurpmeso wrote: > mkdir /tmp/t > cd /tmp/t > cat > makefile <<'EOT' > .NOTPARALLEL: > .WAIT: # Luckily BSD make supports specifying this as target, too > config: > @{ echo MAKE=\"$(MAKE)\";echo MAKEFLAGS=\"$(MAKEFLAGS)\"; } > > ./au;echo config >

Re: 4.4: embeds volatile information in MAKEFLAGS

Hello. Steffen Nurpmeso wrote in <20221105231048.8w3mb%stef...@sdaoden.eu>: |Steffen Nurpmeso wrote in | <20221105230326.qijdr%stef...@sdaoden.eu>: ||Dmitry Goncharov wrote in || : |||On Sat, Nov 5, 2022 at 6:24 PM Steffen Nurpmeso \ |||wrote: |||> make[1]: *** Cannot open jobserver

[bug #63330] readdir() error in 4.4 on Solaris 8

Follow-up Comment #3, bug #63330 (project make): It's very strange because the code in 4.4 dir.c was changed in many places (to introduce directory cache invalidation) but this specific code related to readdir() is the same as in 4.3. I think we will need to either get a repro case (even if it

[bug #63330] readdir() error in 4.4 on Solaris 8

Follow-up Comment #2, bug #63330 (project make): Oh, actually that can't be it. I forgot that ENULLLOOP() sets errno=0 before it tries the command. Hm. Well, POSIX does allow EOVERFLOW to be returned by readdir() (that's the error you see). So maybe there's something about the directory it's

[bug #63330] readdir() error in 4.4 on Solaris 8

Follow-up Comment #1, bug #63330 (project make): Hm. Maybe on Solaris readdir() doesn't reset errno? In src/dir.c you'll find this code: ENULLLOOP (d, readdir (dir->dirstream)); if (d == 0) { if (errno) pfatal_with_name ("INTERNAL: readdir");

[bug #63330] readdir() error in 4.4 on Solaris 8

URL: Summary: readdir() error in 4.4 on Solaris 8 Project: make Submitter: None Submitted: Mon 07 Nov 2022 03:37:45 PM UTC Severity: 3 - Normal Item Group: Bug

Re: GNU Make 4.4 released!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi/2. Paul Smith wrote: > > > > GNU make is a tool which controls the generation of executables and > other non-source files of a program from the program's source > files. > >

Re: GNU Make 4.4 released!

On Mon, 2022-11-07 at 20:40 +0900, KO Myung-Hun wrote: > May I take over OS/2 port maintenance ? > For this, what should I do ? 1. Subscribe to this mailing list and announce your intention to work on this (to prevent possible duplication of effort). 2. Download the latest release