Package Details: boost1.69-libs 1.69.0-13

Git Clone URL: (read-only, click to copy)
Package Base: boost1.69
Description: Free peer-reviewed portable C++ source libraries - runtime libraries
Upstream URL:
Licenses: custom
Submitter: foutrelis
Maintainer: eggz
Last Packager: eggz
Votes: 1
Popularity: 0.000000
First Submitted: 2020-02-22 22:14 (UTC)
Last Updated: 2023-08-07 23:43 (UTC)

Latest Comments

1 2 Next › Last »

eggz commented on 2023-08-07 23:47 (UTC)

@MarsSeed, this package was abandoned, so it is a bit unclear to me who you were adressing. But hey, I fixed it anyway.

I opted to still use the old python3.10 in the aur as dependency, or the maintanance will only get worse over time. The new Py_SET_TYPE function expects a completely diffrent flow and it generated too much rewriting work.

MarsSeed commented on 2023-08-03 22:07 (UTC)

Fails to build with Python 3.11:

==> Making package: boost1.69 1.69.0-12 (2023-08-04 00:03:07 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
Building Boost.Build engine with toolset gcc... tools/build/src/engine/bin.linuxx86_64/b2
Detecting Python version... 3.11
Detecting Python root... /usr
Unicode/ICU support for Boost.Regex?... /usr
Generating Boost.Build configuration in project-config.jam...

Bootstrapping is done. To build, run:


To adjust configuration, edit 'project-config.jam'.
Further information:

  - Command line help:
    ./b2 --help

  - Getting started guide:

  - Boost.Build documentation:

/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/tools/build/src/build/feature.jam:491: in feature.validate-value-string from module feature
error: "3.10" is not a known value of feature <python>
error: legal values: "3.11"
/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/tools/build/src/build/property.jam:341: in validate1 from module property
/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/tools/build/src/build/property.jam:367: in property.validate from module property
/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/tools/build/src/build/build-request.jam:271: in convert-command-line-element from module build-request
/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/tools/build/src/build/build-request.jam:222: in build-request.convert-command-line-elements from module build-request
/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/tools/build/src/build-system.jam:774: in load from module build-system
/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/tools/build/src/kernel/modules.jam:295: in import from module modules
/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/tools/build/src/kernel/bootstrap.jam:139: in boost-build from module
/home/user/.cache/makepkg/boost1.69/src/boost_1_69_0/boost-build.jam:17: in module scope from module

==> ERROR: A failure occurred in build().

 -> error making: boost1.69 (boost1.69-libs boost1.69)

MarsSeed commented on 2023-07-19 10:34 (UTC)

The subpackages should provide boost=$pkgver and boost-libs=$pkgver, respectively.

eggz commented on 2022-02-17 14:55 (UTC) (edited on 2022-02-17 14:57 (UTC) by eggz)

I dirty fixed this package so I cant actually build. But I will not always have the time to maintain this package, So I'm disowning it for now.

lnex commented on 2022-02-17 05:24 (UTC)

I found that there was a fix already. see this, I modify the file and works well.

wbthomason commented on 2022-02-09 07:19 (UTC)

This also fails to build for me, and looking at the CI, it seems like it’s an issue there too.

eggz commented on 2022-02-05 10:59 (UTC)

I have had problems for weeks now building this package, and it seems I am the only one. So I'm really confused right now.

I have this blocking error multiple times:

libs/python/src/exec.cpp:109:14: error: ‘_Py_fopen’ was not declared in this scope; did you mean ‘_Py_wfopen’?

Does anyone have a clue what I am doing wrong, besides executing a very complex makepkg --force on this package??? :-D

bismarckkk commented on 2021-12-22 14:01 (UTC) (edited on 2021-12-22 14:01 (UTC) by bismarckkk)

It seems that default python version is 3.10 now. but building this package need python3.9 and it is not in dependcy.

fmauch commented on 2021-05-12 13:51 (UTC) (edited on 2021-05-12 20:53 (UTC) by fmauch)

For me (locally) it fails with

don't know how to make <e>j7
...found 1 target...
...can't find 1 target...

Same in a clean chroot environment. However, since it works for you and the CI/CD it's probably about my local configuration / make flags used. I'll investigate further.

Edit: Nevermind, my config error: I had MAKEFLAGS=j7. Should be MAKEFLAGS=-j7

bionade24 commented on 2021-05-12 13:18 (UTC)

@fmauch: What do you mean, it built fine on my local machine and on