Re: Problem compiling py-* ports

2023-04-18 Thread Filippo Moretti
After completing installworld and rebuilding python39 I do get the same error as reported previouslyFilippo On Tuesday, April 18, 2023 at 12:54:33 PM UTC, Mateusz Guzik wrote: On 4/18/23, Filippo Moretti wrote: > Good morning,                      I run this versione of Frrebsd and a

Re: Problem compiling py-* ports

2023-04-18 Thread Mateusz Guzik
On 4/18/23, Filippo Moretti wrote: > Good morning, I run this versione of Frrebsd and al > py-* ports fail with the following message.sincerelyFilippo > > FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #6 > main-n261981-63b113af5706: Tue Apr 4 16:57:47 CEST 2023 > filippo@S

Re: Problem compiling py-* ports

2023-04-18 Thread Filippo Moretti
After following the instructions provided I get the following:==>>> All >> py39-pygments-2.14.0 (1/9) ===>  Building for py39-pygments-2.15.0 /usr/local/bin/python3.9: No module named build *** Error code 1 Stop. make: stopped in /usr/ports/textproc/py-pygments ===>>> make build failed for te

Re: Problem compiling py-* ports

2023-04-18 Thread Felix Palmen
* Marek Zarychta [20230418 11:41]: > What is the culprit? Most likely some leftovers from older package versions (so it's only a problem when building in the live system. A clean jail won't have the offending files). > Removing blindly all py- packages for all affected > hos

Re: Problem compiling py-* ports

2023-04-18 Thread Christos Chatzaras
> On 18 Apr 2023, at 11:12, Filippo Moretti wrote: > > Good morning, >I run this versione of Frrebsd and al py-* ports fail > with the following message. > sincerely > Filippo Maybe this helps: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269545#c6

Re: Problem compiling py-* ports

2023-04-18 Thread Marek Zarychta
W dniu 18.04.2023 o 10:46, Felix Palmen pisze: * Filippo Moretti [20230418 08:12]:   File "/usr/local/lib/python3.9/site-packages/setuptools/_importlib.py", line 31, in     if isinstance(ob, importlib_metadata.MetadataPathFinder) AttributeError: module 'importlib_metadata' has no attribute

Re: Problem compiling py-* ports

2023-04-18 Thread Felix Palmen
* Filippo Moretti [20230418 08:12]: >   File "/usr/local/lib/python3.9/site-packages/setuptools/_importlib.py", > line 31, in >     if isinstance(ob, importlib_metadata.MetadataPathFinder) > AttributeError: module 'importlib_metadata' has no attribute > 'MetadataPathFinder' Looks like you're b

Problem compiling py-* ports

2023-04-18 Thread Filippo Moretti
Good morning,   I run this versione of Frrebsd and al py-* ports fail with the following message.sincerelyFilippo FreeBSD STING 14.0-CURRENT FreeBSD 14.0-CURRENT #6 main-n261981-63b113af5706: Tue Apr  4 16:57:47 CEST 2023 filippo@STING:/usr/obj/usr/src/amd64.amd64/sys/ST

Re: Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
I deleted /usr/obj and restarted world I will see tomorrow the outcome.Filippo On Wednesday, December 14, 2022 at 02:22:57 PM GMT+1, Filippo Moretti wrote: I downloaded src for current on 13/12 11.20 CEST.I did have the same issues for about 5 days I made a few attempts all whit sam

Re: Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
I downloaded src for current on 13/12 11.20 CEST.I did have the same issues for about 5 days I made a few attempts all whit same error.Filippo On Wednesday, December 14, 2022 at 02:18:20 PM GMT+1, Herbert J. Skuhra wrote: On Wed, 14 Dec 2022 14:08:01 +0100, Filippo Moretti wrote: > >

Re: Problem compiling CURRENT

2022-12-14 Thread Herbert J. Skuhra
On Wed, 14 Dec 2022 14:08:01 +0100, Filippo Moretti wrote: > > FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #4 > main-n258255-de56ac88099: Wed Sep 28 19:35:24 CEST 2022 > root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY amd64 > > > > > > > > Dear Sir I had the following error while try

Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #4 main-n258255-de56ac88099: Wed Sep 28 19:35:24 CEST 2022 root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY amd64 Dear Sir I had the following error while trying to compile CURRENT===> usr.bin/rs (all) make[4]: /usr/obj/usr/src/amd64.amd64

