From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A1350138334 for ; Tue, 13 Nov 2018 18:12:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DBCA0E0AD0; Tue, 13 Nov 2018 18:11:52 +0000 (UTC) Received: from mail-qk1-f181.google.com (mail-qk1-f181.google.com [209.85.222.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5CF45E0AC2 for ; Tue, 13 Nov 2018 18:11:52 +0000 (UTC) Received: by mail-qk1-f181.google.com with SMTP id q70so3588162qkh.6 for ; Tue, 13 Nov 2018 10:11:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :message-id:mime-version:content-disposition :content-transfer-encoding; bh=CwP4VROjY4+uwB5WU8gKLAvQHTZB0Rp0+2LdpsMdH7U=; b=EIXmB1TDcEiUFQ2n82WeyZXk6hbFv1v1cIaCDTA4ULiq6S+sxx2iBCPDHohz9qVM0j 8bIM2xxAluV8YIilidtUYYGgdg5pyvnM7n9SFnFnABF+ECW0NJv7+D9MlJC6VN5mNgzQ 7YwCm68mgC+cwZPDiwBtFjSNvMwhWQVlLQiYL32dzMFCqKIORPwcj4t3bc6fDZi0oNa2 gnblqZbZm3qJkhXtEyI2Ac2kOvyIt4MpENTW9FxrpgHMxZ1fsXbFm0XEnYve3QEcGX+m lt3lsqXLDgT5lfdmhOe6oW80a0KHXAOID0/U+8U4gcH7n0PtF7l67sP5DwIq5BePW4ez 9Hag== X-Gm-Message-State: AGRZ1gJ+JvcDlbIewvAoQ3Ek6CUEgEZk4/JyHX4NiWM+U4Gbi5VTxZsD +42ojOYPLfN2X/lCGVsmnec738r6POI= X-Google-Smtp-Source: AJdET5e+4Xep3cklxu+Im+Po8T46+2P7xgyqy04vTholqs3GWulV1M8wufiATKAeThNC3K67c46v1A== X-Received: by 2002:aed:3e49:: with SMTP id m9mr5567705qtf.99.1542132711254; Tue, 13 Nov 2018 10:11:51 -0800 (PST) Received: from ffortso4 ([2601:188:180:4f46:1ec1:deff:fe62:b72f]) by smtp.gmail.com with ESMTPSA id q15sm11484329qkl.81.2018.11.13.10.11.50 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 13 Nov 2018 10:11:50 -0800 (PST) Date: Tue, 13 Nov 2018 13:11:49 -0500 From: Jack Subject: Re: [gentoo-user] Weird compilation error (nasm) To: gentoo-user@lists.gentoo.org References: <20181113171138.rwe43lsliihyhh7s@solfire> In-Reply-To: <20181113171138.rwe43lsliihyhh7s@solfire> (from tuxic@posteo.de on Tue Nov 13 12:11:38 2018) X-Mailer: Balsa 2.5.6-70-g55c9d84bf Message-Id: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 30a1e988-c986-477e-90ff-cc1cbb53a6b8 X-Archives-Hash: e8405eb35c08fcabc59fe76c5dfc6561 On 2018.11.13 12:11, tuxic@posteo.de wrote: > Hi, >=20 > I got a weird looking error while upgrading/recompiling nasm: [snip....] > -- Configuring done > -- Generating done > -- Build files have been written to: =20 > /var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/work/libjpeg-turbo-2.0.1-= abi_x86_64.amd64 > >>> Source configured. > * --------------------------- ACCESS VIOLATION SUMMARY =20 > --------------------------- > * LOG FILE: "/var/log/sandbox/sandbox-16492.log" > * > VERSION 1.0 > FORMAT: F - Function called > FORMAT: S - Access Status > FORMAT: P - Path as passed to function > FORMAT: A - Absolute Path (not canonical) > FORMAT: R - Canonical Path > FORMAT: C - Command Line >=20 > F: fopen_wr > S: deny > P: /? > A: /? > R: /? > C: /usr/bin/nasm /? > * =20 > -------------------------------------------------------------------------= ------- > !!! When you file a bug report, please include the following =20 > information: > GENTOO_VM=3D CLASSPATH=3D"" JAVA_HOME=3D"" > JAVACFLAGS=3D"" COMPILER=3D"" > and of course, the output of emerge --info =3Dlibjpeg-turbo-2.0.1 > * > * The following package has failed to build, install, or execute =20 > postinst: > * > * (media-libs/libjpeg-turbo-2.0.1:0/0::gentoo, ebuild scheduled for =20 > merge), Log file: > * '/var/tmp/portage/media-libs/libjpeg-turbo-2.0.1/temp/build.log' >=20 >=20 > If wanted I will post the build.log etc... >=20 > I never had an error looking like this one... >=20 > Any fox for that or am I the onlu one...? >=20 > Cheers! > Meino How did you become root to do this emerge? If you just did "su" you =20 need to do "su -". Most cases I've seen of this type of sandbox =20 violation are because your Environment has not been sanitized. There =20 is something in it that leads emerge to try to do something in a place =20 prohibited by the sandbox. I believe if you check for the ebuild status, it will be marked as =20 having completed configuration, so you could just continue with "ebuild =20 /path/to/ebuild/file qmerge" to complete the process. Jack=