This was a fresh validation run, so make distclean won’t do it. And deleting the file makes no difference. For what it’s worth, I ran with CPUS=1 (instead of my usual CPUS=32) to avoid threading problems. Any other suggestions? Thanks! Richard

On Mar 13, 2017, at 10:07 AM, Ben Gamari <ben@smart-cactus.org> wrote:

Richard Eisenberg <rae@cs.brynmawr.edu> writes:

...

Hi devs,

When I try validating my patch, validation fails with

...

... Registering library for ghc-prim-0.5.0.0.. ghc-cabal: '/home/rae/ghc/ghc-valid/bindisttest/install dir/lib/ghc-8.3.20170312/bin/ghc-pkg' exited with an error: ghc-pkg: Couldn't open database /home/rae/ghc/ghc-valid/bindisttest/install dir/lib/ghc-8.3.20170312/package.conf.d for modification: {handle: /home/rae/ghc/ghc-valid/bindisttest/install dir/lib/ghc-8.3.20170312/package.conf.d/package.cache.lock}: hLock: invalid argument (Bad file descriptor) make[3]: *** [ghc.mk:990: install_packages] Error 1 make[2]: *** [Makefile:51: install] Error 2 make[1]: *** [bindisttest/ghc.mk:33: test_bindist] Error 2 make: *** [Makefile:127: test_bindist] Error 2

This is when I typically `make distclean`. That being said, this does look a bit suspicious. Let me know if cleaning doesn't help.

Cheers,

- Ben

On Mar 13, 2017, at 5:57 PM, Ben Gamari <ben@well-typed.com> wrote:

Richard, this is on Linux, yes?

Yes, it is. But I have now noticed other aspects of some very strange behavior regarding the filesystem on my Linux server, so the problem may be unrelated to GHC. (Example of other problem: running the testsuite, with `make`, reveals tons of stderr mismatches. Some digging reveals that the .run.stderr files are sometimes truncated.) So, thanks for the offers for help, but I’ve passed this problem up to my sysadmin. Thanks, Richard

geekosaur suggests on IRC that this might be related to a SELinux security policy. "what might be possible is that hLock uses fcntl locking, ghc-pkg opens a database r/o if it can't open it r/w, and it tried to acquire a write lock (which will fail with EBADF if the file descriptor is only open for read). and there is an SElinux context prohibiting your process opening the db for write" On Sat, Jul 8, 2017 at 11:20 PM, Matthew Pickering <matthewtpickering@gmail.com> wrote:

Hi Richard,

I seem to be running into a similar error message when using "make install", did you ever find a solution to the problem?

Matt

On Mon, Mar 13, 2017 at 10:17 PM, Richard Eisenberg <rae@cs.brynmawr.edu> wrote:

...

...

On Mar 13, 2017, at 5:57 PM, Ben Gamari <ben@well-typed.com> wrote:

Richard, this is on Linux, yes?

Yes, it is. But I have now noticed other aspects of some very strange behavior regarding the filesystem on my Linux server, so the problem may be unrelated to GHC. (Example of other problem: running the testsuite, with `make`, reveals tons of stderr mismatches. Some digging reveals that the .run.stderr files are sometimes truncated.)

So, thanks for the offers for help, but I’ve passed this problem up to my sysadmin.

Thanks, Richard _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs