NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: port-amd64/56456: build fails to build release with clang or x11



Hi, Joerg, Christos, thank you for your replies!

I figured it was something I wasn't doing correctly, somehow, but I couldn't seem to get it to resolve even on a clean build :( I'll have to look into why that is, but yeah, probably my fault somehow.

Please close this bug and port-amd/54569.


On 11/16/2021 6:15, Joerg Sonnenberger wrote:
The following reply was made to PR port-amd64/56456; it has been noted by GNATS.

From: Joerg Sonnenberger <joerg%bec.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-amd64-maintainer%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
	netbsd-bugs%netbsd.org@localhost, greywolf%starwolf.com@localhost
Subject: Re: port-amd64/56456: build fails to build release with clang or x11
Date: Tue, 16 Nov 2021 15:04:02 +0100

  On Tue, Nov 16, 2021 at 02:30:03AM +0000, Greywolf wrote:
  > The following reply was made to PR port-amd64/56456; it has been noted by GNATS.
  >
  > From: Greywolf <greywolf%starwolf.com@localhost>
  > To: gnats-bugs%netbsd.org@localhost
  > Cc:
  > Subject: Re: port-amd64/56456: build fails to build release with clang or x11
  > Date: Mon, 15 Nov 2021 18:25:07 -0800
  >
  >  On 10/16/2021 1:10, gnats-admin%netbsd.org@localhost wrote:
  >  > Thank you very much for your problem report.
  >  > It has the internal identification `port-amd64/56456'.
  >  > The individual assigned to look at your
  >  > report is: port-amd64-maintainer.
  >  >
  >  >> Category:       port-amd64
  >  >> Responsible:    port-amd64-maintainer
  >  >> Synopsis:       clang and x11 (which uses clang) releases will not build
  >  >> Arrival-Date:   Sat Oct 16 08:10:00 +0000 2021
  >
  >  Hiyas!
  >
  >  I have found a workaround for this issue!
  >
  >  Problem:
  >       The file:
  >
  >       /usr/src/external/apache2/llvm/dist/llvm/include/llvm/Support/VCSRevision.h
  >
  >       is missing and does not show up on a cvs update.  This leads to the command:
Of course it doesn't show up with cvs update. It is not and never was
  part of the repository. The file is created dynamically in
  llvm/include's objdir. I don't know what you are doing wrong locally as
  it works elsewhere. The typical candidates are objdir pollutions.
Joerg



Home | Main Index | Thread Index | Old Index