Bugzilla Bug 220847

I don't know what else to say about this. It just doesn't compile.

Reproducible: Always

Steps to Reproduce:
1. emerge yap
Actual Results:  
fails to compile.


/usr/include/sys/types.h:35: error: expected '=', ',', ';', 'asm' or
'__attribute__' before 'u_char'
make: *** [arrays.o] Error 1
make: *** [absmi.o] Error 1
 * 
 * ERROR: dev-lang/yap-5.1.2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4293:  Called die
 * The specific snippet of code:
 *       emake || die "emake failed"
 *  The die message:
 *   emake failed
 * 
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/dev-lang/yap-5.1.2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/dev-lang/yap-5.1.2/temp/environment'.
 * 
!!! When you file a bug report, please include the following information:
GENTOO_VM=sun-jdk-1.6  CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.6.0.06"
JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""

Created an attachment (id=152415) [details]
yap-5.1.2-x86_64-emergeinfo_buildlog

All in one file.

Please update your portage and the "system" set before reporting *any* further
bugs:

>>>  [1m [37mcfg-update-1.8.2-r1 [0m [0m: Creating checksum index...
setup
/usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
NOTICE: The portage_dep module was replaced by portage.dep
/usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
NOTICE: The portage_dep module was replaced by portage.dep
/usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
NOTICE: The portage_dep module was replaced by portage.dep
  [32;01m* [0m Using: sun-jdk-1.6

After you have done this and this problem persists, please reopen this bug.

(In reply to comment #2)
> Please update your portage and the "system" set before reporting *any* further
> bugs:
> 
> >>>  [1m [37mcfg-update-1.8.2-r1 [0m [0m: Creating checksum index...
> setup
> /usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
> NOTICE: The portage_dep module was replaced by portage.dep
> /usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
> NOTICE: The portage_dep module was replaced by portage.dep
> /usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
> NOTICE: The portage_dep module was replaced by portage.dep
>   [32

(In reply to comment #2)
> Please update your portage and the "system" set before reporting *any* further
> bugs:
> 
> >>>  [1m [37mcfg-update-1.8.2-r1 [0m [0m: Creating checksum index...
> setup
> /usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
> NOTICE: The portage_dep module was replaced by portage.dep
> /usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
> NOTICE: The portage_dep module was replaced by portage.dep
> /usr/lib64/portage/pym/portage_dep.py:39: DeprecationWarning: DEPRECATION
> NOTICE: The portage_dep module was replaced by portage.dep
>   [32;01m* [0m Using: sun-jdk-1.6
> 
> After you have done this and this problem persists, please reopen this bug.
> 

The message is from portage-2.2. It is simply a notice that the module in
question is deprecated. My system is updated, And since there are few packages
that have been updated to portage-2.2, this is a message that will continue to
be present for every package which isn't. I will have nothing further to add to
this bug. It will remain as it is. Good luck with the next guy.

Shingoshi

Er, Xavian, is it really so hard to reopen the bug after you've responded?

Can you attach both config.h and config.log? Your problems are stemming from
there.

Thanks

Keri

I stumbled across the same problem, the problem is caused, because configure
generates:
/* #undef   FFVAX               /* manual */ */
in config.h

This is caused by a faulty config.h.in:

#undef   FFVAX                  /* manual */

The comment should be above or beneath the define macro in it's own line.

BTW: Is there any reason why the development version 5.1.2 is in the tree, but
the current stable 5.1.3 is not ?

Removing the eautoconf call from the ebuild solved the problem for me, question
though is, why is eautoconf causing the problem (what does eautoconf do?).

Created an attachment (id=160387) [details]
Correct config.h.in

The autoconf manual clearly states that templates should start with #undef and
end with the symbol/symbol value and that no additional comments should be
present.
This patch modifies config.h.in to obey these rules and thus eliminates the
error posted.

Created an attachment (id=160389) [details]
Updated ebuild to include patch

This ebuild includes the prior posted patch.

Patch applied in CVS. Thanks for sorting this one out lads!

@Sven E.: yap-5.1.3 isn't yet in the portage tree since it doesn't pass a CHR
bootstrap when installing into a sandbox. I'm waiting for upstream to address
this; if I don't hear back from them in a week or so, I'll hack around this
show-stopper by adding a patch to bootstrap the prolog engine for each CHR pass
(icky).

Keri