[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libcdio-devel] Add support for new arch 'ppc64le' in "libcdio" upst

From: Rocky Bernstein
Subject: Re: [Libcdio-devel] Add support for new arch 'ppc64le' in "libcdio" upstream package
Date: Mon, 23 Dec 2013 03:40:02 -0500

Thanks for the clarification and making the test. I honestly wasn't totally
sure what you were talking about.

It doesn't seem wise to make a release to switch to something that it is
alpha or even beta. More prudent is to wait until the libtool changes go
into the general release, and even then, wait a little bit. That seems to
be the strategy of distributions using this package.

When enough changes occur to warrant a new release (or a potentially severe
problem as in the case of 0.91) ,  I'll use whatever is the *current* released
libtool to build the tarball. In fact, I had to update the version of
automake to the latest version because the GNU site wouldn't take the
automake versio, version 1.11, that comes with Ubunutu 12.04.3 LTS due to a
security vulnerability.

So Instead,  I recommend building off of what is in git at some particular
point in time. The 0.92 release is tagged release-0.92, but you can decide
if there are future changes if you want to use those.

I gather all of the tests (run with "make check" or if you have Ruby
installed "make check-short") work? If you have different kinds of CD
medium in your CD/DVD drive(s) additional tests get run; have you've tried
those tests as well? If not, it would be good to do so to before the next
libcdio release. Lately, we've been releasing about once a year.

Working off of the source, you can use whatever version of libtool you
choose since that is not in git. Or do as is found in many distributions
releases of libcdio: write a patch and specify the patch in your packaging
mechanism such as in an rpm or deb spec file. When the patch is to the
libcdio code, please remember to pass that along so it can be included in
the next release.


On Mon, Dec 23, 2013 at 1:51 AM, ravi <address@hidden> wrote:

> On 12/22/2013 03:26 AM, Rocky Bernstein wrote:
>> By "outdated libtool" do you mean something other than the libtool on
>> *alpha* that has yet to go into general release?
> Im referring ""
>    If so, you have a
>> somewhat odd meaning of "outdated".
> Yes, you are right in a way.
>> Also, while on the topic of outdated, the current libcdio version is
>> release 0.92 which you can get from
>> libcdio/libcdio-0.92.tar.gz.
> I have verified "libcdio-0.92" and found that only "config.guess" file has
> "ppc64le" fixes. But not libtool.m4.
> So, is it possible for you to use the aplha libtool and spin off a new
> version of libcdio ? So that we can test libcdio package on ppc64le setup?
>> On Sat, Dec 21, 2013 at 1:19 PM, ravi <address@hidden> wrote:
>>  including mailing list ...
>>> On 11/23/2013 11:52 PM, ravi wrote:
>>>  Hi,
>>>>         We are in the process of adding support for new architecture
>>>> 'ppc64le' (PowerPC 64 Little Endian) and as part of that, We have worked
>>>> with libtool maintainer to get alpha release (links below) that has all
>>>> the needed bits to support building on ppc64le.
>>>> A stable libtool release is expected by end of this year.
>>>> 'libcdio' upstream package didn't build on 'ppc64le' system because of
>>>> outdated
>>>> libtool. hence we request you to use latest libtool alpha release and
>>>> spin off a new version of 'libcdio' package. so that we can test ppc64le
>>>> fixes.
>>>> Latest 'libcdio' source package we picked is from :
>>>> "";
>>>> Thanks,
>>>> Ravi.
>>>>  --
>>> Ravindran
>>> IBM LinuxTechnologyCenter
> --
> Ravindran
> IBM LinuxTechnologyCenter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]