O. Hartmann ohartmann at walstatt.org wrote on
Sun Oct 15 16:37:58 UTC 2017 :
> . . .
> file
> /usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-avx.bc:No
> such file or directory pkg-static: Unable to access
> . . .
> find ./ -name "*freebsd12.0-avx.bc" -prin
Hmmm This nastygram from pkg-fallout arrived overnight. However,
as far as I can tell, this is complaining about mail/spamassassin
packages being broken, rather than any problem with mail/sa-utils itself.
However, having checked the Build URL, poudriere seems to think
spamassassin built per
Hello.
I'm porting an application (DLib, https://reviews.freebsd.org/D12559) that
uses BLAS and LAPACK, and I have some questions.
1. Is there any pure C implementation that does not require Fortran
compiler?
2. My application looks for cblas_ddot function in BLAS library, but the
default librar
I'm trying to port some software that keeps failing when it tries to find a
config.h.
I know the config.h file is there but I think the compilation is failing
because it's trying to build ltdl and freebsd doesn't need that since
freebsd already has dlopen in libc.
Which configure flag could I try
On Mon, 16 Oct 2017 04:19:24 +
blubee blubeeme wrote:
> I just ran into this issue yesterday myself.
>
> To find the tagname I went to the project in githib, looked at their
> committed files and found the one with the latest date.
>
> Click on that file, then you'll see three buttons in th
I just ran into this issue yesterday myself.
To find the tagname I went to the project in githib, looked at their
committed files and found the one with the latest date.
Click on that file, then you'll see three buttons in the upper right hand
side;
raw, blame, history.
Click on history and you'
On 10/15/2017 11:41, Baptiste Daroussin wrote:
On Sun, Oct 15, 2017 at 06:15:24PM +, Yuri wrote:
Uses/ssl.mk allows SSL_DEFAULT=base. I know this has been discussed here
before, but why is this even allowed? If some ports are built with
SSL_DEFAULT=base, and some with SSL_DEFAULT=openssl, th
On 10/15/17 12:47, O. Hartmann wrote:
all right, that is what I picked up from the porter's handbook, but I must have
overlooked the note (if there is anything like that) regarding the sufficient
first 7
digits.
If you look at other ports, most use 7 digits.
I tried this earlier (yes, and I
Am Sun, 15 Oct 2017 12:35:49 -0700
Yuri schrieb:
> On 10/15/17 12:19, O. Hartmann wrote:
> > Out of the blue there is a so called GH_TAGNAME. It reflects some late
> > commit/revision
> > number on an archive. Now I try to figure out how to find such a
> > GH_TAGNAME. Since I
> > do not push st
On 10/15/17 12:19, O. Hartmann wrote:
Out of the blue there is a so called GH_TAGNAME. It reflects some late
commit/revision
number on an archive. Now I try to figure out how to find such a GH_TAGNAME.
Since I do
not push stuff to github, it is some new playfield and there might be an easy
way
I'm officially maintaining a small port, devele/opencl. These are header files
hosted at
Khronos and can be downloaded easily. Now I'm growing gray hair because OpenCL
headers
have been pushed to version 2.2 and I need to update the port.
Out of the blue there is a so called GH_TAGNAME. It refle
On Sun, Oct 15, 2017 at 06:15:24PM +, Yuri wrote:
> Uses/ssl.mk allows SSL_DEFAULT=base. I know this has been discussed here
> before, but why is this even allowed? If some ports are built with
> SSL_DEFAULT=base, and some with SSL_DEFAULT=openssl, this will obviously
> cause conflicts when two
Uses/ssl.mk allows SSL_DEFAULT=base. I know this has been discussed here
before, but why is this even allowed? If some ports are built with
SSL_DEFAULT=base, and some with SSL_DEFAULT=openssl, this will obviously
cause conflicts when two incompatible openssl libraries will be mapped
into the sa
A port (lang/pocl), of which I am the official maintainer, fails to build with
recent
12-CURRENT and recent 11-STABLE:
[...]
===> Registering installation for pocl-0.14
pkg-static: Unable to access
file
/usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-avx.
I am running into some compiling/ linking errors further along in my
porting process so I re-checked the configure step.
It seems to be that the issue is related to dlopen.
What configure options can I pass to use the standard FreeBSD dlopen
equivalent calls?
The gmake error occurs here:
gmake[
Hey
That was cool and solved the issue real fast!
Thanks you
On Sun, Oct 15, 2017 at 7:30 PM, Romain Tartière wrote:
> On Sun, Oct 15, 2017 at 07:23:49PM +0800, blubee blubeeme wrote:
> > trigger happy missed sending the error:
> >
> > format=`echo tmp/tag.hpp | sed 's|.*\.\([^.]*\)$|\1|'`; \
On Sun, Oct 15, 2017 at 07:23:49PM +0800, blubee blubeeme wrote:
> trigger happy missed sending the error:
>
> format=`echo tmp/tag.hpp | sed 's|.*\.\([^.]*\)$|\1|'`; \
> sed -n \
> -e "/^/{ /-->/d; s|^$|//|p; s|^|//|p; }' lib/tag.xml >
> tmp/tag.hpp; \
> xsltproc --stringparam format $for
trigger happy missed sending the error:
format=`echo tmp/tag.hpp | sed 's|.*\.\([^.]*\)$|\1|'`; \
sed -n \
-e "/^/{ /-->/d; s|^$|//|p; s|^|//|p; }' lib/tag.xml >
tmp/tag.hpp; \
xsltproc --stringparam format $format ./lib/tag.xsl lib/tag.xml >>
tmp/tag.hpp
format=`echo lib/tag.cpp | sed 's|
I figured out the configure script part by adding: GNU_CONFIGURE= yes
and that works fine so far.
I also found that I could use build_depends macro and I added this line
below
BUILD_DEPENDS= gsed:textproc/gsed
but looking at the output command, the build steps is still attempting to
use regular
I'm trying to port some code from github to FreeBSD but I run into a few
issues;
1) The project needs to use gnu make, gnu sed and other gnu tools since it
uses the gnu version of @< for variable names
2) The project also uses autoreconf because there's .am and .in files
I can pull the files down
If you’r using the Gitea port, the update to 1.2.0 will require you to add a
new INTERNAL_TOKEN key to the security section. See
/usr/local/etc/gitea/conf/app.ini.sample for details. Gitea will not start
until this key is added to the configuration.
Gitea will try to add this key itself, but wi
21 matches
Mail list logo
