Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ppc64le entry is needed in config.guess file #91

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 4 comments
Open

ppc64le entry is needed in config.guess file #91

GoogleCodeExporter opened this issue Mar 16, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 6 Nov 2014 at 10:22

@GoogleCodeExporter
Copy link
Author

PowerPC now has the Little Endian version of it. So to make snappy buildable in 
we need ppc64le entry in config.guess file like below,

ppc64le:Linux:*:*)
    echo powerpc64le-unknown-linux-gnu
    exit ;;

Original comment by [email protected] on 6 Nov 2014 at 10:25

@GoogleCodeExporter
Copy link
Author

FWIW, config.sub comes from autotools, so if you just rerun autogen.sh, you 
will get a new version. (We do not maintain this file by hand.) But I agree 
that we will want to do that in the released tarballs at some point, too.

Original comment by [email protected] on 6 Nov 2014 at 10:36

@GoogleCodeExporter
Copy link
Author

It is better to have the entry in the releaed snappy-1.1.1 and snappy-1.1.2 
tarballs since we are using JNI wrapper( xerial github) to build snappyjava in 
PowerPC Little Endian and it fails due to this missing entry.

Original comment by [email protected] on 6 Nov 2014 at 11:20

@GoogleCodeExporter
Copy link
Author

We are of course not going to go back and modify Snappy 1.1.1 or 1.1.2 after 
the fact. Any such fix would be in an 1.1.3 release or similar.

Original comment by [email protected] on 6 Nov 2014 at 11:27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant