Re: INDEX build failed for 4.x
On 2007.01.28 15:46:32 +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait../libexec/ld-elf.so.1: Cannot open /lib/libncurses.so.6 /local0/tmp/erwin/tindex/ports/Mk/bsd.java.mk, line 393: warning: echo JAVA_PORT_NATIVE_BSDJAVA_JDK_1_5 JAVA_PORT_NATIVE_FREEBSD_JDK_1_5 JAVA_PORT_NATIVE_BSDJAVA_JDK_1_5 JAVA_PORT_NATIVE_BSDJAVA_JDK_1_4 JAVA_PORT_NATIVE_BSDJAVA_JDK_1_3 JAVA_PORT_NATIVE_BSDJAVA_JDK_1_2 JAVA_PORT_NATIVE_BSDJAVA_JDK_1_1 JAVA_PORT_LINUX_SUN_JDK_1_5 JAVA_PORT_LINUX_SUN_JDK_1_4 JAVA_PORT_LINUX_SUN_JDK_1_3 JAVA_PORT_LINUX_SUN_JDK_1_2 JAVA_PORT_LINUX_BLACKDOWN_JDK_1_4 JAVA_PORT_LINUX_BLACKDOWN_JDK_1_3 JAVA_PORT_LINUX_BLACKDOWN_JDK_1_2 JAVA_PORT_LINUX_IBM_JDK_1_4 returned non-zero status /libexec/ld-elf.so.1: Cannot open /lib/libncurses.so.6 This is probaly due to builder.FreeBSD.org being upgraded while the INDEX build was running - just ignore it. -- Simon L. Nielsen Hat: clusteradm@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INDEX build failed for 4.x
Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait../local0/tmp/erwin/tindex/ports/www/apache20/Makefile.modules.3rd, line 10: USE_APACHE and Makefile.modules.3rd can't be used together. === www/mod_log_sql2-dtc failed *** Error code 1 *** Error code 1 Stop in /local0/tmp/erwin/tindex/ports. *** Error code 1 Stop in /local0/tmp/erwin/tindex/ports. 1 error Will someone please fix this, or unhook www/mod_log_sql2-dtc from build temporarily? Cheers, -- Xin LI [EMAIL PROTECTED] http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: INDEX build failed for 4.x
On Mon, Oct 09, 2006 at 11:26:20PM +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait.. Done. make_index: avr-libc-1.4.5,1: no entry for /usr/ports/devel/avr-gcc make_index: avr-libc-1.4.5,1: no entry for /usr/ports/devel/avr-gcc Added avr-gcc to devel/Makefile -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INDEX build failed for 4.x
On Wed, Sep 27, 2006 at 01:28:21AM -0400, Kris Kennaway wrote: On Wed, Sep 27, 2006 at 08:23:53AM +0300, Vasil Dimov wrote: On Wed, Sep 27, 2006 at 04:37:30AM +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait.. Done. Warning: Duplicate INDEX entry: php5-imlib2-0.1.00 Committers on the hook: acm ahze alexbl bsam clsung garga hq ijliao joerg leeym markus mat mezz miwi netchild oliver rafan roam sat shaun thierry Most recent CVS update was: [...] Hmmz, where is the error? Have you switched to something like -Werror? It's the duplicate entry; this has always been considered fatal by the INDEX script. I have been observing this in my nightly mails for a long time: /usr/ports# make index Generating INDEX-6 - please wait..Warning: Duplicate INDEX entry: apr-gdbm-db42-1.2.7_1 Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.8_2 Warning: Duplicate INDEX entry: php5-imlib2-0.1.00 Warning: Duplicate INDEX entry: cvsup-without-gui-16.1h_2 Warning: Duplicate INDEX entry: mod_rpaf-0.5 Done. /usr/ports# echo $? 0 /usr/ports# Are you using different build technology than ``make index''? -- Vasil Dimov [EMAIL PROTECTED] % It is not doing the thing we like to do, but liking the thing we have to do, that makes life blessed. -- Goethe pgpiLkIQdh7dt.pgp Description: PGP signature
Re: INDEX build failed for 4.x
On Wed, Sep 27, 2006 at 09:04:19AM +0300, Vasil Dimov wrote: On Wed, Sep 27, 2006 at 01:28:21AM -0400, Kris Kennaway wrote: On Wed, Sep 27, 2006 at 08:23:53AM +0300, Vasil Dimov wrote: On Wed, Sep 27, 2006 at 04:37:30AM +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait.. Done. Warning: Duplicate INDEX entry: php5-imlib2-0.1.00 Committers on the hook: acm ahze alexbl bsam clsung garga hq ijliao joerg leeym markus mat mezz miwi netchild oliver rafan roam sat shaun thierry Most recent CVS update was: [...] Hmmz, where is the error? Have you switched to something like -Werror? It's the duplicate entry; this has always been considered fatal by the INDEX script. I have been observing this in my nightly mails for a long time: /usr/ports# make index Generating INDEX-6 - please wait..Warning: Duplicate INDEX entry: apr-gdbm-db42-1.2.7_1 Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.8_2 Warning: Duplicate INDEX entry: php5-imlib2-0.1.00 Warning: Duplicate INDEX entry: cvsup-without-gui-16.1h_2 Warning: Duplicate INDEX entry: mod_rpaf-0.5 Done. /usr/ports# echo $? 0 /usr/ports# Are you using different build technology than ``make index''? Yes, see the tindex script. Kris pgpjaqUIceRB6.pgp Description: PGP signature
Re: INDEX build failed for 4.x
On Wed, Sep 27, 2006 at 02:20:35AM -0400, Kris Kennaway wrote: On Wed, Sep 27, 2006 at 09:04:19AM +0300, Vasil Dimov wrote: [...] Are you using different build technology than ``make index''? Yes, see the tindex script. Ah, now I see that if anything comes to stderr during ``make index'' than index build is considered broken, thanks for pointing this and sorry for the noise :) -- Vasil Dimov [EMAIL PROTECTED] % Only a fool has no doubts. pgp1EdWr7x446.pgp Description: PGP signature
Re: INDEX build failed for 4.x
On Mon, Aug 28, 2006 at 10:16:57AM -0500, Donald J. O'Neill wrote: On Monday 28 August 2006 09:06, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait.. Done. make_index: htdig-3.2.0.b6_2: no entry for /usr/ports Hello Irwin, Dear Donold :-) Committers on the hook: clsung dougb jylefort krion miwi pav sat skv sumikawa ^^^ this indicates the short list of who is likely to blame for the error. I'm curious. Do you have a purpose in sending all these messages to the list? It's reporting errors that will be seen by users in various situations (e.g. trying to build a certain port, or trying to build the index), as a reminder to whoever broke it (or their collaborators) that it needs fixing, and a warning to users who monitor the list and may encounter the same error. Kris pgp0TQTj8tibC.pgp Description: PGP signature
Re: INDEX build failed for 4.x
On Mon, 2006-08-28 at 10:20 +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait.. Done. make_index: htdig-3.2.0.b6_2: no entry for /usr/ports I don't know if that's a case where I can by-pass maintainership, but if you feel like doing it yourself : http://lists.freebsd.org/pipermail/cvs-ports/2006-August/103863.html -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
Re: INDEX build failed for 4.x
On Monday 28 August 2006 09:06, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait.. Done. make_index: htdig-3.2.0.b6_2: no entry for /usr/ports Committers on the hook: clsung dougb jylefort krion miwi pav sat skv sumikawa Most recent CVS update was: U audio/Makefile snip - to protect whoever U www/campsite/distinfo U www/campsite/pkg-plist U www/campsite/files/patch-transfer_images.php U x11-fm/gentoo/Makefile U x11-fm/gentoo/distinfo U x11-fm/gentoo/pkg-plist U x11-wm/pawm/Makefile U x11-wm/pawm/distinfo U x11-wm/pawm/files/patch-src__pafont.c Hello Irwin, I'm curious. Do you have a purpose in sending all these messages to the list? Are you asking a question without actually asking it? Making a statement of some kind without explicitly saying what it is? What? Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INDEX build failed for 4.x
Donald J. O'Neill wrote: [snip] I'm curious. Do you have a purpose in sending all these messages to the list? Are you asking a question without actually asking it? Making a statement of some kind without explicitly saying what it is? What? Well, the world is imperfect, and sometimes the automated bots run by us will not be able to explicitly point out which port is getting problem... All the purpose of this sort of letters (e.g. tinderbox build failure reports, etc) is in the hope that someone can pick up the work and fix it before users actually being hit by a bug and thus save their time. In other words, this is something like Look out! Ports tree have some *known* trouble now and please do not report problems (without patch, of course) until things gets fixed. Cheers, -- Xin LI [EMAIL PROTECTED] http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: INDEX build failed for 4.x
On Monday 28 August 2006 10:27, LI Xin wrote: Well, the world is imperfect, and sometimes the automated bots run by us will not be able to explicitly point out which port is getting problem... All the purpose of this sort of letters (e.g. tinderbox build failure reports, etc) is in the hope that someone can pick up the work and fix it before users actually being hit by a bug and thus save their time. In other words, this is something like Look out! Ports tree have some *known* trouble now and please do not report problems (without patch, of course) until things gets fixed. Cheers, Thank you for your reply. Tinderbox failure reports I understand. I guess this type of report goes into my ignore category, unless I'm willing to help of course. Not in this case though, I only have 6-STABLE systems. Don ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INDEX build failed for 4.x
On Mon, Aug 28, 2006 at 10:53:39AM -0500, Donald J. O'Neill wrote: On Monday 28 August 2006 10:27, LI Xin wrote: Well, the world is imperfect, and sometimes the automated bots run by us will not be able to explicitly point out which port is getting problem... All the purpose of this sort of letters (e.g. tinderbox build failure reports, etc) is in the hope that someone can pick up the work and fix it before users actually being hit by a bug and thus save their time. In other words, this is something like Look out! Ports tree have some *known* trouble now and please do not report problems (without patch, of course) until things gets fixed. Cheers, Thank you for your reply. Tinderbox failure reports I understand. I guess this type of report goes into my ignore category, unless I'm willing to help of course. Not in this case though, I only have 6-STABLE systems. This is also broken on 6.x. That only 4.x is reported is an artefact of the script that tests 4.x, 5.x, 6.x and 7.x in that order and only reports the first failure. But you're right, for most people, these mails fall in the same category as the tinderbox mails. You can note that there is an error in the tree, but probably not do much else with it. Cheers, -erwin -- Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_///[EMAIL PROTECTED] And it makes you cry.) ([EMAIL PROTECTED] pgppPRlL4bUVK.pgp Description: PGP signature
Re: INDEX build failed for 4.x
Florent Thoumie wrote: On Mon, 2006-08-28 at 10:20 +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait.. Done. make_index: htdig-3.2.0.b6_2: no entry for /usr/ports I don't know if that's a case where I can by-pass maintainership, but if you feel like doing it yourself : http://lists.freebsd.org/pipermail/cvs-ports/2006-August/103863.html Can someone explain to me why that's necessary? (Other than, all ports that interact with apache must have it.) Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INDEX build failed for 4.x
On Mon, 2006-08-28 at 10:29 -0700, Doug Barton wrote: Florent Thoumie wrote: On Mon, 2006-08-28 at 10:20 +, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX - please wait.. Done. make_index: htdig-3.2.0.b6_2: no entry for /usr/ports I don't know if that's a case where I can by-pass maintainership, but if you feel like doing it yourself : http://lists.freebsd.org/pipermail/cvs-ports/2006-August/103863.html Can someone explain to me why that's necessary? (Other than, all ports that interact with apache must have it.) In your case, it sets a default value for APACHE_PORT, at least. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
