Re: Would like to use ARCH (uname -p) but it's not always correct (e.g. arm64)
Hello Tatsuki!
I't seems that you dig it into source configs, I will take a look into this
too.
I was talking using ARCH (and OSREL, OSVERSION, etc) in a more generic way
and only related to ports framework to easier some tasks like dinamic plist
for some files that change with this vars:
---
PLIST_SUB= ARCH=${ARCH}
plist:
libexec/NsCDE/FreeBSD_%%ARCH%%/colorpicker
---
---
PLIST_SUB+= SHLIB_SHVER="${DISTVERSION:R}" \
SHLIB_VER="${DISTVERSION}"
plist:
lib/root/libRHTTPSniff.so.%%SHLIB_SHVER%%
lib/root/libRHTTPSniff.so.%%SHLIB_VER%%
---
So my question is why people often choose a hack to `uname -m` instead of
using ARCH (uname -p).
Thanks
Tatsuki Makino escreveu no dia quinta,
29/12/2022 à(s) 21:41:
> Tatsuki Makino wrote on 2022/12/30 06:17:
> > For x11-wm/nscde, this is present in ${WRCSRC}/configure.ac.
> >
> > OS_PLUS_MACHINE_ARCH=`uname -sm | tr ' ' '_'`
> > AC_SUBST(OS_PLUS_MACHINE_ARCH)
> >
>
> Then, in the case of security/zeek, it seems that uname -m is used in
> zeek-5.0.4/cmake/GetArchitecture.cmake of distfile.
> That's also where FreeBSD gets lowercased.
>
> Regards.
>
>
--
Nuno Teixeira
FreeBSD Committer (ports)
Re: Would like to use ARCH (uname -p) but it's not always correct (e.g. arm64)
(...)
A good example:
"x11-wm/nscde: fix packaging when uname -m != uname -p"
https://cgit.freebsd.org/ports/commit/?id=4ae82fd2ee2059cd9ee0ec99bd6fd8062cd5dbdd
Nuno Teixeira escreveu no dia sexta, 30/12/2022 à(s)
08:22:
> Hello Tatsuki!
>
> I't seems that you dig it into source configs, I will take a look into
> this too.
>
> I was talking using ARCH (and OSREL, OSVERSION, etc) in a more generic way
> and only related to ports framework to easier some tasks like dinamic plist
> for some files that change with this vars:
>
> ---
> PLIST_SUB= ARCH=${ARCH}
> plist:
> libexec/NsCDE/FreeBSD_%%ARCH%%/colorpicker
> ---
> ---
> PLIST_SUB+= SHLIB_SHVER="${DISTVERSION:R}" \
>SHLIB_VER="${DISTVERSION}"
> plist:
> lib/root/libRHTTPSniff.so.%%SHLIB_SHVER%%
> lib/root/libRHTTPSniff.so.%%SHLIB_VER%%
> ---
>
> So my question is why people often choose a hack to `uname -m` instead of
> using ARCH (uname -p).
>
> Thanks
>
> Tatsuki Makino escreveu no dia quinta,
> 29/12/2022 à(s) 21:41:
>
>> Tatsuki Makino wrote on 2022/12/30 06:17:
>> > For x11-wm/nscde, this is present in ${WRCSRC}/configure.ac.
>> >
>> > OS_PLUS_MACHINE_ARCH=`uname -sm | tr ' ' '_'`
>> > AC_SUBST(OS_PLUS_MACHINE_ARCH)
>> >
>>
>> Then, in the case of security/zeek, it seems that uname -m is used in
>> zeek-5.0.4/cmake/GetArchitecture.cmake of distfile.
>> That's also where FreeBSD gets lowercased.
>>
>> Regards.
>>
>>
>
> --
> Nuno Teixeira
> FreeBSD Committer (ports)
>
--
Nuno Teixeira
FreeBSD Committer (ports)
Re: [zstd-sys 2.0.1+zstd.1.5.2] crate failing on arm64
Hello Jan,
I've opened an issue at:
https://github.com/bytecodealliance/wasmtime/issues/5499
Thanks
Jan Beich escreveu no dia sábado, 26/11/2022 à(s)
14:56:
> Nuno Teixeira writes:
>
> > From the log it seems [zstd-sys 2.0.1+zstd.1.5.2] crate failing.
>
> Unlikely if it shows up after "warning: build failed, waiting for other
> jobs to finish..."
> due to MAKE_JOBS_NUMBER=2 in poudriere log.
>
> >
> https://pkg-status.freebsd.org/ampere2/data/main-arm64-default/pf323e9d40f68_s41be508d31/logs/lapce-0.2.4.log
> [...]
> > [io-lifetimes 0.7.3] error[E0554]: `#![feature]` may not be used on the
> stable release channel
> > [io-lifetimes 0.7.3] --> :1:1
> > [io-lifetimes 0.7.3] |
> > [io-lifetimes 0.7.3] 1 | #![feature(rustc_attrs)]
> > [io-lifetimes 0.7.3] |
> > [io-lifetimes 0.7.3]
> > [io-lifetimes 0.7.3] error: aborting due to previous error
>
> Such errors don't abort build and also show up on amd64. If those ever
> become a problem check if adding CARGO_ENV+=RUSTC_BOOTSTRAP=1 helps.
>
> > error: unsupported platform
> >-->
> /wrkdirs/usr/ports/editors/lapce/work/lapce-0.2.4/cargo-crates/wasmtime-runtime-1.0.2/src/traphandlers/
> unix.rs:232:13
> > |
> > 232 | compile_error!("unsupported platform");
> > | ^^
> >
> > error[E0308]: mismatched types
> >-->
> /wrkdirs/usr/ports/editors/lapce/work/lapce-0.2.4/cargo-crates/wasmtime-runtime-1.0.2/src/traphandlers/
> unix.rs:167:73
> > |
> > 167 | unsafe fn get_pc_and_fp(cx: *mut libc::c_void, _signum:
> libc::c_int) -> (*const u8, usize) {
> > | -
> ^^ expected tuple, found `()`
> > | |
> > | implicitly returns `()` as its body has no tail or
> `return` expression
> > |
> > = note: expected tuple `(*const u8, usize)`
> > found unit type `()`
> >
> > For more information about this error, try `rustc --explain E0308`.
> > error: could not compile `wasmtime-runtime` due to 2 previous errors
>
> Looks like
> https://github.com/bytecodealliance/wasmtime/blob/main/crates/runtime/src/traphandlers/unix.rs
> needs something like
> https://github.com/wasmerio/wasmer/blob/dcfdea76999a/lib/vm/src/trap/traphandlers.rs#L302-L304
>
--
Nuno Teixeira
FreeBSD Committer (ports)
Unmaintained FreeBSD ports which are out of date
Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. Please consider also adopting this port. If any ports have already been updated, you can safely ignore the entry. An e-mail will not be sent again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ multimedia/atomicparsley| 20210114.184825.1dbe1be| 20221229.172126.d813aa6 +-+ textproc/redisearch | 2.2.10 | v2.6.4 +-+ x11-toolkits/gnustep-back | 0_28_0 | back-0_30_0 +-+ x11-toolkits/gnustep-gui| 0_28_0 | gui-0_30_0 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
Ports INDEX fails to build correctly
Hi,
the ports' INDEX fails to build correctly:
$ make index
[...]
--- describe.x11-wm ---
make_index: /usr/ports/devel/py-monkeytype: no entry for
/usr/ports/devel/py-libcst03
Done.
$
The trouble is that there is no devel/py-libcst03 port yet. A (untested)
patch is attached.
Best
Philippdiff --git a/devel/Makefile b/devel/Makefile
index 907928eaa837..bb468ee5db5f 100644
--- a/devel/Makefile
+++ b/devel/Makefile
@@ -4762,6 +4762,7 @@
SUBDIR += py-lazy
SUBDIR += py-lazy-object-proxy
SUBDIR += py-libcst
+SUBDIR += py-libcst03
SUBDIR += py-libioc
SUBDIR += py-libpeas
SUBDIR += py-libplist
diff --git a/devel/py-libcst03/Makefile b/devel/py-libcst03/Makefile
new file mode 100644
index ..34dc02559b46
--- /dev/null
+++ b/devel/py-libcst03/Makefile
@@ -0,0 +1,24 @@
+PORTNAME= libcst03
+PORTVERSION= 0.3.23
+CATEGORIES=devel python
+MASTER_SITES= CHEESESHOP
+PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
+
+MAINTAINER=sunp...@freebsd.org
+COMMENT= Concrete syntax tree with AST-like properties
+WWW= https://github.com/Instagram/LibCST
+
+LICENSE= MIT
+LICENSE_FILE= ${WRKSRC}/LICENSE
+
+BUILD_DEPENDS=
${PYTHON_PKGNAMEPREFIX}setuptools_scm>=0:devel/py-setuptools_scm@${PY_FLAVOR}
+RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}yaml>=5.2:devel/py-yaml@${PY_FLAVOR} \
+
${PYTHON_PKGNAMEPREFIX}typing-extensions>=3.7.4.2:devel/py-typing-extensions@${PY_FLAVOR}
\
+
${PYTHON_PKGNAMEPREFIX}typing-inspect>=0.4.0:devel/py-typing-inspect@${PY_FLAVOR}
+
+USES= python:3.6+
+USE_PYTHON=autoplist concurrent distutils
+
+NO_ARCH= yes
+
+.include
diff --git a/devel/py-libcst03/distinfo b/devel/py-libcst03/distinfo
new file mode 100644
index ..2425179ba82f
--- /dev/null
+++ b/devel/py-libcst03/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1638556576
+SHA256 (libcst-0.3.23.tar.gz) =
330f9082a309bad808e283e80845a843200303bb256690185b98ca458a62c4f8
+SIZE (libcst-0.3.23.tar.gz) = 579195
diff --git a/devel/py-libcst03/pkg-descr b/devel/py-libcst03/pkg-descr
new file mode 100644
index ..74375e1c900e
--- /dev/null
+++ b/devel/py-libcst03/pkg-descr
@@ -0,0 +1,10 @@
+LibCST is a Concrete Syntax Tree (CST) parser and serializer library for
Python.
+
+LibCST parses Python source code as a CST tree that keeps all formatting
details
+(comments, whitespaces, parentheses, etc). It's useful for building automated
+refactoring (codemod) applications and linters.
+
+LibCST creates a compromise between an Abstract Syntax Tree (AST) and a
+traditional Concrete Syntax Tree (CST). By carefully reorganizing and naming
+node types and fields, we've created a lossless CST that looks and feels like
an
+AST.
Re: Ports INDEX fails to build correctly
Hi! > the ports' INDEX fails to build correctly: > > $ make index > [...] > --- describe.x11-wm --- > make_index: /usr/ports/devel/py-monkeytype: no entry for > /usr/ports/devel/py-libcst03 > Done. > $ > > The trouble is that there is no devel/py-libcst03 port yet. A (untested) > patch is attached. It was added here: https://lists.freebsd.org/archives/dev-commits-ports-all/2022-December/048636.html -- p...@freebsd.org +49 171 3101372 Now what ?