Problem compiling llvm14

2022-03-26 Thread Filippo Moretti
 File "", line 219, in _call_with_frames_removed  File "/usr/local/lib/python3.8/site-packages/sphinx/cmd/build.py", line 25, in     from sphinx.application import Sphinx  File "/usr/local/lib/python3.8/site-packages/sphinx/application.py", line 43, in     from sphinx.registry import SphinxComp

Re: Problem compiling firefox

2022-02-08 Thread Charlie Li
Filippo Moretti wrote: /usr/local/bin/clang++13 -std=gnu++17 --target=wasm32-wasi --sysroot=/usr/local/share/wasi-sysroot -o rlbox.wasm -Wl,--export-all -Wl,--stack-first -Wl,-z,stack-size=262144 -Wl,--no-entry -Wl,--growable-table ogg_alloc.wasm ogg_bitwise.wasm ogg_framing.wasm xmlparse.wasm

Problem compiling firefox

2022-02-08 Thread Filippo Moretti
/usr/local/bin/clang++13 -std=gnu++17 --target=wasm32-wasi --sysroot=/usr/local/share/wasi-sysroot -o rlbox.wasm -Wl,--export-all -Wl,--stack-first -Wl,-z,stack-size=262144 -Wl,--no-entry -Wl,--growable-table ogg_alloc.wasm ogg_bitwise.wasm ogg_framing.wasm xmlparse.wasm xmlrole.wasm xmltok.was

Re: Problem compiling ports

2021-12-02 Thread Tomoaki AOKI
Confirmed. Thanks for your quick reaction! On Tue, 30 Nov 2021 22:45:37 + Brooks Davis wrote: > Yeah, I've got this in progress. > > -- Brooks > > On Wed, Dec 01, 2021 at 06:57:56AM +0900, Tomoaki AOKI wrote: > > It would be better making new special handling like BE_AMDGPU for it. > > Bui

Re: Problem compiling ports

2021-11-30 Thread Brooks Davis
Yeah, I've got this in progress. -- Brooks On Wed, Dec 01, 2021 at 06:57:56AM +0900, Tomoaki AOKI wrote: > It would be better making new special handling like BE_AMDGPU for it. > Building with BE_STANDARD just for this would be a pain for some users. > > (CC'ing freebsd-ports ML.) > > > On Tue

Re: Problem compiling ports

