Opened 15 years ago
Closed 14 years ago
#24339 closed update (fixed)
Add port xmlrpc-c "stable" to macports
Reported by: | bitmail@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), stefano+macports@… | |
Port: | xmlrpc-c |
Description
I'd like to request the addition of the xmlrpc-c "stable" release to the port tree. As of now, macports only features the "super stable" branch, with release 1.06.30 (current 1.06.38) available. This branch lacks some features (i8 support as of 1.07 f.e.) of the more recent branches ("stable" is up to two years old, whereas the "advanced" branch is up to 3 month old). See the projects homepage for details on the different branches and the release cycle.
Attachments (6)
Change History (18)
comment:1 follow-up: 2 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | xmlrpc-c-stable.diff added |
---|
comment:2 follow-up: 3 Changed 15 years ago by bitmail@…
Replying to ryandesign@…:
I updated xmlrpc-c to 1.06.38 in r66030. But why don't we just update the existing xmlrpc-c port to the latest "stable" release? I don't think there was any intention to have our port follow the "super stable" branch; the port is merely unmaintained and hadn't been updated in years.
Attached is a patch which is a start at doing this -- which fails to build for me on Snow Leopard.
Thanks for picking this up! Well, I agree with you regarding switching away from "super stable". But when initially submitting this ticket, I made a mistake, the i8 support I was referring to is only available as of 1.11. And to be honest, that was the major reason for submitting in the first place. Nevertheless, switching to "stable" (atm according to Sourceforge at 1.16.26) would do the trick.
comment:3 follow-up: 5 Changed 15 years ago by bitmail@…
Replying to bitmail@…:
Replying to ryandesign@…:
I updated xmlrpc-c to 1.06.38 in r66030. But why don't we just update the existing xmlrpc-c port to the latest "stable" release? I don't think there was any intention to have our port follow the "super stable" branch; the port is merely unmaintained and hadn't been updated in years.
Attached is a patch which is a start at doing this -- which fails to build for me on Snow Leopard.
Hm, just checked out&build the stable branch manually (i.e. outside port; OSX 10.5.8 PPC), surprisingly it was
Ausgecheckt, Revision 1903.
and not
svn.revision 1871
as in the diff file. I'm not familiar with the syntax etc., but might that be the reason why the build on Snow Leopard failed?
comment:4 Changed 15 years ago by bitmail@…
I did a recheck, despite the message about Rev. 1903, the freshly build xmlrpc-c-config reports version 1.16.26. But the resulting install seems to be borked, as the consecutive make for the files located in examples/ fails and a standalone rtorrent build (--with-xmlrpc-c=/path/to/new/xmlrpc-c-config) still prefers the "old" xmlrpc-c install that ships with macports atm.
comment:5 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to bitmail@…:
Hm, just checked out&build the stable branch manually (i.e. outside port; OSX 10.5.8 PPC), surprisingly it was
Ausgecheckt, Revision 1903.
and not
svn.revision 1871
as in the diff file. I'm not familiar with the syntax etc., but might that be the reason why the build on Snow Leopard failed?
The latest revision of the repository is 1903, but the last changed revision of the stable branch is 1871.
Changed 14 years ago by macports@…
Attachment: | xmlrpc-c-stable_1_06_40.diff added |
---|
Updated stable patch
comment:6 Changed 14 years ago by macports@…
Have attached a patch to bring it up to 1.06.40 which I've at least managed to get to build for me!
comment:7 Changed 14 years ago by bitmail@…
So,
anyone had any luck yet getting the stable branch to work with macports?
comment:8 Changed 14 years ago by claus@…
Some status reports on various attempts to get a more recent xmlrpc-c into macports:
STABLE - does not compile, unrecognized "ld" option --rpath
TRUNK - compiles OK but has introduced a change which breaks compat
1.25.00 - compiles OK but has same change as trunk
1.24.00 - compiles OK but has same change as trunk
1.22.00 - does not compile, missing the .configure script?
1.19.05 - does not compile, unrecognized "ld" option --rpath
1.17.08 - does not compile, "make all" fails
1.14.00 - does not compile, GCC does not like a particular source syntax (undeclared (ulong))
1.9.0 - does not compile, missing .configure script and macport's libtool is wrong version
1.7.0 - does not compile at all
But I did manage to get the stable branch installed on my system. What I did was:
- use Portfile-xmlrpc-c.diff to patch xmlrpc-c portfile (force "stable" branch download)
- let "sudo port install xmlrpc-c" fail
- go to the build-directory and find the working directory
- make clean
- sudo ./configure
- sudo make
- sudo make install
This approach allows xmlrpc-c 1.16.32 to compile and install, but it does circumvent macports and prevents xmlrpc-c from being registered as an installed package.
Other packages using xmlrpc-c will therefore fail to compile, giving you the message that xmlrpc-c could not be installed. It's poor practice, I know, but if like me you only have a single other package installed which requires xmlrpc-c and you really-really-really need xmlrpc-c 1.7.0 or above due to 64bit integer support, then you can certainly edit the Portfile for rtorrent-devel and comment out the part that adds xmlrpc-c as a dependency when +xmlrpc is used.
Rtorrent-devel will still fail to build. However, the above approach using a manual install also works for this package. Et voila - everything works, but you've shot yourself quite thoroughly in the foot in regards to future updates.
But it does work well... so far.
Hope this helps some of you.
Cheers, Claus / DK
Changed 14 years ago by claus@…
Attachment: | Portfile-xmlrpc-c.diff added |
---|
Brings stable / 1.16.32 into macports
comment:10 Changed 14 years ago by dan@…
I was able to build the most recent stable version (1.16.33) by editing the config.mk after build failed. I removed a hyphen (-) from in front of rpath.
Pre-change: Line 36
CURL_WL_RPATH = -Wl,--rpath -Wl,/opt/local/lib
Post-change: Line 36
CURL_WL_RPATH = -Wl,-rpath -Wl,/opt/local/lib
Packages dependent on xmlrpc-c build and function correctly as well.
Changed 14 years ago by stefano+macports@…
Attachment: | Portfile-xmlrpc-c-1.16.33.diff added |
---|
Port updated for xmlrpc-c v1.16.33
Changed 14 years ago by stefano+macports@…
Attachment: | patch-configure.diff added |
---|
Patch for configure to change --rpath to -rpath
Changed 14 years ago by stefano+macports@…
Attachment: | patch-configure-in.diff added |
---|
Patch for configure.in script to change --rpath to -rpath
comment:11 Changed 14 years ago by stefano+macports@…
With the patches that I've uploaded I was able to build the 1.16.33 version. But rtorrent, linked against the new xmlrpc-c start to give me oddly problems (dyld: Library not loaded: libxmlrpc_server.3.16.dylib), except when I run it from the /opt/local/lib directory.
comment:12 Changed 14 years ago by jmroot (Joshua Root)
Keywords: | xmlrpc-c stable removed |
---|---|
Port: | xmlrpc-c added; xmlrpc removed |
Resolution: | → fixed |
Status: | new → closed |
Type: | request → update |
Version: | 1.8.2 |
I updated xmlrpc-c to 1.06.38 in r66030. But why don't we just update the existing xmlrpc-c port to the latest "stable" release? I don't think there was any intention to have our port follow the "super stable" branch; the port is merely unmaintained and hadn't been updated in years.
Attached is a patch which is a start at doing this -- which fails to build for me on Snow Leopard.