Bug 181340 - Autoconf X checking error with XrmInitialize
Summary: Autoconf X checking error with XrmInitialize
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: autoconf
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Brian Brock
URL: http://www.redhat.com/archives/fedora...
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-13 16:29 UTC by Matthias Saou
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-02-15 11:36:27 UTC


Attachments (Terms of Use)
Updated autoconf-intrinsic patch that fixes upstream bug (1.28 KB, patch)
2006-02-14 18:35 UTC, Toshio Kuratomi
no flags Details | Diff

Description Matthias Saou 2006-02-13 16:29:10 UTC
With :
autoconf-2.59-6
automake-1.9.6-2
libtool-1.5.22-2.2

See the devel list posting linked in the URL field. Basically, after an
autoreconf, the configure X checking fails because of a :

void XrmInitialize( void ) (what the real call should be)

vs.

void XrmInitialize( int ) (what autoconf checks with int=0)

This results in a failed check with :

too many arguments to function 'void XrmInitialize()'

Comment 1 Toshio Kuratomi 2006-02-14 18:35:52 UTC
Created attachment 124634 [details]
Updated autoconf-intrinsic patch that fixes upstream bug

Upstream seems to have munged the function when adopting the debian
maintainer's patch.  The initial report upstream and
ftp.debian.org:/debian/pool/main/a/autoconf/autoconf_2.59a-7.diff.gz has
XrmInitialize() rather than XrmInitialize(0).

Matthias, can you test this?

Comment 2 Matthias Saou 2006-02-15 11:33:18 UTC
It works fine for me now :-)
Now I just need the fix to appear in Rawhide so that I can rebuild synergy in
Extras...

Comment 3 Karsten Hopp 2006-02-15 11:36:27 UTC
fixed in -7, but that may take a while to appear in Rawhide as we're preparing
for  test3

Comment 4 Toshio Kuratomi 2006-02-15 18:18:13 UTC
Issue and patch submitted upstream as well.


Note You need to log in before you can comment on or make changes to this bug.