Re: [PATCH] support for the x32 architecture

Mattia Rizzolo <[email protected]> Fri, 8 Dec 2017 18:33:08 +0100
Newsgroups	gmane.comp.video.xine.devel
Message-ID	<[email protected]>
On Thu, Dec 07, 2017 at 05:59:35PM +0100, Torsten Jager wrote:
> > And yes of course, I'm using a native x32 compiler, so it defaults on
> > building for x32.
> 
> > I suppose this means the configure script is not clever enough though.
> > Consider that I'm running a regular x86-64 kernel, not sure if you're
> > doing checks on it (which you shouldn't, imho).
> 
> 13389:ad1c7438683b contains an auto build time override.

mattia@warren ..QA/0_DONE/xine-lib-1.2/hg/xine-lib-1.2 (hg)-[default] % hg diff -c 13389:ad1c7438683b
abort: unknown revision '13389'!

Also: http://hg.code.sf.net/p/xine/xine-lib-1.2/rev/ad1c7438683b

How would I go about seeing it?

> Maybe it is a better idea to conftest the compiler default only when
> user did not give an explicit host, and force the latter otherwise.
> See "Fix x32 detection 2".

I believe that's what autoconf usually does, isn't it?

> Good lord. The last time I heared "decomissioning" it was Fokushima ??

heh.  It's a quite common word when dealing with machines, but also
google books says it's getting more common over time:
https://books.google.com/ngrams/graph?year_start=1800&year_end=2008&corpus=15&smoothing=7&case_insensitive=on&content=decommission&direct_url=t4%3B%2Cdecommission%3B%2Cc0%3B%2Cs0%3B%3Bdecommission%3B%2Cc0%3B%3BDecommission%3B%2Cc0%3B%3BDECOMMISSION%3B%2Cc0

> > Anyway, I don't really deal with hg myself,
> > I'm keeping the packaging of xine-lib-1.2 in git:
> 
> AFAIK, xine used to reside at git as well. I personally like the hg
> switch because it lets me do almost everything without net.

How would git prevent that?  git is completely decentralized.
Probably you are confusing it with svn?

> > https://anonscm.debian.org/git/collab-maint/xine-lib-1.2.git
> > (probably OT here though ^^)
> 
> What does "OT" mean?

Off Topic

> Did you see that goom animation?

yep!

> > Well, I *could* take a snapshot of the hg repository and package it up,
> > but I don't particularly like to do it, I just prefer to use released
> > tarballs and add patches on top.
> > Were you thinking/suggesting to do that?
> 
> Not for final packaging (there certainly is good reason for not doing
> that there), but for quick testing of recent patches.

yes, I always need to provide an upstream tarball to build a debian
package.
so I've now just done that, a `hg archive` to get a tarball, imported it
and tried again to build it on x32 without any further modification, and
it compiled successfully :)
(It failed to find some plugins files (xineplug_inp_{http,net,pnm,rtsp}.so)
that it was expecting, so it failed to actually produce the .debs, but
that's something that happens on amd64 as well, so the plugin was
probably removed or something?)
So yay!
If you think it would be nice I could upload it to Debian experimental.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
xine-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xine-devel
signature.asc (application/pgp-signature, 833 B)