| Summary: | dev-lang/spidermonkey-24.2.0-r4 - Failed to set XATTR_PAX markings -me /var/tmp/portage/dev-lang/spidermonkey-24.2.0-r4/image//usr/bin/js24 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
| Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | jstein |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Juergen Rose
2017-05-17 18:27:10 UTC
Ping! Is there not any patch? I've no idea why this is occurring, but ginve it seems to be failing on xattr modifications, could you confirm that you have xattr support on your filesystem? Especially the /var/tmp/portage/ one if it differs from your root fs? What is your profile? What is your filesystem? Do you have the same error with one of the following packages? media-fonts/unifont-9.0.06 dev-lang/rust-1.16.0 see https://bugs.gentoo.org/show_bug.cgi?id=620524 https://bugs.gentoo.org/show_bug.cgi?id=620526 (In reply to Ian Stakenvicius from comment #2) > I've no idea why this is occurring, but ginve it seems to be failing on > xattr modifications, could you confirm that you have xattr support on your > filesystem? Especially the /var/tmp/portage/ one if it differs from your > root fs? /var/tmp is a separate logical volume with reiserfs. It seems that there is not any support for xattr on my reiserfs: root@cheetahnew:/root(15)# ll /proc/fs/ total 0 dr-xr-xr-x 6 root root 0 Jun 15 11:05 ext4/ dr-xr-xr-x 6 root root 0 Jun 15 11:05 jbd2/ dr-xr-xr-x 2 root root 0 Jun 15 11:05 lockd/ dr-xr-xr-x 2 root root 0 Jun 15 11:05 nfs/ drwxr-xr-x 2 root root 0 Jun 13 10:34 nfsd/ dr-xr-xr-x 2 root root 0 Jun 15 11:05 nfsfs/ dr-xr-xr-x 2 root root 0 Jun 15 11:05 xfs/ root@cheetahnew:/root(16)# getfattr /var/tmp What should I do, use an other filesystem? (In reply to Alessandro Barbieri from comment #3) > What is your profile? > What is your filesystem? > Do you have the same error with one of the following packages? > > media-fonts/unifont-9.0.06 > dev-lang/rust-1.16.0 > > see > https://bugs.gentoo.org/show_bug.cgi?id=620524 > https://bugs.gentoo.org/show_bug.cgi?id=620526 Emerge works with rust-1.16.0: root@cheetahnew:/usr/src(30)# qlist -Iv unifont rust app-eselect/eselect-rust-0.3_pre20150428 dev-lang/rust-1.16.0 media-fonts/unifont-9.0.06 I just tested. (In reply to Juergen Rose from comment #4) > (In reply to Ian Stakenvicius from comment #2) > > I've no idea why this is occurring, but ginve it seems to be failing on > > xattr modifications, could you confirm that you have xattr support on your > > filesystem? Especially the /var/tmp/portage/ one if it differs from your > > root fs? > > /var/tmp is a separate logical volume with reiserfs. It seems that there is > not any support for xattr on my reiserfs: > root@cheetahnew:/root(15)# ll /proc/fs/ > total 0 > dr-xr-xr-x 6 root root 0 Jun 15 11:05 ext4/ > dr-xr-xr-x 6 root root 0 Jun 15 11:05 jbd2/ > dr-xr-xr-x 2 root root 0 Jun 15 11:05 lockd/ > dr-xr-xr-x 2 root root 0 Jun 15 11:05 nfs/ > drwxr-xr-x 2 root root 0 Jun 13 10:34 nfsd/ > dr-xr-xr-x 2 root root 0 Jun 15 11:05 nfsfs/ > dr-xr-xr-x 2 root root 0 Jun 15 11:05 xfs/ > root@cheetahnew:/root(16)# getfattr /var/tmp > > What should I do, use an other filesystem? Yes. Altnernatively you -may- be able to add xattr support to reiserfs with a kernel option or a mount option. Or, you can set FEATURES="-xattr" in make.conf (In reply to Ian Stakenvicius from comment #6) > (In reply to Juergen Rose from comment #4) > > (In reply to Ian Stakenvicius from comment #2) ... > > root@cheetahnew:/root(16)# getfattr /var/tmp > > > > What should I do, use an other filesystem? > > Yes. Altnernatively you -may- be able to add xattr support to reiserfs with > a kernel option or a mount option. Or, you can set FEATURES="-xattr" in > make.conf Thanks Ian, after changing the filesystem of /var/tmp from reiserfs to ext4 the error disappeared. Thanks for confirming! |
