While any given place may have its own conventions, it's not uncommon for
people to have something either meaningful to them or that they thing is witty,
in their .sig block (after a line consisting of just dash dash space).
The most that is usually expected is that something not be illegal,
James,
What, and who, exactly, are you referring to?
Peter
> On 19 Jan 2021, at 5:00 pm, James Linder wrote:
>
> I'm offended by having somebody tout their beliefs in a technical forum.
> De Grass Tyson presents argument that it is genetic, and I will not
> discriminate on genetics.
> But
I'm offended by having somebody tout their beliefs in a technical forum.
De Grass Tyson presents argument that it is genetic, and I will not
discriminate on genetics.
But touting a belief is not genetic, it is for a purpose, and I think it spoils
the forum. Please don't.
James
$ sudo port install xorg-server
$ sudo port install R
$ sudo port install R-app
Start MacPorts>R.app
In the R.app console
> install.packages(“rgl”)
This will involve a lot of compilation. The OpenMP problem seems to have been
resolved by using the compiler /opt/local/bin/clang++-mp-9.0, and
Thank you, yes! I grabbed the Portfile mentioned at the end of that ticket from
GitHub (since it wasn't on the mirror yet), put it in place, and libjpeg-turbo
+universal built just fine, and the various ports that now depend on it are so
far so good (as updates continue with some of the slower
On Jan 18, 2021, at 21:11, Richard L. Hamilton wrote:
> ...which is a problem given that a lot of ports were apparently changed to
> use it.
>
>
Yes, all ports that depend on jpeg were changed to depend on libjpeg-turbo
yesterday. This had been requested for years but hadn't been done
...which is a problem given that a lot of ports were apparently changed to use
it.
main.log_libjpeg-turbo.txt.gz
Description: GNU Zip compressed data
smime.p7s
Description: S/MIME cryptographic signature
On Jan 18, 2021, at 04:56, Peter West wrote:
> I’ve removed XQuartz (again), and installed R and R-app from MacPorts. The R
> install warned me that
> Clang compilers provided by Xcode do not support OpenMP. Some R packages
> using OpenMP may require additional
> flags in the Makevar file
On Jan 18, 2021, at 06:40, Janosch Peters wrote:
> I need sparkle as a dependency for the new MacPass port. Your points about
> sparkle are of course valid. When I wrote the message I thought it might
> still be nice to give users the choice to use it or not - via a variant for
> instance.
On Jan 18, 2021, at 19:38, Tom wrote:
> how can I build clang with -ilocal option support in order to build CrossOver
> Wine for 32on64?
That's an option that Crossover added to clang. When I last looked into the
issue last year, you had to use Crossover's special version of clang, which
Hi,
how can I build clang with -ilocal option support in order to build CrossOver
Wine for 32on64?
Regards
Hi,
how can I build clang that supports -ilocal to build to Wine for 32on64?
Regards
> Am 12.01.2021 um 02:46 schrieb Ryan Schmidt :
>
> On Jan 11, 2021, at 09:41, Janosch Peters wrote:
>
>> I am struggling to create working port file for
>> sparkle(https://github.com/sparkle-project/Sparkle). All targets contained
>> in the Xcode project are building with no errors but when
I’ve removed XQuartz (again), and installed R and R-app from MacPorts. The R
install warned me that
Clang compilers provided by Xcode do not support OpenMP. Some R packages using
OpenMP may require additional
flags in the Makevar file (e.g. data.table) to build. Please consult package
14 matches
Mail list logo
