Re: ports r500205 generates extraneous "make describe"
On Thu, May 02, 2019 at 05:41:45PM -0600, Adam Weinberger wrote: > On Thu, May 2, 2019 at 3:36 PM Peter Jeremy wrote: > > > > Doing a "make describe" (part of "make index") in > > /usr/ports/science/ALPSCore > > now generates extraneous output as below. Could you please look into this. > > > > server% make describe > > sh: /usr/local/mpi/openmpi2/bin/mpicc: not found > > make: "/usr/ports/Mk/Uses/compiler.mk" line 78: warning: > > "/usr/local/mpi/openmpi2/bin/mpicc --version" returned non-zero status > > make: "/usr/ports/Mk/Uses/compiler.mk" line 133: warning: > > "/usr/local/mpi/openmpi2/bin/mpicxx -### /dev/null 2>&1" returned non-zero > > status > > ALPSCore-2.2.0_7|/usr/ports/science/ALPSCore|/usr/local|Generic algorithms > > and utilities for condensed matter > > physics|/usr/ports/science/ALPSCore/pkg-descr|po...@freebsd.org|science/usr/ports/devel/boost-libs > > /usr/ports/devel/cmake /usr/ports/devel/ninja /usr/ports/math/eigen3 > > /usr/ports/net/openmpi2 /usr/ports/science/hdf5 > > /usr/ports/science/szip|/usr/ports/devel/boost-libs /usr/ports/net/openmpi2 > > /usr/ports/science/hdf5 > > /usr/ports/science/szip|https://github.com/ALPSCore/ALPSCore > > > > -- > > Peter Jeremy > > I was wondering about this too. Perhaps instead of _VARS, this should be using > OPENMPI2_CONFIGURE_ENV= cc=... cxx=... > OPENMPI2_MAKE_ENV= cc=... cxx=... You can only change CC/CXX after bsd.port.pre.mk otherwise it breaks bits of the framework like compiler.mk. This should probably be changed to a .if PORT_OPTIONS:M test after includ'ing bsd.port.pre.mk. -- Mathieu Arnold signature.asc Description: PGP signature
Re: ports r500205 generates extraneous "make describe"
On Fri, May 3, 2019 at 2:00 AM Mathieu Arnold wrote: > > On Thu, May 02, 2019 at 05:41:45PM -0600, Adam Weinberger wrote: > > On Thu, May 2, 2019 at 3:36 PM Peter Jeremy wrote: > > > > > > Doing a "make describe" (part of "make index") in > > > /usr/ports/science/ALPSCore > > > now generates extraneous output as below. Could you please look into > > > this. > > > > > > server% make describe > > > sh: /usr/local/mpi/openmpi2/bin/mpicc: not found > > > make: "/usr/ports/Mk/Uses/compiler.mk" line 78: warning: > > > "/usr/local/mpi/openmpi2/bin/mpicc --version" returned non-zero status > > > make: "/usr/ports/Mk/Uses/compiler.mk" line 133: warning: > > > "/usr/local/mpi/openmpi2/bin/mpicxx -### /dev/null 2>&1" returned > > > non-zero status > > > ALPSCore-2.2.0_7|/usr/ports/science/ALPSCore|/usr/local|Generic > > > algorithms and utilities for condensed matter > > > physics|/usr/ports/science/ALPSCore/pkg-descr|po...@freebsd.org|science/usr/ports/devel/boost-libs > > > /usr/ports/devel/cmake /usr/ports/devel/ninja /usr/ports/math/eigen3 > > > /usr/ports/net/openmpi2 /usr/ports/science/hdf5 > > > /usr/ports/science/szip|/usr/ports/devel/boost-libs > > > /usr/ports/net/openmpi2 /usr/ports/science/hdf5 > > > /usr/ports/science/szip|https://github.com/ALPSCore/ALPSCore > > > > > > -- > > > Peter Jeremy > > > > I was wondering about this too. Perhaps instead of _VARS, this should be > > using > > OPENMPI2_CONFIGURE_ENV= cc=... cxx=... > > OPENMPI2_MAKE_ENV= cc=... cxx=... > > You can only change CC/CXX after bsd.port.pre.mk otherwise it breaks > bits of the framework like compiler.mk. > > This should probably be changed to a .if PORT_OPTIONS:M test after > includ'ing bsd.port.pre.mk. Of course, that makes sense. Setting CONFIGURE/MAKE_ENV would fix only the "make describe". # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.org ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Is there a way to build only the port from source, and install dependencies from packages with the make command?
Hi Yuri,
With the following in my .zshrc, I just run "ibd" before making a
particular port:
function ibd () {
# Can also make all-depends-list
pkg install --yes $(make build-depends-list run-depends-list | sort -u |
sed 's/\/usr\/ports\///')
}
Modify at will.
Le mer. 1 mai 2019 à 17:49, Dave Cottlehuber a écrit :
> On Tue, 30 Apr 2019, at 21:17, Adam wrote:
> > On Tue, Apr 30, 2019 at 12:36 PM Yuri wrote:
> >
> > > Sometimes instructions to build some port from source are needed. "cd
> > > /usr/ports/{caregory}/{port-name} && make" rebuilds everything from
> > > source, including dependencies.
> > >
> > > Is there an easy way to make it install missing dependencies with pkg,
> > > without listing them? I couldn't find such feature.
>
> from within the appropriate port directory:
>
> function make-depends --description 'installs runtime and buildtime
> dependencies for a given port'
> sudo pkg install -r FreeBSD --automatic (make build-depends-list
> run-depends-list | sed -E -e 's,^.+/([^/]+/[^/]+$),\1,')
> end
>
> function make-pkg --description 'test port build locally'
> make clean \
> check-sanity \
> fetch makesum checksum \
> extract patch \
> configure build \
> stage stage-qa \
> check-orphans \
> check-plist \
> package \
> && find /tmp/usr/ports -name \*.txz -type f
> end
>
> I use these locally while working on ports - should work similar for you
> too.
>
> A+
> Dave
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Gitea update to 1.8 breaking config change
For those of you using Gitea a quick heads-up: In Gitea 1.8.0, a new config variable JWT_SECRET has been introduced. If not set in gitea/conf/app.ini, Gitea will try and add it to the file; in the default setup of the port, the file is not writable by the git user, and Gitea will not start because of that. To get Gitea going again, either add that variable (see gitea/conf/app.ini.sample), or make app.ini writable to the git user so Gitea can add a suitable value for you. Do not use the value in the sample configuration! I’ve just submitted the PR for the update to 1.8.0, so the updated port should become available in the next couple of days. Stefan -- Stefan BethkeFon +49 151 14070811 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Gitea update to 1.8 breaking config change
Stefan Bethke writes: > For those of you using Gitea a quick heads-up: [...] The proper place to document breaking changes is UPDATING file. ports@ list has low signal-to-noise ratio but high traffic, so your heads-up maybe forgotten before the next /quarterly branches. https://www.freebsd.org/doc/en/books/porters-handbook/moved-and-updating-files.html ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Gitea update to 1.8 breaking config change
On Fri, May 3, 2019 at 1:36 PM Jan Beich wrote: > > Stefan Bethke writes: > > > For those of you using Gitea a quick heads-up: > [...] > > The proper place to document breaking changes is UPDATING file. > ports@ list has low signal-to-noise ratio but high traffic, so your > heads-up maybe forgotten before the next /quarterly branches. > > https://www.freebsd.org/doc/en/books/porters-handbook/moved-and-updating-files.html Jan is correct, but a breaking change like this should also go into the pkg-message for the gitea port. # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.org ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
