Date: Thu, 29 Mar 2012 11:33:57 -0400 From: Super Bisquit <superbisquit@gmail.com> To: Nathan Whitehorn <nwhitehorn@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: wi diff Message-ID: <CA%2BWntOuX472WpSYUccNQrRu6C7rH8Lwx4U7tW1bG=2rKsT-rwQ@mail.gmail.com> In-Reply-To: <4F707833.8080107@freebsd.org> References: <CA%2BWntOtovGHo1wPzJQ5bf4-xrtcMzdXhnWSiBxH7vUp%2B_1-zJw@mail.gmail.com> <20120324172025.67615299@narn.knownspace> <CA%2BWntOtwEpaoUyC8xTu4Cw2-hSCb10sCPrPxJYZ0eU5Wo9wppA@mail.gmail.com> <4F707833.8080107@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 26, 2012 at 10:07 AM, Nathan Whitehorn <nwhitehorn@freebsd.org>wrote: > On 03/25/12 19:39, Super Bisquit wrote: > >> On 3/24/12, Justin Hibbits<chmeeedalf@gmail.com> wrote: >> >>> On Sat, 24 Mar 2012 17:04:58 -0400 >>> Super Bisquit<superbisquit@gmail.com**> wrote: >>> >>> I sent two emails- the second a repeat of the first. >>>> In GENERIC, all warnings were edited out and wi was not added in the >>>> miibus section. >>>> I haven't rebooted yet. The other messages show the error. >>>> >>>> Apologies for the sudden come and go. >>>> >>>> Justin, thanks for the reply in CURRENT. I think that clang, llvm, and >>>> related need to be in the base and not in ports. Developer version >>>> releases are different. Look on emulation for some posts I made, is >>>> it possible to get what was sent- I think from you if I recall >>>> correctly- to be in source? >>>> >>>> If it wasn't for the error, buildworld on powerpc with clang would >>>> have worked. >>>> >>>> Garrett, has the error from tinderbox build been corrected and has a >>>> build been setup with clang instead? >>>> >>> >>> From my understanding, wi(4) does not attach to the mii bus, so you >>> will never see it. If my understanding is correct, mii is for physical >>> ethernet only (a real networking expert can correct me here, gladly). >>> So the attachment you see of wi(4) should only be on the macio, pci, or >>> pccard buses, if in fact you have a wi(4) card (original airport, >>> not airport extreme in the case of my diff). >>> >>> As for the clang/llvm problems, since clang is not complete regarding >>> powerpc (and anything but x86/x86-64 and most of arm), it doesn't make >>> sense to keep updating them just to track any possible PowerPC >>> changes. One very important part that's missing in the PowerPC target >>> is position-independent code, which is required for shared libraries. >>> I've been working off and on with getting Thread-local storage working >>> for PowerPC, but have not done too much (wrote the basic function, >>> haven't added the codegen parts in), but will continue working on it >>> over the coming months, and then turn my attention to PIC (if nobody >>> else has stepped up to it by then). With these being the two biggest >>> stumbling points, solving them will go a long way to getting clang >>> buildworlding FreeBSD. >>> >>> - Justin >>> >>> >> I emailed the Debian maintainers for clang and asked about configure >> options. Although it is not FreeBSD, the information may help some. >> The #llvm irc channel mentioned that FreeBSD was/is interested in >> PowerPC builds. >> >> > You need to add -fno-strict-aliasing when building straight from SVN, at > which point everything works fine. You can see how it's done in the FreeBSD > tree. > -Nathan > ______________________________**_________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-ppc<http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>; > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@**freebsd.org<freebsd-ppc-unsubscribe@freebsd.org> > " > Hey, Nathan, how's it going? Anyway, am I to add the flag to ./configure as -option or is it for make -option?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BWntOuX472WpSYUccNQrRu6C7rH8Lwx4U7tW1bG=2rKsT-rwQ>