1

Hi,

  Since pulling from git yesterday moring, I haven't been able to get
incremental builds of llvm-linux-x86_64 to work. The initial build works,
but subsequent incremental builds fail with:

/home/vagrant/build/dpg/llvm-linux-x86_64/tools/clang/clang.order: file not
recognized: File truncated
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
ninja: build stopped: subcommand failed.
./utils/build-script: command terminated with a non-zero exit status 1,
aborting
./utils/build-script: command terminated with a non-zero exit status 1,
aborting

If I rm -rf the llvm-linux-x86_64 build directory and build from scratch it
succeeds (once), but incremental builds fail.

A couple of us at IBM are seeing this problem (not just my bad luck....).

Any suggestions on how to fix? Anyone else seeing it?

thanks,

--dave

2

This is an upstream llvm problem that is currently being fixed. The patch is under review.

Either clean your workspace, or here is a patch that fixes it:

Michael

order-file-fix.patch (1.47 KB)

···

On Feb 11, 2016, at 10:00 AM, David P Grove via swift-dev <swift-dev@swift.org> wrote:

Hi,

Since pulling from git yesterday moring, I haven't been able to get incremental builds of llvm-linux-x86_64 to work. The initial build works, but subsequent incremental builds fail with:

/home/vagrant/build/dpg/llvm-linux-x86_64/tools/clang/clang.order: file not recognized: File truncated
clang: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
./utils/build-script: command terminated with a non-zero exit status 1, aborting
./utils/build-script: command terminated with a non-zero exit status 1, aborting

If I rm -rf the llvm-linux-x86_64 build directory and build from scratch it succeeds (once), but incremental builds fail.

A couple of us at IBM are seeing this problem (not just my bad luck....).

Any suggestions on how to fix? Anyone else seeing it?

thanks,

--dave

_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

3

The patch landed up stream. I just created a pull request with the cherry-pick and am just running it through the CI. Once it passes the tests, I will commit.

Michael

···

On Feb 11, 2016, at 1:44 PM, Michael Gottesman <mgottesman@apple.com> wrote:

This is an upstream llvm problem that is currently being fixed. The patch is under review.

Either clean your workspace, or here is a patch that fixes it:

<order-file-fix.patch>

Michael

On Feb 11, 2016, at 10:00 AM, David P Grove via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:

Hi,

Since pulling from git yesterday moring, I haven't been able to get incremental builds of llvm-linux-x86_64 to work. The initial build works, but subsequent incremental builds fail with:

/home/vagrant/build/dpg/llvm-linux-x86_64/tools/clang/clang.order: file not recognized: File truncated
clang: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
./utils/build-script: command terminated with a non-zero exit status 1, aborting
./utils/build-script: command terminated with a non-zero exit status 1, aborting

If I rm -rf the llvm-linux-x86_64 build directory and build from scratch it succeeds (once), but incremental builds fail.

A couple of us at IBM are seeing this problem (not just my bad luck....).

Any suggestions on how to fix? Anyone else seeing it?

thanks,

--dave

_______________________________________________
swift-dev mailing list
swift-dev@swift.org <mailto:swift-dev@swift.org>
https://lists.swift.org/mailman/listinfo/swift-dev