Bug 2817

Summary: main.c
Product: pkg-config Reporter: andy <andy314159pi>
Component: srcAssignee: Scott James Remnant <scott>
Status: RESOLVED INVALID QA Contact:
Severity: blocker    
Priority: high    
Version: unspecified   
Hardware: Other   
OS: AIX   
Whiteboard:
i915 platform: i915 features:

Description andy 2005-03-25 12:44:35 UTC
xlc_r -DHAVE_CONFIG_H -I. -I. -I.-DPKGLIBDIR="\"/usr/local/lib/pkgconfig\""
-I./glib-1.2.8 -g -qfullpath -O3 -qmaxmem=-1 -qtune=auto  -c main.c
"main.c", line 193.35: 1506-196 (E) Initialization between types 
"void*" and "void(*)(struct poptContext_s*,enum poptCallbackReason,const struct
poptOption*,const char*,void*)" is not allowed.
"main.c", line 572.17: 1506-196 (S) Initialization between types "char*" and
"int" is not allowed.
make[2]: *** [main.o] Error 1
make[2]: Leaving directory `/wrk2/pkgconfig-0.15.0'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/wrk2/pkgconfig-0.15.0'
make: *** [all-recursive-am] Error 2

xlc is very standards compliant and this probably represents a real bug.  I have
autconfig and automake to the most recent stable as of march 25,2005.
I do not know what this error means because I am not a C programmer.  If we
re-implement this in Fortran then I can help debug this. Thanks! -Andy 
andy314159pi@yahoo.com
Comment 1 Tollef Fog Heen 2005-03-28 08:15:19 UTC
*** Bug 2816 has been marked as a duplicate of this bug. ***
Comment 2 Tollef Fog Heen 2005-03-28 08:17:34 UTC
*** Bug 2815 has been marked as a duplicate of this bug. ***
Comment 3 Tollef Fog Heen 2005-04-01 22:47:17 UTC
Could you please try again with the latest version found on
http://pkgconfig.freedesktop.org/releases ?
Comment 4 Tollef Fog Heen 2005-04-21 17:21:06 UTC
As I'm not able to reproduce this problem, nor do I get any feedback from the
submitter, I'm closing this bug.
Comment 5 andy 2005-04-21 17:39:30 UTC
ah ha!
I forgot to tell you that your fix worked! 
Thanks!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.