Date: Tue, 10 Aug 2004 18:32:42 -0500 From: "P.D. Seniura" <pdseniura@techie.com> To: "Michael Nottebrock" <michaelnottebrock@gmx.net> Cc: freebsd-ports@FreeBSD.org Subject: i got a possible working scenario (Re: -Current build problemsand core dumped) Message-ID: <20040810233242.8C8FD790034@ws1-14.us4.outblaze.com>
next in thread | raw e-mail | index | archive | help
Hi, I found audio/arts will use the same build-knobs that other KDE components have under FreeBSD's ports system. In the failing scenario, I have WANT_KDE_FINAL=yes in my /etc/make.conf . I commented that out and inserted WANT_KDE_DEBUG=yes to kick in the --enable-debug=full configure option for arts. And the resulting mcopidl binary is NOT crashing. :) If I could ask you or someone reading this to try WANT_KDE_FINAL=yes and then see if your build fails when it runs mcopidl for other modules inside there. I am also building arts with its two options enabled for NAS & ESD. These may not make a difference, they've already built & installed fine with gcc342. BTW I'm doing all of this in BATCH=yes mode, and the settings are all in /etc/make.conf (it's a huge pain to do 522 ports with pkgtools.conf ;) . I will try to further test building arts without the 'debug' option but also without the 'final' option. I am strongly suspecting the 'final' option is causing some code to be miscompiled somehow (the ./configure --help blurb does show --enable-final as experimental). Thing is I always have had 'final' in effect for most of this year but it is _just now_ breaking, if my gut feeling on this is correct. ;) As I type this, audio/arts has finished compiling and has been installed. Keeping fingers crossed as I undo the debug option now & try it again. Thank you for helping. ----- Original Message ----- From: Michael Nottebrock <michaelnottebrock@gmx.net> Date: Tue, 10 Aug 2004 00:20:57 +0200 To: "P.D. Seniura" <pdseniura@techie.com> Subject: Re: -Current build problems with audio/arts: "lt-mcopidl in free(): error: chunk is already free" and core dumped > On Monday 09 August 2004 23:12, P.D. Seniura wrote: > > > And so that brings me to a question about these > > packages being built on the build-farms -- the logs > > at rabarber shows being linked against /usr/local/lib > > on _that_ machine -- is /usr/local/lib on _that_ > > machine a fresh build of a 5-current world? > > Each package is built in a chroot jail, which is populated with a bindist (the > 'distribution' tarballs you get on a FreeBSD installation cd and which are > extracted by sysinstall) and (earlier built) dependency packages. After the > package is built, the chroot jail is deleted and a new one is created for the > next packagebuild. > > The bindist we are using is a -CURRENT snapshot made by > http://snapshots.se.freebsd.org, from August, 1st. > > Just to make sure I absolutely get this right: The mcopidl binary from _our > package_ does coredump on your machine? That's plain weird. :-\ > > -- > ,_, | Michael Nottebrock | lofi@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040810233242.8C8FD790034>