Skip to content

archivers/liblz4: fix build failure on DragonFly#1541

Closed
dragonflybot wants to merge 1 commit into
masterfrom
agentic/archivers-liblz4-20260528-101530Z
Closed

archivers/liblz4: fix build failure on DragonFly#1541
dragonflybot wants to merge 1 commit into
masterfrom
agentic/archivers-liblz4-20260528-101530Z

Conversation

@dragonflybot

Copy link
Copy Markdown
Member

Generated by the DragonFly agentic build-fix loop and verified in a clean dev-env. Reviewed and accepted by operator operator before submission.

Problem

The build failed on @2026Q2 — classified patch-error, confidence high.

A DragonFly‑specific post‑patch step (likely from a Makefile in the DeltaPorts overlay) invokes sed on file paths that incorrectly include a ../../ prefix, causing it to resolve outside the source tree. The missing file error (No such file or directory) occurs because the constructed path /construction/archivers/liblz4/lz4-1.10.0/../../Makefile points to /construction/archivers/liblz4/Makefile instead of the intended ${WRKSRC}/Makefile. This is not a static patch‑hunk failure; the sed command itself is flawed.

Evidence:

  • Exact error line:
    sed: /construction/archivers/liblz4/lz4-1.10.0/../../Makefile: No such file or directory
  • The failing command shown in the log:
    /usr/bin/sed -i.bak 's|GNU FreeBSD|GNU FreeBSD DragonFly|' /construction/archivers/liblz4/lz4-1.10.0/../../Makefile /construction/archivers/liblz4/lz4-1.10.0/../../lib/Makefile /construction/archivers/liblz4/lz4-1.10.0/../../programs/Makefile

Both clearly show that the sed operation is acting on paths that escape WRKSRC by an extra two levels.

Fix

Automated fix for the build failure in archivers/liblz4.

What changed

2 files changed, +11/-6

  • ports/archivers/liblz4/Makefile.DragonFly
  • ports/archivers/liblz4/overlay.dops

Verification

Built successfully in a DragonFly dev-env (dsynth) for target @2026Q2.
Verified 2026-05-28T11:42:12.098923+00:00.

Provenance

  • Operator: operator
  • Agent: model=deepseek/deepseek-v4-pro attempts=1 tokens=157183

> Generated by the DragonFly agentic build-fix loop and verified in a clean dev-env. Reviewed and accepted by operator `operator` before submission.

## Problem

The build failed on `@2026Q2` — classified `patch-error`, confidence `high`.

A DragonFly‑specific post‑patch step (likely from a Makefile in the DeltaPorts overlay) invokes `sed` on file paths that incorrectly include a `../../` prefix, causing it to resolve outside the source tree. The missing file error (`No such file or directory`) occurs because the constructed path `/construction/archivers/liblz4/lz4-1.10.0/../../Makefile` points to `/construction/archivers/liblz4/Makefile` instead of the intended `${WRKSRC}/Makefile`. This is not a static patch‑hunk failure; the sed command itself is flawed.

**Evidence:**

- **Exact error line:**
  `sed: /construction/archivers/liblz4/lz4-1.10.0/../../Makefile: No such file or directory`
- **The failing command shown in the log:**
  `/usr/bin/sed -i.bak 's|GNU FreeBSD|GNU FreeBSD DragonFly|' /construction/archivers/liblz4/lz4-1.10.0/../../Makefile /construction/archivers/liblz4/lz4-1.10.0/../../lib/Makefile /construction/archivers/liblz4/lz4-1.10.0/../../programs/Makefile`

Both clearly show that the sed operation is acting on paths that escape `WRKSRC` by an extra two levels.

## Fix

Automated fix for the build failure in `archivers/liblz4`.

## What changed

2 files changed, +11/-6

- `ports/archivers/liblz4/Makefile.DragonFly`
- `ports/archivers/liblz4/overlay.dops`

## Verification

Built successfully in a DragonFly dev-env (dsynth) for target `@2026Q2`.
Verified 2026-05-28T11:42:12.098923+00:00.

## Provenance

- Operator: operator
- Agent: model=deepseek/deepseek-v4-pro attempts=1 tokens=157183

Signed-off-by: Fred [bot] <github@dragonflybsd.org>
@tuxillo tuxillo marked this pull request as ready for review May 28, 2026 13:52
@tuxillo tuxillo marked this pull request as draft May 28, 2026 13:52
@tuxillo tuxillo closed this May 28, 2026
@tuxillo tuxillo deleted the agentic/archivers-liblz4-20260528-101530Z branch May 28, 2026 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants