The date command as shown in the 3rd synopsis should do what you are looking for. The combination of the -j option and the new_date provides a way to provide the 'starting date/time' without actually setting the system clock, and the -v will do the requested adjustment to that and print it.
Are these GPU acceleration tasks some custom-built programs? If you trust them not to harm your system, you could just change the owner of those programs to root and set the SUID bit (see chmod)
From what has been posted here in the forums, the ports repository is being transitioned from SVN to git, and updates to the repository have been stopped until that is complete.
git -C /usr clone https://git.freebsd.org/ports.git ports
Cloning into 'ports'...
fatal: repository 'https://git.freebsd.org/ports.git/' not found
Shouldn't this work?
You did not fully answer question from SirDice, so I ask a different question: where is source of pwm tools you are trying to install?
Perhaps pwm tools can be changed to look for unicorn 1.0.2 instead of 1.0.2rc3 or 1.0.2rc4.
pkg lock is your friend when you need specific options for a port. Building the port actually created a local "package" which then got installed on your system. pkg lock <package> tells pkg not to touch that one, ever, if there's a difference between what is installed locally and what is in...
Change the python module to use version 1.0.2 without the -rcX part.
I cannot say how to do this since the python module is unknown.
P.S. Why do people insist on making software that depends on 'release candidates' rather than an official release of a dependent module?
Something built against a particular version of gcc will require the low-level runtime components of that version of gcc to actually run. On FreeBSD, an installation of gcc includes both the build tools (compiler/linker/etc) and those low-level runtime parts. There is no separate port/package...
From list of targets in bsd.port.mk:
# config - Configure options for this port (using ${DIALOG}).
# Automatically run prior to extract, patch, configure, build,
# install, and package.
Defining the make variable...
I suggest to see which llvm versions on your system are shown to actually be required by something:pkg info -rx llvm
On my machine, the results are:
% pkg info -rx llvm
llvm10-10.0.1_4:
mesa-dri-20.2.3_1
In the past, I've seen multiple llvm versions listed, and some of those showed...
I did this:git clone -b stable/12 --depth 1 https://git.freebsd.org/freebsd/src.git src.git
I used --depth 1 because I don't care about all the history; I just want the source code. Without that, it takes a whole lot longer to download, but the result, currently, is smaller than the SVN...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.