Date: Sat, 6 Oct 2018 12:26:15 +0000 (UTC) From: Filippo Moretti <filippomore@yahoo.com> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: Problem compiling rust Message-ID: <1912901660.157423.1538828775273@mail.yahoo.com> References: <1912901660.157423.1538828775273.ref@mail.yahoo.com>
index | next in thread | previous in thread | raw e-mail
 extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/share/doc/cargo/README.md extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/manifest.in extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/etc/bash_completion.d/cargo extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/bin/cargo extracting cargo-0.29.0-x86_64-unknown-freebsd/cargo/share/zsh/site-functions/_cargorunning: /usr/ports/lang/rust/work/rustc-1.29.1-src/build/x86_64-unknown-freebsd/stage0/bin/cargo build --manifest-path /usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/Cargo.toml --frozenTraceback (most recent call last): File "/usr/ports/lang/rust/work/rustc-1.29.1-src/x.py", line 20, in <module>  bootstrap.main() File "/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 843, in main  bootstrap(help_triggered) File "/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 819, in bootstrap  build.build_bootstrap() File "/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 646, in build_bootstrap  run(args, env=env, verbose=self.verbose) File "/usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/bootstrap.py", line 148, in run  raise RuntimeError(err)RuntimeError: failed to run: /usr/ports/lang/rust/work/rustc-1.29.1-src/build/x86_64-unknown-freebsd/stage0/bin/cargo build --manifest-path /usr/ports/lang/rust/work/rustc-1.29.1-src/src/bootstrap/Cargo.toml --frozen*** Error code 1 Stop.make[1]: stopped in /usr/ports/lang/rust*** Error code 1 Stop.make: stopped in /usr/ports/lang/rust[root@sting /usr/ports/lang/rust]# I always had this problem trying to compiling rust (amd64 alpha3),as I only need it to compile firefox I wonder if it is possible to disable its building.Thanks Filippo From owner-freebsd-current@freebsd.org Sat Oct 6 12:38:12 2018 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30C8B10B8CFD for <freebsd-current@mailman.ysv.freebsd.org>; Sat, 6 Oct 2018 12:38:12 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94CD3732EE for <freebsd-current@freebsd.org>; Sat, 6 Oct 2018 12:38:11 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Sat, 06 Oct 2018 12:38:04 +0000 Authentication-Results: out.migadu.com; auth=pass (plain) Received: from [192.168.1.141] ([62.122.208.146]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 4DBA20CE-F3FF-4192-BC0D-BC79FBB68E39.1 envelope-from <greg@unrelenting.technology> (authenticated bits=0) (version=TLSv1/SSLv3 cipherìDHE-RSA-AES256-GCM-SHA384 verifyúIL); Sat, 06 Oct 2018 12:38:03 +0000 Date: Sat, 06 Oct 2018 15:38:00 +0300 From: Greg V <greg@unrelenting.technology> Subject: Re: linux-c7 and opengl apps? To: Theron <theron.tarigo@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, x11-list freebsd <freebsd-x11@freebsd.org> Message-Id: <1538829480.11691.0@smtp.migadu.com> In-Reply-To: <dbff419a-b104-fb60-d0b3-0eecd7dbd0d1@gmail.com> References: <CAECmPwvjJWNFELoeMcxGNFi_oXS5hWE4D2tTxi0TJpwBOriOrQ@mail.gmail.com> <dbff419a-b104-fb60-d0b3-0eecd7dbd0d1@gmail.com> X-Mailer: geary/0.12.4 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: quoted-printable DKIM-Signature: v=1; a=rsa-sha256; bhŠBVUM4Ox/pNV5WgKCkXbftK97IRdhwd4h9MzAyszVI=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; sÞfault; b=Bmg6L99qo48ERfW6BY307mRXUWF+1mAVCMCQpYZ0NlwMtpTh3z72yKFKQsGriDH6F/dImxBGWyfeg3YG9ZdGnULJytkTckQm2zy2USMOVaFJbE7dP6llPQjsbYp2cfKtRrs7le28GKN9fjwQXIHIFMdC+3Zqwc5Whh8GqCuqQz0X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 06 Oct 2018 12:38:12 -0000 On Fri, Oct 5, 2018 at 11:21 PM, Theron <theron.tarigo@gmail.com> wrote: > % /compat/linux/opt/VirtualGL/bin/glxinfo | grep OpenGL > libGL error: MESA-LOADER: failed to retrieve device information Do you have linsysfs mounted? Try reading /compat/linux/sys/class/drm/card0/device/uevent. Mesa won't retrieve device information without linsysfs. I wrote the linsysfs patch that exposed the info there so that recent Mesa would work :) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222375 (Wow, that was a year ago… interesting note from there: you might need to set LIBGL_DRI3_DISABLE=1 for Linux apps) Also, what's with the "/opt/VirtualGL"? Are you using mesa from linux-c7 or something… weird? > This problem has existed forever. I am not sure it is actually a > fault in Linux emulation, as these very same symptoms ("failed to > retrieve device information" message, console freeze) existed back in > FreeBSDDesktop/freebsd-base-graphics days when attempting to run > purely FreeBSD OpenGL apps. At the time the workaround was a patch > to Mesa's GPU detection; the underlying kernel problem wasn't > addressed. There was a somewhat related issue (but not the same one, FreeBSD and Linux versions of mesa/libdrm use different mechanisms to get device info). Mostly affected Wayland-EGL clients — they would try to access /dev/dri/card408 instead of /dev/dri/card0, fail to get info and fall back to software rendering. I fixed it a while ago: https://gitlab.freedesktop.org/mesa/mesa/commit/db8519a369261cdedda50852facc45616d4eba28 But I never saw console freezes when Mesa couldn't properly detect the GPU o_0home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1912901660.157423.1538828775273>