Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) [amd64 system ld being lld vs. binutils based]

On 2017-Apr-15, at 11:30 PM, Mark Millard <markmi at dsl-only.net> wrote:

> On 2017-Apr-15, at 2:30 AM, Mark Linimon <linimon at lonesome.com> wrote:
> 
>> On Fri, Apr 14, 2017 at 08:27:29PM -0700, Mark Millard wrote:
>>> I've seen material quoted from a exp-run that reported
>>> that about 54(?) ports were then blocked by lang/gcc6-aux
>>> not building.
>> 
>> Although the first is an older run (the last complete run IIUC), there
>> were 50 and 51 respectively as of:
>> 
>> http://thunderx1.nyi.freebsd.org/build.html?mastername=110arm64-default&build=423029
>> http://beefy8.nyi.freebsd.org/build.html?mastername=head-armv6-default&build=p437390_s316341
>> 
>> I think you're fairly deep into unexplored territory here.
> 
> 
> Looks like it. I tried an amd64 context (that was built using
> WITH_LLD_IS_LD= in case that matters) and ports-mgmt/synth's
> indirect build of lang/gcc6-aux quickly stopped for:
> 
> configure:4439: /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap/bin/gcc -O2 -pipe  -g -fstack-protector -fno-strict-aliasing -I/usr/local/include  -L/usr/local/lib -fstack-protector conftest.c  >&5
> /usr/bin/ld: error: unable to find library -lssp_nonshared
> /usr/bin/ld: error: unable to find library -lc
> collect2: error: ld returned 1 exit status
> configure:4443: $? = 1
> configure:4480: result: 
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME ""
> | #define PACKAGE_TARNAME ""
> | #define PACKAGE_VERSION ""
> | #define PACKAGE_STRING ""
> | #define PACKAGE_BUGREPORT ""
> | #define PACKAGE_URL ""
> | /* end confdefs.h.  */
> | 
> | int
> | main ()
> | {
> | 
> |   ;
> |   return 0;
> | }
> configure:4486: error: in `/usr/obj/portswork/usr/ports/lang/gcc6-aux/work/build':
> configure:4490: error: C compiler cannot create executables
> 
> This happened even if I checked off in gcc6-aux's config
> to do a bootstrap.
> 
> Even amd64 has build problems (at least for use of the
> modern/experimental ld).

I reverted to an amd64 system based on WITHOUT_LLD_IS_LD= and
that avoided this issue: at least the build has gotten farther
and is still in progress.

It looks like the lang/gcc6-aux bootstrap/bin/gcc for amd64 is
using /usr/bin/ld in a way that is binutils specific at this
point.

===
Mark Millard
markmi at dsl-only.net