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

divergence to push upstream: $cc vs eval $compile_ok #47

Open
ntyni opened this issue Nov 9, 2017 · 1 comment
Open

divergence to push upstream: $cc vs eval $compile_ok #47

ntyni opened this issue Nov 9, 2017 · 1 comment

Comments

@ntyni
Copy link
Contributor

ntyni commented Nov 9, 2017

Looking for common classes of upstream divergences, I noticed this (from charorder.U):

-if $cc $ccflags -o byteorder byteorder.c >/dev/null 2>&1 ; then
+set byteorder
+if eval $compile_ok ; then

It looks to me like these are equivalent, but our version ('eval $compile_ok') is an improvement as it refactors the compilation command to a centralized place (Compile.U). So these divergences should IMO be pushed upstream.

I couldn't find the history behind these differences but I'm guessing Jarkko improved the units when importing them.

A rough estimate of the affected files is

./ls-diff.pl --pat=Compile|cut -c56-|while read i; do if ./ls-diff.pl -ddp -D-u $i |grep -q '^-.*ccflags'; then echo $i; fi; done | wc -l
36

which probably gives some false positives of course. Most of the files have other divergences too, but those can be dealt with separately.

Thoughts welcome.

@Tux
Copy link
Collaborator

Tux commented Nov 12, 2017

I think this pre-dates Jarkko's work and can be Andy's improvements

I think that all units that require Compile.U can be "upgraded" to $compile_ok and then pushed upstream hoping for acceptance

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

No branches or pull requests

2 participants