Hello,
On head with ports of head to the port devel/android-tools-simpleperf
fails to build with the error:
...
--- read_elf.o ---
In file included from read_elf.cpp:34:
In file included from /usr/local/llvm10/include/llvm/ADT/StringRef.h:12:
/usr/local/llvm10/include/llvm/ADT/STLExtras.h:559:49
Hi, list
math/suitesparse failed at linking
libclang_rt.profile-x86_64.a:
gmake[5]: Leaving directory
'/var/ports/work/usr/ports/math/suitesparse/work/SuiteSparse-5.8.1/Mongoose/build'
gmake[4]: *** [CMakeFiles/Makefile2:151:
CMakeFiles/mongoose_unit_test_edgesep.dir/all] Error 2
gmake[4]: ***
On Wed, Dec 02, 2020 at 11:20:06AM EST, Thierry Thomas wrote:
> But I´m wondering why a dependency on a port of llvm is needed (let´s
> say 10 or 11), even when the compiler in base has the same version.
>From my experience ports that needed 8 (and I would assume for other
base versions) but can't
Thierry Thomas writes:
> Le mer. 2 déc. 20 à 16:55:33 +0100, tech-lists
> écrivait :
>
>> Hi,
>
>> Is there a minimum version/maximum version listed in dependencies that
>> one can filter on? Is it the case that some ports want eg llvm8 and
>> *only* that version? Is llvm11 incompatible with
On Wed, Dec 02, 2020 at 05:20:06PM +0100, Thierry Thomas wrote:
But I´m wondering why a dependency on a port of llvm is needed (let´s
say 10 or 11), even when the compiler in base has the same version.
I've often wondered that as well
--
J.
signature.asc
Description: PGP signature
Adam Weinberger writes:
> While the end-user package burden is significantly lower, I suspect
> very, very few users actually make use of the gtk3 frontend-specific
> features. Honestly, the plain x11 frontend is probably sufficient for
> the vast majority of gvim users (it's what I test with), a
Le mer. 2 déc. 20 à 16:55:33 +0100, tech-lists
écrivait :
> Hi,
> Is there a minimum version/maximum version listed in dependencies that
> one can filter on? Is it the case that some ports want eg llvm8 and
> *only* that version? Is llvm11 incompatible with llvm9 for example?
Yes, some port
On Wed, Dec 02, 2020 at 04:17:56PM +0100, Jan Beich wrote:
Jan Beich writes:
If you don't have JS-capable browser yet simply filter .poudriere.* files e.g.,
$ poudriere bulk -j 122amd64 -z test editors/vim
^C
$ grep \^devel/llvm
/poudriere/data/logs/bulk/122amd64-default-test/latest/.poudrie
On Wed, Dec 02, 2020 at 06:49:54AM -0800, David Wolfskill wrote:
My local "make index" had no issues with a ports tree (head@r556814),
running on stable/12@r368270.
forgot to mention, this machine runs -current.
After running an update:
[...]
Generating INDEX-13
[...]
--- describe.x11-wm ---
Jan Beich writes:
> If you don't have JS-capable browser yet simply filter .poudriere.* files
> e.g.,
>
> $ poudriere bulk -j 122amd64 -z test editors/vim
> ^C
> $ grep \^devel/llvm
> /poudriere/data/logs/bulk/122amd64-default-test/latest/.poudriere.ports.queued
> devel/llvm10 llvm10-10.0.1_3 g
On Wed, Dec 02, 2020 at 06:49:54AM -0800, David Wolfskill wrote:
On Wed, Dec 02, 2020 at 02:41:17PM +, tech-lists wrote:
Hi,
I'm getting these errors when make index runs on latest ports:
[...]
Warning: Duplicate INDEX entry: ocaml-nox11-4.05.0_1
Warning: Duplicate INDEX entry: mc-nox11-4.8
Matthias Apitz writes:
> I have done what Jan suggested and for editors/vim it only compiled llvm10;
> but now for some other dependency, some 1000 ports later, it is making
> llvm11 also; do I have any chance based on the poudriere ports list to
> see, which port is now pulling in llvm11?
See "
On Wed, Dec 02, 2020 at 02:41:17PM +, tech-lists wrote:
> Hi,
>
> I'm getting these errors when make index runs on latest ports:
> [...]
> Warning: Duplicate INDEX entry: ocaml-nox11-4.05.0_1
> Warning: Duplicate INDEX entry: mc-nox11-4.8.24
> [...]
>
> Should I raise this in bugzilla?
>
> t
Hi,
I'm getting these errors when make index runs on latest ports:
[...]
Warning: Duplicate INDEX entry: ocaml-nox11-4.05.0_1
Warning: Duplicate INDEX entry: mc-nox11-4.8.24
[...]
Should I raise this in bugzilla?
thanks,
--
J.
signature.asc
Description: PGP signature
El día martes, diciembre 01, 2020 a las 02:25:38p. m. -0700, Adam Weinberger
escribió:
> Jan's answer is completely correct about why both get pulled in and
> that it's possible to avoid concurrent llvms by setting
> DEFAULT_VERSIONS.
>
> The default vim setup involves the gtk3 frontend. The lis
15 matches
Mail list logo
