pyside6 -- freecad dependeny fails to compile

[tckosvic]

@genome,

I understand what you are saying but the actual errors that are listed by emerge were included in my first post. The errors listed in the build.log file look to me to be a repetition of the errors listed by emerge.
But perhaps there is more info in build.log that I am not conversant with.
See below from my first post.

[eschwartz]

[Genone]

[tckosvic]

As a sidebar to my query on pyside6 compile errors, I am doing some forced learning about pastebin apps, pastebin websites, and also how error messages from emerge differ from those in build.log.
Thanks all.

Anyone suggest an alternate to wgetpaste (that I thought was a gentoo std) that can handle whole files (not text snippets) and binary files, e.g., gz files?

Also best (non-google) pastebin site to handle whole binary files?

I know this really is a sidebar and perhaps should be an independent question.

thanks all, tom kosvic

[Nowa]

[tckosvic]

I reloaded a gzipped build.log file to a pastebin I found that says it will handle binary files.

https://paste.c-net.org/MelroseCrips

Let me know if it works

thanks, tom kosvic

[Ionen]

Hm, think(?) it failed to find Qt6 because of the way the pyside6 ebuild disable things, and then gives a misleading error with init_enum.

aka, think another Qt component was installed with USE=designer set (if not some overlooked automagic), and the .cmake file expects to find it.. but pyside6 does the CMAKE_DISABLE_FIND_PACKAGE thing with USE=-designer and that makes it fail (always thought this would cause problems, doing that is safe'ish for some Qt components but not all of them).

Not sure if it'll help but you can try enabling USE=designer on pyside6 as a workaround.

[tckosvic]

Your analysis was way above me. I am just a retired engineer messing around in fluid mechanics and astronomy.
I don't remember setting designer as USE flag anywhere intentionally if that helps the diagnosis.

I will run emerge pyside6 with designer set a a USE for the emerge.

Appreciate your expertise, thanks.

[tckosvic]

@Ionen, update.

After adding designer USE flag to pyside6, the emerge would not run until qttools was also re-emerged with designer as a USE flag.

That is now running, will take a while.

thanks, tom kosvic

[Ionen]

I could be wrong fwiw (hardly know pyside6 or python) esp. given I hardly see what could be requiring designer, but I don't see much else. If it didn't help, feel free to unset USE=designer on qttools and pyside6.

I did find one other person run into this error (on freecad forums, doesn't sound like they're using Gentoo and may be doing something odd), but that didn't really give me any ideas. Whatever they're doing shouldn't be required to build pyside6 normally. Maybe someone else will have an idea though.

Edit: On another note, if you only need it for freecad I tend to feel people are better off using the AppImage or flatpak for it -- pyside is a mess and there's often other problems. Moreso if pyside/freecad take a while to build for you.

[tckosvic]

This emerge qttools and pyside6 run with USE =designer did not go as far as previous.

[Ionen]

Well, that's actually a more interesting error and makes more sense with the error you were getting further on. You can "probably" unset the designer stuff albeit I do wonder why it led to a different error.

Haven't tried but perhaps the ebuild for shiboken6/pyside6 are broken when PYTHON_TARGETS="python3_11 python3_12" (which you have set, probably in your /etc/portage/make.conf if not package.use) rather than having only one (the default). Likely worth a bug report.

You could try to go back to the default (by removing PYTHON_TARGETS, which will give you just python3_12) and do a world update as a workaround anyhow. Alternatively, USE=-python_targets_python3_11 on dev-python/shiboken6, dev-python/pyside6, and dev-python/pyside6-tools should be sufficient -- perhaps portage will complain about other packages I overlooked though.

[tckosvic]

@Ionen,

I will work through the things you suggested.

I have an anathema for appimages but I did download freecad appimage just to get it running. It didn't run because (so I have diagnosed) a fuse module is not compiled into my kernel or made separately as a module. Now I made a new kernel with fuse activated.

The freecad appimage started up in text in a terminal but then threw error that freecad appimage "could not initialize GLX" before any graphics started. I can't find any gentoo info on GLX. So I am investigating GLX.

thanks for your assistance. tom kosvic

[Hu]

Failure to initialize GLX is often an indication that the program lacks access to video acceleration. This could be because it is not in the video group, or might be a side effect of some sandbox imposed by the AppImage.

[tckosvic]

I removed from package.use PYTHON_TARGETS --> python3_11 python3_12
and left: PYTHON_SINGLE_TARGET --> python3_12

I removed from package.use all references to "designer" USE flag

I ran emerge -av freecad and it ran to completion and starts up to gui and freecad runs. Thus, freecad v1 rc2 compiled and at least starts up gui. That is what I've been trying to get going.

I have no idea what happened to pyside6 that was a dependency of freecad at one point. Perhaps freecad is missing some functionality w/o pyside6 but I don't know yet.

thanks, tom kosvic

[tckosvic]

Further clarification, pyside6 is now instaled as emerge of pyside6 is calling for a rebuild. So the changes described in previous reply must have worked to get pyside6 compiled.

[Nowa]

[Nowa]

I see in your log that some user managed python environment is leaking into portage: /home/tom/miniconda3/bin/python3.12

I suspect this is the cause of your original problem. It may also cause problems elsewhere, I recommend investigating where it comes from and then ensuring it stays confined to your user.

Your second configure problem is weirder, it originates in shiboken. /usr/lib64/cmake/Shiboken6/Shiboken6Config-python3.11.cmake should set(SHIBOKEN_PYTHON_VERSION_MINOR "11") but somehow you have a mismatch between the name of the configure file and the python version it is setting. Perhaps this is also caused by your python 3.12 miniconda environment leaking into the build.
_________________
OS: Gentoo 6.10.12-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400

[Ionen]

Ah, hadn't noticed that, likely not an ebuild problem for python version then. These variables can indeed cause problems.

[tckosvic]

Very good observation. I didn't note miniconda issue. I think minicpnda environment could be confusing things. I will deactivate from minicoda and try another emerge @world. On another occasion miniconda environment has created an issue. i.e., stopped running dconf-editor.

thanks for noting that.

tom kosvic

[Hu]

You should not need to deactivate the miniconda environment, because it should not be active in the root shell at all. How are you starting the root shell from which you start emerge? You should use /bin/su -, so that you get a clean environment. Omitting the - allows user variables to leak through, and we have seen numerous users suffer odd problems when such variables leak.

[tckosvic]

I have just been using su (w/o - ) to get to root. The base miniconda environment sticks to the root prompt in terminal so emerge has been using miniconda environment at least some of the time. I am sure that is how modules got emerged in python environments that weren't what emerge USE flags were setting. It just never occurred to me that miniconda could be an issue.

I did a manual conda deactivate as root to start the emerge that is now running.

I feel certain the miniconda environment has caused all the python related problems we all have been addressing.

I would like to see a "sticky" thread on the website describing this problem and how to avoid it to help prevent others from wasting all this time unnecessarily. I don't think I have the privileges needed to do this myself.

thanks, tom kosvic