Minor dropbear build tweaks#706
Merged
Merged
Conversation
No functional changes, just refreshed them against my own to double-check and make diff'ing easier.
Disable FORTIFY so that stuff runs on legacy Kindles Tweak a few defaut settings for speed, and to avoid clobbering system files.
Frenzie
approved these changes
Jul 15, 2018
Frenzie
left a comment
Member
There was a problem hiding this comment.
Didn't test but I "like" the hack. ;-)
Contributor
|
Dunno if it's related to this PR. https://api.travis-ci.org/v3/job/407002046/log.txt This dropbear build succeeded thus, but its log is near 4MB too: https://api.travis-ci.org/v3/job/406649732/log.txt But in this dropbear build (and my bump's) log, there is like 20% of the log that are warnings related to the dropbear build: The commit CI succeeded (9K of log shorter, nothing obvious |
Member
Author
|
Gah, there's another Travis limit beyond the "I'll stop showing you stuff on the web UI" one? Grmbl. I'll take care of it (and fix those -I calls, because WTH? :D) |
Member
Author
|
Should be taken care of in #711 ;). |
Member
There's also "don't take more than the x minute timeout". What happened here exactly? |
Member
Author
|
Dropbear did not honor CFLAGS, (upstream issue, fixed, but not in any
release), and clang was being very very very very verbose with the default
warning set, because the lack of custom CFLAGS meant it didn't honor our
attempts at taming those ;).
…On Sat, Jul 28, 2018, 22:41 Frans de Jonge ***@***.***> wrote:
Gah, there's another Travis limit beyond the "I'll stop showing you stuff
on the web UI" one?
There's also "don't take more than the x minute timeout". What happened
here exactly?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#706 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAG1Zr0ZIF5_FiT34af5Z3tMCLKRgVZAks5uLMxigaJpZM4VP-fP>
.
|
Member
Author
|
Which is how we learned that 4MB of logs meant an abort ;p.
…On Sat, Jul 28, 2018, 22:45 NiLuJe ***@***.***> wrote:
Dropbear did not honor CFLAGS, (upstream issue, fixed, but not in any
release), and clang was being very very very very verbose with the default
warning set, because the lack of custom CFLAGS meant it didn't honor our
attempts at taming those ;).
On Sat, Jul 28, 2018, 22:41 Frans de Jonge ***@***.***>
wrote:
> Gah, there's another Travis limit beyond the "I'll stop showing you stuff
> on the web UI" one?
>
> There's also "don't take more than the x minute timeout". What happened
> here exactly?
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#706 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAG1Zr0ZIF5_FiT34af5Z3tMCLKRgVZAks5uLMxigaJpZM4VP-fP>
> .
>
|
Member
|
Huh, I'd have expected something more like at least 10 ('cause it's a rounder number). Oh well. :-P |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hopefully without breaking anything ;).
(Ground-work for minor changes to the plugin to make it easier to test without risking clobbered system files).