On Wed, 30 Mar 2016, Aleksander Alekseev wrote:
CPUTYPE?=native
CFLAGS+=-O2 -pipe
CXXFLAGS+=-O2 -pipe
These will bite with no provocation, and prevent ports that want to
set their own flags from using them.
Frankly as a rule of thumb I prefer binary packages. But how would you
recommend to
> Did you erase /usr/src before checking out -CURRENT? Obsolete files
> left in there can easily break things. 'svn stat /usr/src' will show
> those files with a '?'.
I did. `svn stat /usr/src` outputs nothing and has return code 0.
> The first stages of buildworld build a copy of clang
On Tue, 29 Mar 2016, Aleksander Alekseev wrote:
Do you still have your old make.conf for comparison?
Sure. Current make.conf:
```
CPUTYPE?=native
CFLAGS+=-O2 -pipe
CXXFLAGS+=-O2 -pipe
These will bite with no provocation, and prevent ports that want to set
their own flags from using them.
On Mon, 28 Mar 2016, Aleksander Alekseev wrote:
I think I realized what's going on. I probably rebuilded the world on
two different machines but forgot to do it on this one. I will
re-check this and report results a bit later.
OK, here is a problem. I can't upgrade the world because of
On 29 Mar 2016, at 15:53, Aleksander Alekseev wrote:
>
>> For some reason, your build does not pick up the __alloc_size defines
>> from sys/cdefs.h. You will have to figure out which cdefs.h your
>> build is including, and check whether that is in sync with the rest
>> of your
> Do you still have your old make.conf for comparison?
Sure. Current make.conf:
```
CPUTYPE?=native
CFLAGS+=-O2 -pipe
CXXFLAGS+=-O2 -pipe
```
Old make.conf:
```
CC=/usr/bin/clang
CXX=/usr/bin/clang++
CPP=/usr/bin/clang-cpp
CPUTYPE?=native
CFLAGS+=-O2 -pipe
CXXFLAGS+=-O2 -pipe
```
Just
On Tue, 29 Mar 2016 16:53:18 +0300
Aleksander Alekseev wrote:
> > For some reason, your build does not pick up the __alloc_size
> > defines from sys/cdefs.h. You will have to figure out which
> > cdefs.h your build is including, and check whether that is in sync
> > with the rest
> For some reason, your build does not pick up the __alloc_size defines
> from sys/cdefs.h. You will have to figure out which cdefs.h your
> build is including, and check whether that is in sync with the rest
> of your source tree.
I removed CC, CXX and CPP lines from /etc/make.conf and it
On 29 Mar 2016, at 11:38, Aleksander Alekseev wrote:
>
> OK, here is what I did so far.
>
> First I booted with 10.2 kernel (it's always good to have a backup).
> Now I have 10.2 kernel and world. After that I installed clang38 using
> ports (and discovered a bug #208375 in a
OK, here is what I did so far.
First I booted with 10.2 kernel (it's always good to have a backup).
Now I have 10.2 kernel and world. After that I installed clang38 using
ports (and discovered a bug #208375 in a process).
> Don't try to build world with ports clang, it's not yet supported (at
>
OK, here is what I did so far.
First I booted with 10.2 kernel (it's always good to have a backup).
Now I have 10.2 kernel and world. After that I installed clang38 using
ports (and discovered a bug #208375 in a process).
> Don't try to build world with ports clang, it's not yet supported (at
>
On 28 Mar 2016, at 16:00, Aleksander Alekseev wrote:
>
>> I think I realized what's going on. I probably rebuilded the world on
>> two different machines but forgot to do it on this one. I will
>> re-check this and report results a bit later.
>
> OK, here is a problem. I
On Tue, 29 Mar 2016 00:42:09 +0200
Gary Jennejohn wrote:
> On Mon, 28 Mar 2016 17:00:31 +0300
> Aleksander Alekseev wrote:
>
> > > I think I realized what's going on. I probably rebuilded the world on
> > > two different machines but forgot to do it on
On Mon, 28 Mar 2016 17:00:31 +0300
Aleksander Alekseev wrote:
> > I think I realized what's going on. I probably rebuilded the world on
> > two different machines but forgot to do it on this one. I will
> > re-check this and report results a bit later.
>
> OK, here is a
> I think I realized what's going on. I probably rebuilded the world on
> two different machines but forgot to do it on this one. I will
> re-check this and report results a bit later.
OK, here is a problem. I can't upgrade the world because of compile
errors I mentioned before:
> It used to be FreeBSD 10.2 but I rebuilded and reinstall kernel and
> world from CURRENT according to Handbook instructions. I have exact
> steps recorded in case it would help. I hope such way of upgrading
> FreeBSD is correct?
I think I realized what's going on. I probably rebuilded the world
On Mon, 28 Mar 2016 08:47:35 +0300
Aleksander Alekseev wrote:
> > What's the output of these commands?:
> >
> > freebsd-version
> > uname -r
> > uname -a
> > grep "define __FreeBSD_version" /usr/include/sys/param.h
> >
>
> $ freebsd-version
> 10.2-RELEASE
>
> $ uname -r
> What's the output of these commands?:
>
> freebsd-version
> uname -r
> uname -a
> grep "define __FreeBSD_version" /usr/include/sys/param.h
>
$ freebsd-version
10.2-RELEASE
$ uname -r
11.0-CURRENT
$ uname -a
FreeBSD portege 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r297287: Sat Mar
26 12:36:04
On Sun, 27 Mar 2016 23:42:02 +0300
Aleksander Alekseev wrote:
> Hello
>
> I'm using FreeBSD CURRENT because of recent improvements in area of
> Intel GPUs support in this branch. Also there is a hope that by using
> CURRENT I can discover some bugs and contribute to FreeBSD
Hello
I'm using FreeBSD CURRENT because of recent improvements in area of
Intel GPUs support in this branch. Also there is a hope that by using
CURRENT I can discover some bugs and contribute to FreeBSD project a
bit by reporting them.
Today I noticed that I can't install anything from ports any
20 matches
Mail list logo