On 29/04/2019 21:12, Joe Maloney wrote:
With CFT version you chose to build, and package individual components such as
sendmail with a port option. That does entirely solve the problem of being
able to reinstall sendmail after the fact without a rebuild of the userland
(base) port but
On 25 Aug 2017, at 07:32, Mark Millard wrote:
>
> As I remember _Static_assert is from C11, not
> the older C99.
In pre-C11 dialects of C, _Static_assert is an identifier reserved for the
implementation. sys/cdefs.h defines it to generate a zero-length array if the
On 7 Aug 2017, at 16:20, Maxim Sobolev wrote:
>
> One way to defeat this would be to mark those headers with the #pragma
> clang system_header. As per:
>
> https://clang.llvm.org/docs/UsersManual.html#id27
That won’t fix the issue, because base (as you can see from the
On 21 Aug 2016, at 22:23, Mark Millard wrote:
>
> On armv6 (an rpi2) C++ by itself can have /lib/libgcc_s.so.1 not being
> sufficient, for example with g++6 being used:
>
>> # g++6 -std=c++14 -O2 cpp_clocks_investigation.cpp
>> # ldd a.out
>> a.out:
>>
On 1 Apr 2015, at 05:03, Rui Paulo rpa...@me.com wrote:
That is expected. WITH_PKG=devel is a make(1) option that only affects ports
(non-binary pkgs).
Are you sure? I have it in make.conf on one of my systems where I never build
ports manually (and don't even have a ports tree installed)
On 6 Jul 2012, at 20:32, Sergey Kandaurov wrote:
This is probably because the private symbol __collate_load_error changed
to macro (i.e. removed) in r235785 after 9.0. If so, it might brake those
older binaries which rely on that symbol, though it's still defined in
Symbol.map. Probably David
On 2 Jun 2012, at 03:56, Erich Dollansky wrote:
But I have to mention one disadvantage. The ports are in no way linked to the
releases. This leads to situations in which a small change in a basic library
will result in a complete update of the installed ports. I expressed this
already many
On 2 Jun 2012, at 12:01, Erich wrote:
I would even accept to get the 'release' ports tree without security fixes
just to have a system which is up and running fast after I tried an upgrade
like what is happening at the moment with PNG dependent ports.
You have this already. Just install
On 2 Jun 2012, at 12:19, Erich wrote:
Hi,
On 02 June 2012 PM 12:04:26 David Chisnall wrote:
On 2 Jun 2012, at 12:01, Erich wrote:
I would even accept to get the 'release' ports tree without security fixes
just to have a system which is up and running fast after I tried an upgrade
like
Thanks to all who replied, both on and off list. I've attempted to distill the
replies that I got into a coherent summary. I've put the draft on the wiki
here:
http://wiki.freebsd.org/WhyUseFreeBSD
Feedback welcome!
David
On 30 May 2012, at 19:20, David Chisnall wrote:
Hi Everyone
Hi Everyone,
This is off-topic, so please feel free to disregard it, but I'm sending it to
this list in the hope that it will reach a largish number of users.
I am currently looking at updating some of our advocacy material (which
advertises exciting new features like SMP support), and
Hi Everyone,
I have just finished merging libc++ and all of the things that it depends on
into 9-STABLE. Since 9.1 is due to branch Real Soon Now™, it would be good if
it could see a bit of testing before then. Because it uses C++11, libc++ will
only work if built with clang, so it is
On 23 May 2012, at 10:29, Trond Endrestøl wrote:
CC='gcc'
snip
something as make buildworld runs smoothly
without WITH_LIBCPLUSPLUS=yes in /etc/src.conf.
You are trying to build C++11 code with a C++98 compiler. If you want to build
libc++, you must be using clang++. There is a reason
13 matches
Mail list logo