Re: FreeBSD 10.0-CURRENT: messed up the ports and system (gcc46 won't compile) and need to repair - how?
> > Did you rebuild ports/devel/binutils after change to 10.0 current. > > I was having same problem with gcc45 , then i rebuilt binutils with uname_r > > 9.0-Current and it went away. > > The most recent update to gcc46 also missed the shared library version > bump of mpfr to mpfr.so.5, I've had issues with mpfr and other libraries as a result of autoconf bugs. Notably, they use the glob 'freebsd1*' to identify FreeBSD 1.X, and therefore they assume that shared libraries aren't supported. I hope the fix for that isn't too painful. Apologies for In-reply-to munging; I'm not subscribed. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Inline definition problem in current
On Tue, Mar 24, 2009, Doug Barton wrote: > David Schultz wrote: > > On Mon, Mar 23, 2009, Gustau Perez wrote: > >> a few time ago I switched to current, right now I've it updated to > >> yesterday. While compiling some ports (in fact, building x11/gnome2) I > >> found that some of them (written in C) are using some inline functions > >> (I guess it is because the compiler will replace the call to the > >> function with the function itself). The problem is that gcc fails with > >> the following message : > >> > >>error: nested function 'XXX' declared but never defined > >> > >> checking the code, the function is declared and then implemented in a > >> header file which is included in the offending .c file. The function is > >> declared as 'inline'. The only solution I found is to change the > >> definition to static. > >> > >> Checking pontyhat shows me that many ports are failing because of > >> this problem. What I can understand is why is this happening, because > >> the same ports compiles fine in STABLE and the compilers's version in > >> base seems to be the same (gcc (GCC) 4.2.1 20070719 [FreeBSD], the same > >> in current) > > > > Which other ports were broken for this reason? > > I am trying to compile gimp on -current right now and x11/babl and > graphics/gegl both have this problem. Take a look at > http://pointyhat.freebsd.org/errorlogs/i386-8-failure.html for more > examples (click on the link on the right under Package to see the > logs). There are currently over 600 broken ports in -current, all the > ones I clicked on in a completely bogus sample had this same problem. My bug; I missed an important line when merging from gcc trunk 122565. Instead of reporting: error: nested function 'foo' declared but never defined gcc should have been reporting: warning: inline function 'foo' declared but never defined I'll check in a fix as soon as I run a buildworld. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: HEADS DOWN (was Re: HEADS UP: putenv, setenv, unsetenv, getenv changes)
On Wed, May 02, 2007, Brooks Davis wrote: > On Tue, May 01, 2007 at 08:06:45PM +0400, Andrey Chernov wrote: > > All backed out. > > > > Not because I admit they are technically wrong and not because of bug > > reports (I receive nothing). But because I surprisingly meets so > > strong opposition and resistance so lost any desire to continue that. > > > > Anyone who interested in POSIX can dig out what changes and how > > through cvs diffs. > > FreeBSD does care about standards and your change probably makes sense, > but the way you went about it was all wrong. > > First, you committed an API/ABI change to libc without even performing > a buildworld. You should be commended for fixing the problems quickly, > but the breakage rightfully made people nervous. Just to clarify, the nature of my original response was not that this change is unequivocally bad, but that it broke stuff, and the stated rationale seemed dodgy. (Just because POSIX says so doesn't make it a good idea.) The change actually caught me just as I was restoring my main desktop after a hard drive crash and rebuilding all the ports and other applications I use. Lots of random stuff broke while compiling x11 libs or some such thing, and I wound up installing a few dozen things from packages. I guess that's what I get for running -CURRENT when I have deadlines! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
