Package Details: libsearpc 2:3.3.0-4

Git Clone URL: https://aur.archlinux.org/libsearpc.git (read-only, click to copy)
Package Base: libsearpc
Description: A simple C language RPC framework (including both server side & client side)
Upstream URL: https://github.com/haiwen/libsearpc
Licenses: Apache
Submitter: aclindsa
Maintainer: thealchemist (Joffrey)
Last Packager: Joffrey
Votes: 87
Popularity: 0.001276
First Submitted: 2013-01-19 15:50 (UTC)
Last Updated: 2024-05-09 09:16 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

<deleted-account> commented on 2013-08-11 10:08 (UTC)

I've had a problem to compile it on my Raspberrry My machine had no "patch, gcc, pkg-config" Would it possible to add this to the depends list.

kevincox commented on 2013-07-20 03:46 (UTC)

I noticed you added armv7h. Would it be possible to add armv6h as well. I have tested it and it works.

kevincox commented on 2013-07-04 01:11 (UTC)

Adding "armv6h" to the "arch" variable allows for use on arm devices such as the raspberry pi.

aclindsa commented on 2013-04-05 14:37 (UTC)

peplin: Ah, I hadn't updated in a few days and hadn't gotten the pacman 4.1 update yet. I'll update the packages.

peplin commented on 2013-04-05 14:21 (UTC)

Follow to the previous comment - prepare is now called automatically in pacman >= 4.1.

peplin commented on 2013-04-05 14:20 (UTC)

The call to prepare() at the top of build() is causing problems because the patch is applied twice. The second time it detects that it's already been applied and you're either given the option to reverse the patch (bad) or skip it, which causes the entire install to fail.

aclindsa commented on 2013-04-04 18:08 (UTC)

Are you doing anything different than downloading the tarball, extracting it, and running makepkg? (If you're installing it with pacaur/yaourt/something can you try doing it manually with makepkg to see if you can reproduce the problem that way?)

aclindsa commented on 2013-04-04 18:06 (UTC)

hobarrera: Interesting - I have never seen that happen before and can't reproduce it now. I'm having trouble thinking of anything that would cause this.

whynothugo commented on 2013-04-04 17:49 (UTC)

Oh, I thought the patch was no longer needed since it looks like it's already applied upstream: ==> Starting build()... patching file libsearpc.pc.in Reversed (or previously applied) patch detected! Assume -R? [n]

aclindsa commented on 2013-04-04 11:51 (UTC)

hobarrera: After looking into it, the patch *is* necessary. Without it, auto-configuration does not work properly for packages which have build requirements on libsearpc (i.e. those build scripts will look for header files at the build path, not the installed path).

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »