[Dibbler-devel] Question regarding dibbler pkg
thomson at klub.com.pl
Wed Nov 20 11:47:54 CET 2013
On 20.11.2013 08:55, snehal wrote:
> We are in the process of adding support for new arch (ppc64le) and
> as part of that we wanted to send patches for config.guess/sub and
> configure as appropriate.
Out of curiosity, can you tell me a bit more about that new arch?
Sending a link to some description would be fine. I tried to google it,
but just found tons of patches to different projects...
Hmmm, I must admit that I'm no automake/autoconf expert.
config.guess/sub was added by libtoolize. I know that if those files are
missing, they are also added by autoreconf -i (a command that I run
frequently, every time I tweak something in configure.ac or any of the
Makefile.am files). But I see that after your patches are applied, they
are not overwritten by autoreconf -i. So I *think* it is ok for me to
> 1) We should send patches to dibbler-devel-request at klub.com.pl mailing
> list ?
Almost. dibbler-devel-request is an alias when you send your subscribe
and unsubscribe requests. To post to the list, you need to send to
dibbler-devel, but since I got your mail, you figured that out already :)
There's a limit of 40KB per post IIRC. I hope you don't need patches
larger than that. If you do, please file a bug in bugzilla and attach it
> 2) Latest config.guess and config.sub w/ ppc64le fix is available @
This one looks good. The only question I have is about this part:
+ if test "$UNAME_PROCESSOR" = unknown ; then
On Mac OS you assume that if the processor is detected as unknown, it is
powerpc. Is this a safe assumption? I think not, but I may be wrong.
Are these your changes or did you use a new automake/autoconf to
generate it? If that is so, which version was that?
I will accept it, but if you used a different (presumably newer than I
have) automake/autoconf, I'd like to install it, regenerate all files
and then apply your patches. This is better than selectively updating
only two files to those generated by a newer tool.
> Do you want to take these from the above sites and spin a new version of
> your package for distro to pick up
For some definition of a spin :) I have not updated tarballs since July.
Ok, it's a high time to finally spin them up.
There's one caveat you should know, though. I'm heading out for a week
long vacation on Saturday and I won't be able to do much about dibbler
before that. I can accept the patches, install automake/autoconf etc,
but I won't have enough time to prepare new release.
Your patches are now available in the git repo. Can you check that they
work for you?
Thanks for sending those patches,
More information about the Dibbler-devel