Jeffrey Walton wrote:
> > > A quick
> > > workaround if you're using zipped archives is to add -DD to the command
> > > line.
> >
> > What do you mean? Neither 'tar' not 'make' takes a '-DD' option.
>
> I believe that would be the -D and -DD option to unzip (1).
This workaround would
1) requir
On Sat, Jan 8, 2022 at 1:30 AM Bruno Haible via cfarm-users
wrote:
>
> Peter Gutmann wrote:
> > A quick
> > workaround if you're using zipped archives is to add -DD to the command
> > line.
>
> What do you mean? Neither 'tar' not 'make' takes a '-DD' option.
I believe that would be the -D and -D
Peter Gutmann wrote:
> A quick
> workaround if you're using zipped archives is to add -DD to the command line.
What do you mean? Neither 'tar' not 'make' takes a '-DD' option.
Bruno
___
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https
Bruno Haible via cfarm-users writes:
>On both machines, the clock is 8 hours behind reality.
Being in a country that's ahead of everyone else on earth's time zone, I've
become used to "clock skew detected" almost as an extra motd. A quick
workaround if you're using zipped archives is to add -D
On Sat, Jan 8, 2022 at 12:48 AM Bruno Haible via cfarm-users
wrote:
>
> On both machines, the clock is 8 hours behind reality. When unpacking
> freshly created tarballs, this leads to warning messages such as
>
> tar: foobar-20220107: time stamp 2022-01-08 00:36:16 is 28740.13808
On Sat, Jan 8, 2022 at 12:57 AM Christian Jullien via cfarm-users
wrote:
>
> Also, the following variables are set
>
> LANG=zh_CN
> LC_ALL=zh_CN
> LC_CTYPE=zh_CN
> LC_NUMERIC=zh_CN
> LC_TYPE=zh_CN
>
> I set them in my .bash_profile to more common en_US.UTF-8
>
> You probably want to set them globa
On 07-01-22, Bruno Haible via cfarm-users wrote:
> On both machines, the clock is 8 hours behind reality. When unpacking
> freshly created tarballs, this leads to warning messages such as
>
> tar: foobar-20220107: time stamp 2022-01-08 00:36:16 is 28740.13808862 s in
> the
and gcc401
On both machines, the clock is 8 hours behind reality. When unpacking
freshly created tarballs, this leads to warning messages such as
tar: foobar-20220107: time stamp 2022-01-08 00:36:16 is 28740.13808862 s in
the future
and subsequent build failures.
Would it be possible to correct
On both machines, the clock is 8 hours behind reality. When unpacking
freshly created tarballs, this leads to warning messages such as
tar: foobar-20220107: time stamp 2022-01-08 00:36:16 is 28740.13808862 s in the
future
and subsequent build failures.
Would it be possible to correct this? I
cfarm-announces writes:
>Feel free to report any issues
First issue :-). Looks like clang is present but not set up:
> gcc test.c
> clang test.c
In file included from test.c:1:
In file included from /usr/include/stdlib.h:394:
In file included from /usr/include/sys/types.h:227:
In file include
Hi Vincent,
On 07-01-22, Vincent Lefevre via cfarm-users wrote:
> On 2022-01-07 11:45:26 +0100, CFarm Annoucements via cfarm-announces wrote:
> > We are happy to announce the availability of two Loongson machines with a
> > recent LoongArch [1] 3A5000 processor running at 2.5 GHz: gcc400 and gcc40
On 2022-01-07 11:45:26 +0100, CFarm Annoucements via cfarm-announces wrote:
> We are happy to announce the availability of two Loongson machines with a
> recent LoongArch [1] 3A5000 processor running at 2.5 GHz: gcc400 and gcc401.
gcc401 was already used for a Debian-RISC-V VM running on gcc140.
R
Thanks, is it possible to install subversion please?
-Original Message-
From: cfarm-announces [mailto:cfarm-announces-boun...@lists.tetaneutral.net]
On Behalf Of CFarm Annoucements via cfarm-announces
Sent: Friday, January 07, 2022 11:45
To: cfarm-announ...@lists.tetaneutral.net
Cc: CFarm
13 matches
Mail list logo
