unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Jacob Hrbek <kreyren@rixotstudio.cz>
Cc: 54011-done@debbugs.gnu.org
Subject: bug#54011: FreeCAD: Unable to import STEP files
Date: Fri, 18 Feb 2022 16:00:08 +0000	[thread overview]
Message-ID: <871r00noss.fsf@kitej> (raw)
In-Reply-To: <87pmnmudcq.fsf@kitej>

[-- Attachment #1: Type: text/plain, Size: 968 bytes --]

Guillaume Le Vaillant <glv@posteo.net> skribis:

> When decompressing the zip file and importing the STEP file:
>
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "/gnu/store/cwfgf3xb2vfqckxqv196jz8xpbigxkqj-python-shiboken-2-5.15.2/lib/python3.9/site-packages/shiboken2/files.dir/shibokensupport/__feature__.py", line 142, in _import
>     return original_import(name, *args, **kwargs)
> <class 'ImportError'>: /gnu/store/pd0pxvnr3qdgcz37p80v6q8p0wk9xyfh-freecad-0.19.3-0.09a05a9/lib/Import.so: undefined symbol: _ZN3tbb6detail2r122cancel_group_executionERNS0_2d118task_group_contextE
>
> I guess now we have to find where
> '_ZN3tbb6detail2r122cancel_group_executionERNS0_2d118task_group_contextE'
> is coming from.

It was coming from the fact that the freecad package had the tbb package
as dependency, but it also depends on opencascade-occt which depends on
tbb-2020.
Fix pushed as 27a91b2f57bd0bf7efab77eaeb4b920f162bf8c8.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-02-18 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 14:56 bug#54011: FreeCAD: Unable to import STEP files Jacob Hrbek
2022-02-16  8:55 ` Guillaume Le Vaillant
2022-02-16 13:45   ` Guillaume Le Vaillant
2022-02-18 16:00     ` Guillaume Le Vaillant [this message]
2022-02-18 16:07       ` Jacob Hrbek
2022-02-19 21:55       ` Jacob Hrbek
2022-02-19 22:48         ` Guillaume Le Vaillant
2022-02-20  1:05           ` Jacob Hrbek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871r00noss.fsf@kitej \
    --to=glv@posteo.net \
    --cc=54011-done@debbugs.gnu.org \
    --cc=kreyren@rixotstudio.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).