Warner Losh writes:
What happens if you say ‘DEBUG_FLAGS+= -gdwarf-2’ instead of a
naked -g?
Experiment in progress ...
... same result as before. (Dang.)
What next?
Robert Huff
___
freebsd-cur
What happens if you say ‘DEBUG_FLAGS+= -gdwarf-2’ instead of a naked -g?
Warner
On Apr 2, 2014, at 9:47 PM, Robert Huff wrote:
> Warner:
>
> > This will happen with fmake. I?ve put some safety belts in place in
> > another fix to keep this from tripping people up (and plan on using > a
> >
I have new information.
The previous problem occurs when I run this script:
#! /bin/sh
set -x
cd /usr/src
if [ -f buildworld.log ]
then rm buildworld.log
fi
rm -rf /usr/obj
cp -p /usr/src/sys/amd64/conf/JERUSALEM /root
make cleandir
date > ./buildworld.time
make -d l buildwor
Jilles Tjoelker writes:
> These messages are harmless, but are fixed by r264167.
And so they were. Thank you.
Now back to the original issue.
Robert Huff
___
freebsd-current@freebsd.org mailing list
On Sat, Apr 05, 2014 at 11:12:36AM -0400, Robert Huff wrote:
> While it's probably not related to the nominal issue, a deeper
> look at the full buildworld log found ten instances of this:
> make[3]: "/usr/src/share/mk/bsd.subdir.mk" line 89: warning: duplicate
> script for target "all_subd
While it's probably not related to the nominal issue, a deeper look at
the full buildworld log found ten instances of this:
make[3]: "/usr/src/share/mk/bsd.subdir.mk" line 89: warning: duplicate
script for target "all_subdir_libnv" ignored
make[3]: "/usr/src/share/mk/bsd.subdir.mk" line 89: wa
On 4/4/2014 4:05 AM, Oliver Pinter wrote:
Is there any change in src.conf?
There is no src.conf. (See original post.)
Robert Huff
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mail
On 4/3/14, Robert Huff wrote:
> Warner Losh writes
>
>> > Can you prune down your make.conf to find the minimal line(s) that
>> > cause this?
>>
>> Yes, but each run will take about three hours
>>
>> Starting with an empty make.conf,
>
> Empty make.conf = same result.
>
Warner Losh writes
> Can you prune down your make.conf to find the minimal line(s) that
> cause this?
Yes, but each run will take about three hours
Starting with an empty make.conf,
Empty make.conf = same result.
Where do I look next?
1) I know very littl
Warner Losh writes
> amd64, I assume?
Yes, as per the provided uname.
> Can you prune down your make.conf to find the minimal line(s) that
> cause this?
Yes, but each run will take about three hours
Starting with an empty make.conf,
On Apr 2, 2014, at 9:47 PM, Robert Huff wrote:
> Warner:
>
> > This will happen with fmake. I?ve put some safety belts in place in
> > another fix to keep this from tripping people up (and plan on using > a
> > similar technique to keep people from hitting the aicasm bug on
> > such system
Warner:
> This will happen with fmake. I?ve put some safety belts in place in
> another fix to keep this from tripping people up (and plan on using
> a similar technique to keep people from hitting the aicasm bug on
> such systems).
As long as make-related issues are on the table .
12 matches
Mail list logo
