Skip to content

Conversation

@graebm
Copy link
Contributor

@graebm graebm commented Mar 17, 2023

This hack was an attempt to work around a long-standing bug where we had our include-paths and linker-paths in the wrong order. This was fixed in #455 so we don't need the hack anymore.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This hack was a workaround to a long-standing bug where we had our include-paths and linker-paths in the wrong order. Now that it's fixed, this hackery isn't necessary.
@graebm graebm marked this pull request as ready for review March 17, 2023 22:53
@graebm graebm merged commit 25855db into main Mar 17, 2023
@graebm graebm deleted the remove-hack branch March 17, 2023 23:01
graebm added a commit that referenced this pull request Apr 21, 2023
graebm added a commit that referenced this pull request Apr 21, 2023
…ly. (#469)

**Issue:**
"Remove linker hack (#462)" caused internal Amazon devs to start having issues building Lambda applications.

**Investigation:**
In Amazon's internal build system, dependencies are built as both static and shared libs. "Remove linker hack (#462)"  resulted in a switch from using static libs, to using the shared libs.

Lambda applications need all their runtime dependencies explicitly packaged up. The switch to use shared libs meant devs needed to add a lot more runtime dependencies.

**Description of changes:**
Put back code that forces dependencies to be linked statically, to keep things simple and minimize runtime dependencies.
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

Successfully merging this pull request may close these issues.

2 participants