2021-11-30 Thread Tomoaki AOKI
It would be better making new special handling like BE_AMDGPU for it. Building with BE_STANDARD just for this would be a pain for some users. (CC'ing freebsd-ports ML.) On Tue, 30 Nov 2021 17:45:30 + Brooks Davis wrote: > In the config for devel/llvm11, is BE_STANDARD enabled? If not, you

Re: Problem compiling ports

2021-11-30 Thread Brooks Davis
In the config for devel/llvm11, is BE_STANDARD enabled? If not, you won't have the web assembly backend. -- Brooks On Tue, Nov 30, 2021 at 05:24:45PM +, Filippo Moretti via current wrote: > error: unable to create target: 'No available targets are compatible with > triple "wasm32-unknown-wa

Problem compiling ports

2021-11-30 Thread Filippo Moretti via current
error: unable to create target: 'No available targets are compatible with triple "wasm32-unknown-wasi"' 1 error generated. gmake[3]: *** [Makefile:380: /usr/ports/devel/wasi-libc/work/wasi-libc-ad5133410f66b93a2381db5b542aad5e0964db96/build/dlmalloc/src/dlmalloc.o] Error 1 error: unable to creat

Re: Problem compiling world

2021-09-02 Thread 内藤祐一郎
Hi. I see the same problem on my current box. Just adding ‘kconfig.h’ in the pkg-plist file works for me. Would you try the following patch? diff --git a/graphics/drm-current-kmod/pkg-plist b/graphics/drm-current-kmod/pkg-plist index 45ab906cef7c..6a77f568e058 100644 --- a/graphics/drm-current-k

Re: Problem compiling world

2021-05-29 Thread Filippo Moretti via current
Yes I doFilippo On Saturday, May 29, 2021, 12:37:46 PM GMT+2, Hans Petter Selasky wrote: On 5/29/21 10:25 AM, Filippo Moretti via current wrote: > I have the following error while compiling world:--- linux_genalloc.o ---In > file included from /usr/local/sys/modules/drm-current-kmod/l

Re: Problem compiling world

2021-05-29 Thread Hans Petter Selasky
On 5/29/21 10:25 AM, Filippo Moretti via current wrote: I have the following error while compiling world:--- linux_genalloc.o ---In file included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/src /linux_genalloc.c:35:In file included from /usr/src/sys/compat/linuxkpi/common/inclu

Problem compiling world

2021-05-29 Thread Filippo Moretti via current
I have the following error while compiling world:--- linux_genalloc.o ---In file included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/src /linux_genalloc.c:35:In file included from /usr/src/sys/compat/linuxkpi/common/include/linux/interrup t.h:35:In file included from /usr/local

Re: Problem compiling harfbuzz

2021-05-05 Thread Robert Huff
"Herbert J. Skuhra" writes: > Have you tried to (re)build devel/gobject-introspection? I think > ports list is more appropriate. Indeed. See the thread "looking for port origin for executable". That answer worked for me, and provided additional useful information.

Re: Problem compiling harfbuzz

2021-05-04 Thread Herbert J. Skuhra
On Tue, 04 May 2021 10:20:24 +0200, Filippo Moretti via freebsd-current wrote: > > Good morning,    harfbuzz did not compile with he > following error:  File > "/usr/local/lib/python3.8/site-packages/mesonbuild/modules/gnome.py", line > 449, in _get_dependencies_flags >    

Problem compiling harfbuzz

2021-05-04 Thread Filippo Moretti via freebsd-current
Good morning,    harfbuzz did not compile with he following error:  File "/usr/local/lib/python3.8/site-packages/mesonbuild/modules/gnome.py", line 449, in _get_dependencies_flags     if use_gir_args and self._gir_has_option('--extra-library'):   File "/usr/local/lib/python3.

Re: Problem compiling libgit2

2021-04-06 Thread Guido Falsi via freebsd-current
On 06/04/21 18:59, Filippo Moretti via freebsd-current wrote: After moving ports to git I had the following error while updating libgit2:===>  Extracting for libgit2-1.1.0 => ===>  Extracting for libgit2-1.1.0 => SHA256 Checksum OK for libgit2-1.1.0.tar.gz. ===>  Patching for libgit2-1.1.0 sed:

Problem compiling libgit2

2021-04-06 Thread Filippo Moretti via freebsd-current
After moving ports to git I had the following error while updating libgit2:===>  Extracting for libgit2-1.1.0 => ===>  Extracting for libgit2-1.1.0 => SHA256 Checksum OK for libgit2-1.1.0.tar.gz. ===>  Patching for libgit2-1.1.0 sed: /usr/ports/devel/libgit2/work/libgit2-1.1.0/cmake/Modules/Selec

Re: Problem compiling gcc10

2021-03-06 Thread Dimitry Andric
On 6 Mar 2021, at 11:19, Filippo Moretti wrote: > > This is the output from MAKE_JOBS_UNSAFE=yes > > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... confi

Re: Problem compiling gcc10

2021-03-06 Thread Filippo Moretti via freebsd-current
This is the output from MAKE_JOBS_UNSAFE=yes checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... configure: error: in `/usr/ports/lang/gcc10/work/.build/x86_64

Re: Problem compiling gcc10

2021-03-05 Thread Dimitry Andric
On 5 Mar 2021, at 18:19, Filippo Moretti via freebsd-current wrote: > > The following is the error while compiling on: > [root@sting /usr/ports]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD > 14.0-CURRENT #32 main-n245104-dfff1de729b: Fri Feb 26 12:08:40 CET 2021 > root@sting:/usr/obj/usr/src/a

Problem compiling gcc10

2021-03-05 Thread Filippo Moretti via freebsd-current
The following is the error while compiling on: [root@sting /usr/ports]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT #32 main-n245104-dfff1de729b: Fri Feb 26 12:08:40 CET 2021 root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING amd64 gmake[6]: *** [Makefile:1212: multi-do] Error 1gm

Problem compiling drm-current-kmod

2021-01-13 Thread Filippo Moretti
Good morning,    my system:[root@STING /usr/ports/graphics/drm-current-kmod]# uname -a FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #16 main-c255860-g2903606b606: Tue Jan 12 04:59:16 CET 2021 root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64 I get the following

Re: Problem compiling drm-current-kmod

2021-01-13 Thread Emmanuel Vadot
On Wed, 13 Jan 2021 11:45:31 +0100 Emmanuel Vadot wrote: > On Wed, 13 Jan 2021 10:32:01 + (UTC) > Filippo Moretti wrote: > > > Good morning,    my system:[root@STING > > /usr/ports/graphics/drm-current-kmod]# uname -a > > FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT

Re: Problem compiling drm-current-kmod

2021-01-13 Thread Emmanuel Vadot
On Wed, 13 Jan 2021 10:32:01 + (UTC) Filippo Moretti wrote: > Good morning,    my system:[root@STING > /usr/ports/graphics/drm-current-kmod]# uname -a > FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #16 > main-c255860-g2903606b606: Tue Jan 12 04:59:16 CET 2021 > r

Re: Problem compiling custom kernel

2021-01-11 Thread Kyle Evans
On Sat, Jan 9, 2021 at 8:34 AM Filippo Moretti wrote: > > I tried to compile my custom kernel but I did get the following error,I > enclose the beginning of dmesg output.So far I could always build kernel > STING.I did switch to git and previously I could build it without > issues.sincerelyFili

Problem compiling custom kernel

2021-01-09 Thread Filippo Moretti
I tried to compile my custom kernel but I did get the following error,I enclose the beginning of dmesg output.So far I could always build kernel STING.I did switch to git and previously I could build it without issues.sincerelyFilippo Copyright (c) 1992-2021 The FreeBSD Project. Copyright (c) 19

Re: Problem compiling custom kernel

2021-01-09 Thread David Wolfskill
On Sat, Jan 09, 2021 at 02:33:58PM +, Filippo Moretti wrote: > I tried to compile my custom kernel but I did get the following error,I > enclose the beginning of dmesg output.So far I could always build kernel > STING.I did switch to git and previously I could build it without > issues.since

Re: Problem compiling git from ports

2021-01-03 Thread Filippo Moretti
Thank you Michal,   I upgraded ruby26-gems to ruby27-gems:I did early upgraded to ruby27 but ruby-gems was inadvertently omittedsincerelyFilippo On Saturday, January 2, 2021, 10:23:13 PM GMT+1, Michal Meloun wrote: On 01.01.2021 21:19, Filippo Moretti wrote:

Re: Problem compiling git from ports

2021-01-02 Thread Michal Meloun
On 01.01.2021 21:19, Filippo Moretti wrote: It worked thank youFilippo On Friday, January 1, 2021, 5:25:10 PM GMT+1, Milan Obuch wrote: On Fri, 1 Jan 2021 16:11:52 + (UTC), Filippo Moretti wrote: I run again portmaster and I have the same error as previously reportedF

Re: Problem compiling git from ports

2021-01-01 Thread Filippo Moretti
It worked thank youFilippo On Friday, January 1, 2021, 5:25:10 PM GMT+1, Milan Obuch wrote: On Fri, 1 Jan 2021 16:11:52 + (UTC), Filippo Moretti wrote: >  > I run again portmaster and I have the same error as previously > reportedFilippo On Friday, January 1, 2021, 4:05:18 PM GM

Re: Problem compiling git from ports

2021-01-01 Thread Filippo Moretti
I run again portmaster and I have the same error as previously reportedFilippo On Friday, January 1, 2021, 4:05:18 PM GMT+1, Filippo Moretti wrote: Ufs It exits with a different error: ===> Installing contributed scripts /bin/mkdir -p /usr/ports/devel/git/work-default/stage/usr/loca

Re: Problem compiling git from ports

2021-01-01 Thread Milan Obuch
On Fri, 1 Jan 2021 16:11:52 + (UTC), Filippo Moretti wrote: > > I run again portmaster and I have the same error as previously > reportedFilippo On Friday, January 1, 2021, 4:05:18 PM GMT+1, Filippo > Moretti wrote: > Ufs > It exits with a different error: > ===> Installing contributed

Problem compiling git from ports

2021-01-01 Thread Filippo Moretti
I could not update git from 2.29 in my system [root@STING /usr/ports/devel/git]# uname -a FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #14 main-c255423-gee938b20335: Wed Dec 30 10:41:00 CET 2020 root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64 This is the error which can be dup

Re: Problem compiling git from ports

2021-01-01 Thread Mateusz Guzik
What filesystem is this? Does it work if you sysctl vfs.cache_fast_lookup=0 ? On 1/1/21, Filippo Moretti wrote: > I could not update git from 2.29 in my system > [root@STING /usr/ports/devel/git]# uname -a > FreeBSD STING 13.0-CURRENT FreeBSD 13.0-CURRENT #14 > main-c255423-gee938b20335: Wed Dec

Re: Problem compiling world amd64

2020-09-18 Thread Filippo Moretti
Thank you very much buildworld worked properly sincerelyFilippo On Friday, September 18, 2020, 10:20:58 AM GMT+2, Yasuhiro KIMURA wrote: From: Filippo Moretti Subject: Problem compiling world amd64 Date: Fri, 18 Sep 2020 07:57:40 + (UTC) > [filippo@sting ~]$ uname -a > F

Problem compiling world amd64

2020-09-18 Thread Filippo Moretti
[filippo@sting ~]$ uname -a FreeBSD sting 13.0-CURRENT FreeBSD 13.0-CURRENT #11 r365578: Thu Sep 10 19:38:51 CEST 2020 root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64 I have the following error during buildworld:ed '1s/\/bin\//\/rescue\//' /usr/src/rescue/rescue/../../sbin/reboot/ne

Re: Problem compiling world amd64

2020-09-18 Thread Yasuhiro KIMURA
From: Filippo Moretti Subject: Problem compiling world amd64 Date: Fri, 18 Sep 2020 07:57:40 + (UTC) > [filippo@sting ~]$ uname -a > FreeBSD sting 13.0-CURRENT FreeBSD 13.0-CURRENT #11 r365578: Thu Sep 10 > 19:38:51 CEST 2020 root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING 

Re: Problem compiling chromium

2020-08-09 Thread John-Mark Gurney
Filippo Moretti wrote this message on Sun, Aug 02, 2020 at 08:23 +: > This is the last eror I get attempting to compile chromium on amd64 arch > R363570[263/38159] python ../../mojo/public/tools/mojom/mojom_parser.py > --input-root /usr/ports/www/chromium/work/chromium-84.0.4147.105/ > --inp

Problem compiling chromium

2020-08-02 Thread Filippo Moretti
This is the last eror I get attempting to compile chromium on amd64 arch R363570[263/38159] python ../../mojo/public/tools/mojom/mojom_parser.py --input-root /usr/ports/www/chromium/work/chromium-84.0.4147.105/ --input-root /usr/ports/www/chromium/work/chromium-84.0.4147.105/out/Release/gen --o

Re: Problem compiling Chromium

2020-06-08 Thread Filippo Moretti
Thank you,  compile error follows: [829/38881] python ../../chrome/test/chromedriver/embed_extension_in_cpp.py --dromedriver/chrome ../../chrome/test/chromedriver/extension/background.js ../../tension/manifest.json FAILED: gen/chrome/test/chromedriver/chrome/embedded_automation

Re: Problem compiling Chromium

2020-06-07 Thread Kevin Oberman
On Sun, Jun 7, 2020 at 9:49 AM bob prohaska wrote: > Don't know about AMD, but on ARM failures that resemble this are > common. In some cases the actual error message is tens or a hundred > lines prior to the last make output. > > If you search for the string Error: or maybe error: does anything

Problem compiling Chromium

2020-06-07 Thread Filippo Moretti
Good evening, FreeBSD sting 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r361787: Sun Jun  7 15:02:09 CEST 2020 root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64 the build fails with the following message/common/extensions/api/action.json ../../chrome/common/extension

Re: Problem compiling Chromium

2020-06-07 Thread bob prohaska
Don't know about AMD, but on ARM failures that resemble this are common. In some cases the actual error message is tens or a hundred lines prior to the last make output. If you search for the string Error: or maybe error: does anything show up? Including the colon : helps to reduce irrelevant hit

Re: Problem compiling rust: observations on swap: GNU tar

2018-10-15 Thread Cy Schubert
In message <97680f3e-fb00-abc7-81d5-c61c9cae7...@gmail.com>, Graham Perrin writ es: > On 14/10/2018 22:34, Cy Schubert wrote: > > > Set TAR in make.conf to gnu tar from ports. Some tarballs will cause bsdtar > to exhaust memory and swap. There was discussion a while ago suggesting this > is a bu

Problem compiling rust: observations on swap: GNU tar

2018-10-15 Thread Graham Perrin
On 14/10/2018 22:34, Cy Schubert wrote: > Set TAR in make.conf to gnu tar from ports. Some tarballs will cause bsdtar > to exhaust memory and swap. There was discussion a while ago suggesting this > is a bug in vmm. Thanks! My make.conf for poudriere: root@momh167-gjp4-hpelitebook8570p-freebs

RE: Problem compiling rust: observations on swap

2018-10-14 Thread Cy Schubert
. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -Original Message- From: Graham Perrin Sent: 14/10/2018 15:19 To: freebsd-current@freebsd.org Subject: Problem compiling rust: observations on swap On 06/10/2018 23:41, Rebecca Cran wrote: > On 10/6/1

Problem compiling rust: observations on swap

2018-10-14 Thread Graham Perrin
On 06/10/2018 23:41, Rebecca Cran wrote: > On 10/6/18 6:40 AM, Greg V wrote: > >> BTW, this error message doesn't say much, but if cargo fails, you >> might be out of memory. > > I was going to suggest being out of memory too. I've seen the rust build > cause my system to run out of all 32GB RAM a

Re: Problem compiling rust

2018-10-06 Thread Rebecca Cran
On 10/6/18 6:40 AM, Greg V wrote: > > BTW, this error message doesn't say much, but if cargo fails, you > might be out of memory. I was going to suggest being out of memory too. I've seen the rust build cause my system to run out of all 32GB RAM and 2GB swap. -- Rebecca Cran _

Re: Problem compiling rust

2018-10-06 Thread Greg V
On Sat, Oct 6, 2018 at 3:26 PM, Filippo Moretti wrote: 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 ext

Problem compiling rust

2018-10-06 Thread Filippo Moretti
  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  e

Re: Problem compiling rust

2018-04-19 Thread Bryan Drewery
On 4/17/18 10:25 AM, Filippo Moretti wrote: > I have the folloing error while compiling rust on i386 current of April the > 9th It looks like the normal bootstrap bug with the ino64 changes but is fine on my amd64 system. Perhaps I missed something for i386 support. Are you able to build lang/rus

Problem compiling rust

2018-04-17 Thread Filippo Moretti
I have the folloing error while compiling rust on i386 current of April the 9th rust_error Description: Binary data ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: Problem compiling akonadi

2017-02-21 Thread Trond Endrestøl
On Tue, 21 Feb 2017 09:00-, Filippo Moretti wrote: > While trying to compile akonadi I get the following error: > ===> Installing for qtchooser-39===> Checking if qtchooser already > installed===> Registering installation for qtchooser-39 as > automaticInstalling qtchooser-39...pkg-static:

Problem compiling akonadi

2017-02-21 Thread Filippo Moretti
While trying to compile akonadi I get the following error: ===> Installing for qtchooser-39===> Checking if qtchooser already installed===> Registering installation for qtchooser-39 as automaticInstalling qtchooser-39...pkg-static: qtchooser-39 conflicts with qt4-dbus-4.8.7 (installs

Problem compiling akonadi

2017-02-20 Thread Filippo Moretti
While trying to compile akonadi I get the following error: ===> Installing for qtchooser-39===> Checking if qtchooser already installed===> Registering installation for qtchooser-39 as automaticInstalling qtchooser-39...pkg-static: qtchooser-39 conflicts with qt4-dbus-4.8.7 (installs files into

gobject-introspection-1.36.0_1 problem compiling causing xorg to fail

2013-08-30 Thread biddut . mitra
  CC   gthash_test-gthash-test.o   CCLD gthash-test   CC   gi_dump_types-gdump.o   CC   gi_dump_types-gi-dump-types.o   CCLD gi-dump-types   CC   glib_print-glib-print.o   CCLD glib-print   GEN  g-ir-scanner   GEN  g-ir-annotation-tool   GISCAN GLib-2.0.gir ERROR

Re: problem compiling cuse4bsd-kmod

2011-12-05 Thread Hans Petter Selasky
Hi current users, Regarding the MK_CTF=XXX changes, did you check that code is still compliant for external ports? --HPS On Monday 05 December 2011 14:39:56 Robert Huff wrote: > Hello: > When trying to update I get: > > ===> Building for cuse4bsd-kmod-0.1.21_2 > make -f > /data/port-wor

Re: Problem compiling libs after pass to current

2011-11-28 Thread Maciej Milewski
Dnia poniedziałek, 28 listopada 2011 18:55:04 ZaRiuS KRiNG pisze: > Ok, the second know how make, but the first no. > > How can set new uname -r in the environment? Sorry but in some things need > a lot of experience, and for that try use current > > About what programs got the fail? Chromium and

Re: Problem compiling libs after pass to current

2011-11-28 Thread ZaRiuS KRiNG
Ok, the second know how make, but the first no. How can set new uname -r in the environment? Sorry but in some things need a lot of experience, and for that try use current About what programs got the fail? Chromium and Abiword, with one, 2-3 with second just one. But make that, pkg_add -r and co

Re: Problem compiling libs after pass to current

2011-11-28 Thread Maciej Milewski
Dnia niedziela, 27 listopada 2011 19:59:44 ZaRiuS KRiNG pisze: > Hi! is my first post here and have a little problem try to google some and > don't find any of value. > > A week ago compile the src of current, and after that in any new port i > install, if compile before any lib, don't work, i nee

Re: Problem compiling libs after pass to current

2011-11-27 Thread Benjamin Kaduk
On Sun, 27 Nov 2011, ZaRiuS KRiNG wrote: Hi! is my first post here and have a little problem try to google some and don't find any of value. A week ago compile the src of current, and after that in any new port i install, if compile before any lib, don't work, i need to install pkg from reposit

Problem compiling libs after pass to current

2011-11-27 Thread ZaRiuS KRiNG
Hi! is my first post here and have a little problem try to google some and don't find any of value. A week ago compile the src of current, and after that in any new port i install, if compile before any lib, don't work, i need to install pkg from repository of that lib and continue compiling the p

Re: Problem compiling kernel

2011-11-07 Thread Garrett Cooper
On Mon, Nov 7, 2011 at 1:57 AM, Alexander Yerenkow wrote: > > > 2011/11/7 Garrett Cooper >> >> On Nov 6, 2011, at 11:57 PM, Peter Jeremy wrote: >> >> > On 2011-Nov-06 17:41:49 +0200, Alexander Yerenkow >> > wrote: >> >> And problem com

Re: Problem compiling kernel

2011-11-07 Thread Alexander Yerenkow
2011/11/7 Garrett Cooper > On Nov 6, 2011, at 11:57 PM, Peter Jeremy wrote: > > > On 2011-Nov-06 17:41:49 +0200, Alexander Yerenkow > wrote: > >> And problem compiling kernel for amd64 arch. > >> > >> I attached full log: > >> > >> htt

Re: Problem compiling kernel

2011-11-07 Thread Garrett Cooper
On Nov 6, 2011, at 11:57 PM, Peter Jeremy wrote: > On 2011-Nov-06 17:41:49 +0200, Alexander Yerenkow wrote: >> And problem compiling kernel for amd64 arch. >> >> I attached full log: >> >> http://www.box.net/shared/juajg1o2lg1mxbht5x9b > > It looks like

Re: Problem compiling kernel

2011-11-07 Thread Peter Jeremy
On 2011-Nov-06 17:41:49 +0200, Alexander Yerenkow wrote: >And problem compiling kernel for amd64 arch. > >I attached full log: > >http://www.box.net/shared/juajg1o2lg1mxbht5x9b It looks like you did a parallel - in which case the actual error is buried somewhere in that output.

Problem compiling kernel

2011-11-06 Thread Alexander Yerenkow
Date: 2011-11-06 09:50:25 +0200 (вс, 06 ноя 2011) And problem compiling kernel for amd64 arch. I attached full log: http://www.box.net/shared/juajg1o2lg1mxbht5x9b I find somewhere that to build kernel I need to have world build; So, world built just fine before I tried to build kernel. Also

Re: Problem compiling -current on 4.6-RELEASE

2002-07-25 Thread Ruslan Ermilov
On Thu, Jul 25, 2002 at 02:45:15PM +0200, Sheldon Hearn wrote: > On (2002/07/25 11:45), Martin Bundgaard wrote: > > > I have a problem. When trying to do a 'make buildworld' on a (freshly > > fetched) -current source-tree, I quickly get an error: > > Other people have pointed out the cause of th

Re: Problem compiling -current on 4.6-RELEASE

2002-07-25 Thread Sheldon Hearn
On (2002/07/25 11:45), Martin Bundgaard wrote: > I have a problem. When trying to do a 'make buildworld' on a (freshly > fetched) -current source-tree, I quickly get an error: Other people have pointed out the cause of the problem. However, please note for future reference that what you're doin

Re: Problem compiling -current on 4.6-RELEASE

2002-07-25 Thread Martin Bundgaard
> The tar directory should really be in the attic. I guess you forgot to > use -P when using cvs update/checkout. You're right, pruning would have resolved the problem, but is there any reason for the empty directories to be there in the first place? -mb To Unsubscribe: send mail to [EMAIL PR

Re: Problem compiling -current on 4.6-RELEASE

2002-07-25 Thread Ruslan Ermilov
On Thu, Jul 25, 2002 at 11:45:21AM +0200, Martin Bundgaard wrote: > > (This has already been posted on questions, but I got no replies.) > > Hi. > > I have a problem. When trying to do a 'make buildworld' on a (freshly > fetched) -current source-tree, I quickly get an error: > > --- > ===> gnu

Re: Problem compiling -current on 4.6-RELEASE

2002-07-25 Thread Stefan Farfeleder
On Thu, Jul 25, 2002 at 11:45:21AM +0200, Martin Bundgaard wrote: <...> > ===> gnu/usr.bin/tar > rm -f tar addext.o argmatch.o backupfile.o basename.o dirname.o error.o > exclude.o full-write.o getdate.o getline.o getopt.o getopt1.o getstr.o > hash.o human.o mktime.o modechange.o prepargs.o prin

Problem compiling -current on 4.6-RELEASE

2002-07-25 Thread Martin Bundgaard
(This has already been posted on questions, but I got no replies.) Hi. I have a problem. When trying to do a 'make buildworld' on a (freshly fetched) -current source-tree, I quickly get an error: --- ===> gnu/usr.bin/tar rm -f tar addext.o argmatch.o backupfile.o basename.o dirname.o error.o e

Problem compiling

2001-01-15 Thread Adriaan Erasmus
Hi,   My box hangs up solid when recompiling my kernel to add pcm driver. I got the latest src tree though cvsup and I followed the standard procedure to recompile my new kernel to include pcm   I can do a /usr/sbin/config MYNEWKERNEL Then in /usr/src/sys/compile/MYNEWKERNEL I can do make d

Re: Problem Compiling Kernel

2000-11-21 Thread Michael Brune
"Brune, Michael" wrote: > I CVSup'ed the sources today, built and installed world and everything > was fine. When I tried to compile the kernel, I recieve this error when > I do the 'make depend' > > ./aicasm -nostdinc -I- -I. -I../../ -I../../../include > -I../../contrib/dev/acpica/Subsystem/Inc

Problem Compiling Kernel

2000-11-20 Thread Michael Brune
I CVSup'ed the sources today, built and installed world and everything was fine. When I tried to compile the kernel, I recieve this error when I do the 'make depend' ./aicasm -nostdinc -I- -I. -I../../ -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -I../../cam/scsi -I../../dev/a