Re: serfmake doesn't generate serf-1.pc file

17 views
Skip to first unread message

Gabriela Gibson

unread,
May 18, 2013, 5:28:28 PM5/18/13
to serf...@googlegroups.com
On 18/05/13 04:58, Justin Erenkrantz wrote:

Hi,

I tried and failed to post to the serf-dev list, and mailed Justin directly, he asked me to try posting again, this failed too, and so I'm using googlegroups to post this.  This is the discussion so far:

With respect to your email, we've moved towards "scons" in trunk of serf
- so you should just be able to install that (apt-get install scons) and
you be good to go.  It's quite likely that we haven't updated all of the
documentation just yet.  Patches are very much appreciated!  =)

I think I've found the bug that causes the problem described below in the serf "serfmake" python script in serf-1.2.0 obtained from

http://serf.googlecode.com/files/serf-1.2.0.tar.bz2

If you run "serfmake install" without calling "serfmake build",
it calls
>   builder.install_target(File('.', LIBNAME, 'la'), False)
which in turn calls
>   self.build_target(target, dry_run)

However, running "serfmake build" calls both
>   builder.build_target(File('.', LIBNAME, 'la'), False)
>   builder.build_target(File('.', PCFILE, 'pc'), False)

This is an issue because the README suggests running "serfmake
install" without the prior step of "serfmake build".  I do notice
now that this advice is for "non-packaged releases" though.

If you add the line below in the patch, it all works fine.

[[[
--- serf/serfmake    2012-12-09 18:56:19.000000000 +0000
+++ serf.work2/serfmake    2013-05-18 21:57:48.233982634 +0100
@@ -145,6 +145,7 @@
 def cmd_install(param):
   builder = Builder(param)
   ### should be called .install_all()
+  builder.build_target(File('.', PCFILE, 'pc'), False)
   builder.install_target(File('.', LIBNAME, 'la'), False)
]]]

Gabriela


On Fri, May 17, 2013 at 4:40 AM, Gabriela Gibson wrote:

    -------- Original Message --------
    Subject: serfmake doesn't generate serf-1.pc file

    Hi,

    I upgraded to Ubuntu 12.10 and got the latest svn trunk, and had
    some difficulties with serf.  The python version is 2.7.3

    I tried following the instructions in serf/README and serfmake.

    I cannot get serfmake to work, but had better luck with buildconf.

    Here is what I found when trying to use serfmake:

    1. README suggests --with-serf=/usr/local/serf, serfmake suggests
    --with-serf=/usr/local.  I tried both, and neither worked.
Oops, meant --prefix= ...


    2. serfmake breaks like so:

    g@musashi:~/trunk/serf$ sudo ./serfmake --prefix=/usr/local
    --with-apr=/usr/local/apr --with-apr-util=/usr/local/apr install
    Installing: serf.h
    Installing: serf_bucket_types.h
    Installing: serf_bucket_util.h
    Installing: serf-1.pc
    ERROR: exception:
    [Errno 2] No such file or directory: 'serf-1.pc'

    serfmake [cmd] [options]
    Commands:
             build   Builds (default)
             check   Runs test cases
             install Installs serf into PREFIX
             clean   Cleans
    Options:
             --with-apr=PATH         prefix for installed APR and APR-util
                                     (needs apr-1-config and
    apu-1-config; will look in PATH)
             --with-gssapi=PATH      build serf with GSSAPI support
                                     (needs krb5-config; will look in
    PATH/bin)
             --prefix=PATH           install serf into PATH (default:
    /usr/local)
    Quick guide:
             serfmake --prefix=/usr/local/serf --with-apr=/usr/local/apr
    install

    ----

     From what I can see, it appears that _write_pcfile(self) does not
    get called (I put a debug marker in) and so, the file serf-1.pc
    is never generated.


I
    regards,

    Gabriela

    [1] We're writing to let you know that the group you tried to
    contact (serf-dev) may not exist, or you may not have permission to
    post messages to the group.



Lieven Govaerts

unread,
May 20, 2013, 10:22:18 AM5/20/13
to serf...@googlegroups.com
Hi Gabriela,

On Sat, May 18, 2013 at 11:28 PM, Gabriela Gibson <gabriel...@gmail.com> wrote:

