Skip to content

Bootstraping error #185

Description

@d3xt0rn
...
checking for sysctl... no
checking for unsetenv... yes
checking for vsnprintf... yes
checking for wait3... yes
checking for wait4... yes
checking for waitpid... yes
checking for warn... yes
checking for warnx... yes
checking for getopt... yes
checking for realpath... yes
checking for dirname... yes
checking for sigaction... yes
checking for stresep... (cached) no
checking for strlcpy... yes
checking for emalloc in -lutil... no
checking whether stat file-mode macros are broken... no
checking if compiler supports __func__
checking if diff -u works... yes
checking for MACHINE & MACHINE_ARCH...
defaults: MACHINE=x86_64, MACHINE_ARCH=x86_64
Using: MACHINE=x86_64, MACHINE_ARCH=x86_64
Using: MKSRC=${srcdir}/mk
configure: creating ./config.status
./config.status: line 529: 0a1,135: command not found
./config.status: line 530: syntax error near unexpected token `newline'
./config.status: line 530: `> # This file is a shell script that caches the results of configure'
===> exited with status 1
aborted.
root:/sources/all4pkgsrc/pkgsrc/bootstrap# diff --verison

(im not presed ^C its just crashed)

Activity

  1. iamleot commented on Aug 7, 2026

    @iamleot
    Member

    On which system does it happen? Which pkgsrc version? What is the exact bootstrap invocation? (please share that too)

  2. d3xt0rn commented on Aug 7, 2026

    @d3xt0rn
    Author

    On which system does it happen? Which pkgsrc version? What is the exact bootstrap invocation? (please share that too)

    L.F.S. latest stable, ./bootstrap

  3. bsiegert commented on Aug 7, 2026

    @bsiegert
    Contributor

    I assume this is the bmake configure?

    I have seen this happen if you are running bootstrap with the wrong shell. Do you have $SHELL set? Is your default shell zsh?

    If so, try bash ./bootstrap.

  4. d3xt0rn commented on Aug 8, 2026

    @d3xt0rn
    Author

    bootstrap done thx

  5. iamleot commented on Aug 8, 2026

    @iamleot
    Member

    bootstrap done thx

    What was the problem?

  6. added a commit that references this issue on Aug 25, 2026
  7. added a commit that references this issue on Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions