element-desktop: build error about gentoo-overlay

[VPaulV]

I guess I found a solution - https://bugs.gentoo.org/909731
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c433d383887eeb559d1826becd4a5cf9944ca7f7

[VPaulV]

It was not wayland related issue, I only migrated to it a few days ago

[PF4Public]

Please do not ignore issue template that says: "Please provide any relevant information including the full build log."

[PF4Public]

Oh, I am sorry. Thought I have added it: http://0x0.st/HvMi.log

Seriously? Come on! "Please provide any relevant information including the full build log. Please don't use external services for that."

P.S: I have seen in another issue you was happy that somebody was using ungoogled. This is my daily driver as well, thank you for the ebuild

Glad to know.

[VPaulV]

Full build log:
build.log

[PF4Public]

Did it work before?

/var/tmp_builddir looks like a symlink. webpack does not like symlinks.

[VPaulV]

No, it didn't work previously.

/var/tmp_builddir is not a symbolic link. I build everything in RAM, but it seems 20GB is insufficient for electron/element-web. Therefore, I designated a special directory on my NVME for their build with PORTAGE_TMPDIR="/var/tmp_builddir"

[PF4Public]

Then there might be an issue with permissions on that mountpoint.

[VPaulV]

Seems to have the same permissions as the one in RAM?

home /home/me # ls -lah /var/tmp_builddir/portage/
total 0
drwxrwxr-x 1 portage portage 12 Nov 14 23:27 .

home /home/s10n # ls -lah /tmp/portage/
total 0
drwxrwxr-x  2 portage portage  40 Nov 12 19:35 .

What permissions should I setup?

[PF4Public]

It is trying to access '/.config/svgrrc'. That's not right. Check your environment, it shouldn't be in root, it should be in portage directory.

[VPaulV]

I am sorry, I am not following you. What exactly should I check? I guess it is something NPM related?

[PF4Public]

It is searching for .svgrrc:
https://github.com/gregberge/svgr/blob/f73f14d84f3a372e4f1f1af02ba0b5ccfbc5bd6d/website/pages/docs/configuration-files.mdx#L16-L18

In an ascending manner until it hits home:
https://github.com/cosmiconfig/cosmiconfig/blob/42ca3fab6d6ae593a895c0fe4e2a5f6b297e6361/README.md?plain=1#L26

https://github.com/cosmiconfig/cosmiconfig/blob/42ca3fab6d6ae593a895c0fe4e2a5f6b297e6361/src/index.ts#L131

On your system it does not stop until it reaches root, which suggests that there is something wrong with your configuration, perhaps because you switch portage folders.

It might be possible to prevent this behaviour via --no-runtime-config:
https://github.com/gregberge/svgr/blob/f73f14d84f3a372e4f1f1af02ba0b5ccfbc5bd6d/packages/cli/README.md?plain=1#L21

But I'm not very familiar with all this JavaScript mess that is being constantly created around node.

For your reference it does not fail this way for me. Neither on my system, nor in my tests: https://github.com/PF4Public/gentoo-overlay/actions/workflows/element-web.yml

For example

src_compile () 
{ 
    node -r os -e 'console.log(os.homedir());'
    die
    node /usr/bin/yarn run build || die
}

results in following:

/var/tmp/portage/net-im/element-web-1.11.49/homedir
 * ERROR: net-im/element-web-1.11.49::pf4public failed (compile phase):

[VPaulV]

When I am checking /var/tmp_builddir/portage/net-im/element-web-1.11.49/work/element-web-1.11.49, I see no .svgrrc there. Could you please check if it is generated for you? Or where it is located in your case?

[PF4Public]

Could you please check if it is generated for you?

It isn't and it shouldn't. The problem is that on your system it does not stop at /var/tmp_builddir/portage/net-im/element-web-1.11.49/, but goes up.

[VPaulV]

Alright, I allocated 32gb to build in RAM, so everything is in /var/tmp/portage. Yet, the build fails with the same error. I guess we now know that the problem is not with the PORTAGE_TMPDIR.

[PF4Public]

🤷🏻 No idea what else could it be :(

[PF4Public]

Would you like to submit PR?

[VPaulV]

Sure, if you think it is needed. Since it is working well in your tests, maybe my system is abnormal and something is broken? Would be wrong to add a fix just for my system xD

[PF4Public]

Would be wrong to add a fix just for my system xD

This fix should not harm anyway.

[VPaulV]

I conducted a test in a VM with a clean Gentoo install, and the build failed there as well. Therefore, I guess the patch makes sense. I wonder what kind of extra setup do you have on your system

[PF4Public]

I wonder what kind of extra setup do you have on your system

Not using wayland perhaps :D