On 18/05/13 04:58, Justin Erenkrantz wrote:

Hi,

I tried and failed to post to the serf-dev list, and mailed Justin directly, he asked me to try posting again, this failed too, and so I'm using googlegroups to post this. 

Hm, being member of the serf-dev group should allow you to send mails to it. Strange. Are you using different email addresses maybe?
 
This is the discussion so far:

With respect to your email, we've moved towards "scons" in trunk of serf
- so you should just be able to install that (apt-get install scons) and
you be good to go.  It's quite likely that we haven't updated all of the
documentation just yet.  Patches are very much appreciated!  =)

I think I've found the bug that causes the problem described below in the serf "serfmake" python script in serf-1.2.0 obtained from

http://serf.googlecode.com/files/serf-1.2.0.tar.bz2

If you run "serfmake install" without calling "serfmake build",
it calls
>   builder.install_target(File('.', LIBNAME, 'la'), False)
which in turn calls
>   self.build_target(target, dry_run)

However, running "serfmake build" calls both
>   builder.build_target(File('.', LIBNAME, 'la'), False)
>   builder.build_target(File('.', PCFILE, 'pc'), False)

Indeed.
 

This is an issue because the README suggests running "serfmake
install" without the prior step of "serfmake build".  I do notice
now that this advice is for "non-packaged releases" though.

If you add the line below in the patch, it all works fine.

[[[
--- serf/serfmake    2012-12-09 18:56:19.000000000 +0000
+++ serf.work2/serfmake    2013-05-18 21:57:48.233982634 +0100
@@ -145,6 +145,7 @@
 def cmd_install(param):
   builder = Builder(param)
   ### should be called .install_all()
+  builder.build_target(File('.', PCFILE, 'pc'), False)
   builder.install_target(File('.', LIBNAME, 'la'), False)
]]]

I've tested your patch and it solves the issue, so I've applied it on the 1.2.x branch in r1865.
  
Gabriela

Thanks!

Lieven
 

--
You received this message because you are subscribed to the Google Groups "Serf Development List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to serf-dev+u...@googlegroups.com.
To post to this group, send email to serf...@googlegroups.com.
Visit this group at http://groups.google.com/group/serf-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Gabriela Gibson

unread,
May 21, 2013, 2:40:40 PM5/21/13
to serf...@googlegroups.com

Gabriela Gibson

unread,
May 21, 2013, 2:51:54 PM5/21/13
to serf...@googlegroups.com
Hi Igo,

I was not a member of this Google Group and had to become one in order to post, and this caused the confusion, along with Googles' not-so-useful reply.

Is there a way you can set what messages are sent to refused mails so people don't think that Google has deleted this group?

Gabriela


 

Lieven Govaerts

unread,
May 22, 2013, 3:28:16 PM5/22/13
to serf...@googlegroups.com
I honestly don't know, only Justin & Greg are owners of this
discussion group, so I don't have access to the group settings.

Lieven

> Gabriela
>

Justin Erenkrantz

unread,
May 22, 2013, 4:05:02 PM5/22/13
to serf...@googlegroups.com
I didn't see any options to alter the text of the failure message.  -- justin 

Greg Stein

unread,
Jun 8, 2013, 6:18:44 PM6/8/13
to serf...@googlegroups.com, Gabriela Gibson
On Tue, May 21, 2013 at 2:51 PM, Gabriela Gibson
<gabriel...@gmail.com> wrote:
> I was not a member of this Google Group and had to become one in order to
> post, and this caused the confusion, along with Googles' not-so-useful
> reply.

Just to clear up what is going on here:

The group is set to require membership before posting. That cuts down
on the spam *tremendously*. It was *very* difficult to keep up with
the spam moderation before that switch was enabled.

In addition, the first post of all new members gets moderated (yes,
spammers have even managed to join-then-spam). I moderate their first
post through and set the bit that allows future postings to go
unmoderated.

The serf library requires some technical expertise to work with, so I
never felt that the settings turned people away. (unlike, say,
us...@subversion.a.o)

Based on Gabriela's note, it also sounds like the web interface allows
posting without some of the moderation fences kicking in.

Cheers,
-g
Reply all
Reply to author
Forward
0 new messages