Bug 30925 – ladcca-0.3.1.ebuild fails during ladcca compile

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Paul Ruhland 2003-10-11 13:23:49 UTC]

compile fails due to undefined constants referenced in 'ladccad/main.c'.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Paul Ruhland 2003-10-11 13:26:33 UTC]

Created attachment 19112 [details]
new ebuild which patches the src prior to configure/make/etc

[Comment 2 Paul Ruhland 2003-10-11 13:27:40 UTC]

Created attachment 19113 [details]
ebuild digest

[Comment 3 Paul Ruhland 2003-10-11 13:28:39 UTC]

Created attachment 19114 [details, diff]
patch to fix undefined constant references in 'ladccad/main.c'

[Comment 4 Martin Holzer (RETIRED) 2003-10-12 11:51:43 UTC]

is this a gcc3 bug ?

[Comment 5 Artem Egorkine 2003-10-16 03:53:40 UTC]

Perhaps not gcc3 bug, but gcc3-related bug.
Anyway, including limits.h hever hurt anyone.
The patch works great, maybe it deserves to
go official?

[Comment 6 Paul Ruhland 2003-10-16 19:01:37 UTC]

I have no idea if it is a gcc bug.  Possibly.

I'd like to say there would be no ill effects from including this here but
I can only speak for my current combination of gcc and glibc.

gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice)
(GNU libc) 2.3.2 (Gentoo Linux 1.4 2.3.2-r1)

Does this compile on earlier versions of gcc and glibc?  The glibc
'/usr/src/limits.h' has to be explicitly included on my system to use any
of these constants (ie. LONG_MAX).

Its definitely some change in either or both gcc and glibc.  Was there some
intended change to enforce this behaviour?  I don't know.

[Comment 7 J. Ellis (RETIRED) 2003-10-16 19:04:12 UTC]

Spoke the developer last night. He has released a 0.3.2 that includes the
patch. I'll try to find time to get into portage tonight (Japan time).

[Comment 8 J. Ellis (RETIRED) 2003-10-17 03:14:49 UTC]

0.3.2 is now in portage. Have fun :/