ALHP/ALHP.GO
7
43
Fork 8
Code Issues 30 Pull Requests Projects Releases Wiki Activity

[Suggestion] Making ALHP aware of failed LTO build #66

New Issue
Closed
opened 2021-11-24 22:47:22 +01:00 by Gontier-Julien · 2 comments
Gontier-Julien commented 2021-11-24 22:47:22 +01:00
Copy Link

For easier debugging of what pacakge fail with LTO, we could make AHLP see at the end of the log if it find error: ld returned 1 exit status/error: ld returned 2 exit status (i think it fine do just try to find error: ld returned).

With that we could do a seperate folder with faild LTO build or do an automatic process that will rebuild said package without LTO.

For easier debugging of what pacakge fail with LTO, we could make AHLP see at the end of the log if it find `error: ld returned 1 exit status`/`error: ld returned 2 exit status` (i think it fine do just try to find `error: ld returned`). With that we could do a seperate folder with faild LTO build or do an automatic process that will rebuild said package without LTO.
anonfunc added the enhancement label 2021-11-25 01:56:45 +01:00
anonfunc commented 2021-11-25 01:56:54 +01:00
Owner
Copy Link

Implemented in 743b08bba1.

Implemented in https://git.harting.dev/anonfunc/ALHP.GO/commit/743b08bba1cb7347be3f1c741a604fb470cb7f95.
👍 2
anonfunc commented 2021-11-25 23:37:48 +01:00
Owner
Copy Link

This should work now. Please reopen if you encounter any new logs that had this error and were not rebuild automatically.

This should work now. Please reopen if you encounter any **new** logs that had this error and were not rebuild automatically.
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked upstream
bug
Something is not working
 build-failure
package build fails
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 informational
Provides information about something
 invalid
Something is wrong
 invalid/corrupt package
Package needs to be rebuild
 packaging issue
priority: high
High priority
 question
More information is needed
 support
wontfix
This won't be fixed
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
anonfunc
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ALHP/ALHP.GO#66
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?