Re: Building on OS X - how?

Good evening, On Wed, 10 Aug 2016, Hubert Feyrer wrote: I've added a bit more information below[2], but to cut a long story short - what excact build.sh options does one use these days to cross-build -current/amd64 from OS X? Did I miss any documentation[3] It seems this was resolved

Re: Building on OS X - how?

> On 16/08/2016, at 7:41 PM, matthew green wrote: > >> I've been trying to find when this breakage occurred, > > it happened when your port switched to GCC 5. sorry :-) Yeah. While looking for the “backend” directory I saw gcc.old and gcc. A quick look showed me they

Re: Building on OS X - how?

> On 12/08/2016, at 3:34 AM, Thor Lancelot Simon wrote: > > It's curious that this doesn't break the tools build, and doesn't > prevent using the built tools to build a kernel! If this can break > the cross-build of the target compiler, I think we must have suddenly > sprouted

re: Building on OS X - how?

> I've been trying to find when this breakage occurred, it happened when your port switched to GCC 5. sorry :-) .mrg.

Re: Building on OS X - how?

Hi Jaromir, > Am 13.08.2016 um 22:06 schrieb Jaromír Doleček : > FWIW, build of tools for both i386 and sparc64 finished without > problems for me on Mac OS X host (10.11.6), building from clean > sources. Do you have the Mac OS X Command Line Tools installed? It’s not

Re: Building on OS X - how?

On Sat, Aug 13, 2016 at 10:06:35PM +0200, Jarom??r Dole??ek wrote: > FWIW, build of tools for both i386 and sparc64 finished without > problems for me on Mac OS X host (10.11.6), building from clean > sources. The problem is not with the tools build. Thor

Re: Building on OS X - how?

FWIW, build of tools for both i386 and sparc64 finished without problems for me on Mac OS X host (10.11.6), building from clean sources. Jaromir 2016-08-12 21:54 GMT+02:00 matthew green : > Thor Lancelot Simon writes: >> On Thu, Aug 11, 2016 at 04:05:06PM +0100, Robert

Re: Building on OS X - how?

On Sat, Aug 13, 2016 at 03:17:16PM +0200, Hubert Feyrer wrote: > > Hi, > > On Sat, 13 Aug 2016, matthew green wrote: > > this fails building the native gcc, which requires a bunch of host > > tools to run. going on your following post, there is a problem > > with genmatch. i don't have access

re: Building on OS X - how?

Hi, On Sat, 13 Aug 2016, matthew green wrote: this fails building the native gcc, which requires a bunch of host tools to run. going on your following post, there is a problem with genmatch. i don't have access to any osx to test, so i'm not sure where to start looking. there aren't too

Re: Building on OS X - how?

On Aug 12, 2016, at 6:44 PM, Michael Plass wrote: > The config.status for host-libcpp is at > https://gist.github.com/mfplass/6a75e12339bc97223854953fee1fa9fc And the relevant diffs with the working (in-jail) build is 619,620c619,620 < S["LTLIBICONV"]="-L/usr/local/lib -liconv

Re: Building on OS X - how?

On Aug 12, 2016, at 12:54 PM, matthew green wrote: > Thor Lancelot Simon writes: >> On Thu, Aug 11, 2016 at 04:05:06PM +0100, Robert Swindells wrote: >>> 2) /usr/bin/cc: Undefined symbols for architecture x86_64: "_iconv" in external/gpl3/gcc/usr.bin/backend >>> >>> This

re: Building on OS X - how?

Thor Lancelot Simon writes: > On Thu, Aug 11, 2016 at 04:05:06PM +0100, Robert Swindells wrote: > > > > >2) /usr/bin/cc: > > >Undefined symbols for architecture x86_64: "_iconv" > > >in external/gpl3/gcc/usr.bin/backend > > > > This should be in libc. > > For what value of "should"?

Re: Building on OS X - how?

On Thu, Aug 11, 2016 at 12:15:32PM -0400, Thor Lancelot Simon wrote: > If that is the case, then it means that the compilation of a *target* > executable is using *host* header files. That will eventually cause corrupt > builds even in a NetBSD-on-NetBSD build. It is in host-libiberty and runs a

Re: Building on OS X - how?

On Aug 11, 2016, at 8:32 AM, Thor Lancelot Simon wrote: > On Thu, Aug 11, 2016 at 04:29:54PM +0200, Hubert Feyrer wrote: >> >> 2) /usr/bin/cc: >> Undefined symbols for architecture x86_64: "_iconv" >> in external/gpl3/gcc/usr.bin/backend > > This bug has appeared within the past few days

Re: Building on OS X - how?

On Thu, Aug 11, 2016 at 04:05:06PM +0100, Robert Swindells wrote: > > >2) /usr/bin/cc: > >Undefined symbols for architecture x86_64: "_iconv" > >in external/gpl3/gcc/usr.bin/backend > > This should be in libc. For what value of "should"? _iconv is in the implementation-defined

Re: Building on OS X - how?

On Thu, Aug 11, 2016 at 09:00:35AM -0700, Michael Plass wrote: > > That sounds like it may be related to a problem I ran into when cross-building > from FreeBSD (11 beta something). With a package for libiconv installed, the > compile > must have found the header in /usr/local/include, but the

Re: Building on OS X - how?

On Thu, Aug 11, 2016 at 04:29:54PM +0200, Hubert Feyrer wrote: > > 2) /usr/bin/cc: >Undefined symbols for architecture x86_64: "_iconv" >in external/gpl3/gcc/usr.bin/backend This bug has appeared within the past few days and breaks my builds on OS X 10.9.5 as well. I'm not having much

Re: Building on OS X - how?

Hubert Feyrer wrote: >On Wed, 10 Aug 2016, co...@sdf.org wrote: >> There shouldn't be anything special about building from OS X. >> You just ran into a setup that happens to not work with it. > >Well, that's my question: what _does_ work? > >I have OS X 10.10.5 (Yosemite) and

Re: Building on OS X - how?

On Wed, 10 Aug 2016, co...@sdf.org wrote: There shouldn't be anything special about building from OS X. You just ran into a setup that happens to not work with it. Well, that's my question: what _does_ work? I have OS X 10.10.5 (Yosemite) and no wish to upgrade, so pointers on where to get

Re: Building on OS X - how?

There shouldn't be anything special about building from OS X. You just ran into a setup that happens to not work with it. It'd be good to file a bug report for it, or at least mention where it fails.

Building on OS X - how?

Hi, for a long time I've cross-built -current/amd64 from OS X. After following the advice to install Command Line Tools[1] as a second compiler besides Xcode, things went downhill and I see different build errors with no special build flags, or with various settings like "-V