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

rust plugin: fix linker on i386 #2580

Merged
merged 2 commits into from
Jun 7, 2019

Conversation

dalance
Copy link
Contributor

@dalance dalance commented Jun 5, 2019

On i386 environment, linker becomes i386-linux-gnu-gcc according to
arch_triplet. It causes the following error on build.snapcraft.io:

error: linker `i386-linux-gnu-gcc` not found
  |
  = note: No such file or directory (os error 2)

To fix it, I added _get_linker method to adjust linker name.

  • Have you followed the guidelines for contributing?
  • Have you signed the CLA?
  • Have you successfully run ./runtests.sh static?
  • Have you successfully run ./runtests.sh tests/unit?

On i386 environment, linker becomes i386-linux-gnu-gcc according to
arch_triplet. It causes the following error on build.snapcraft.io:

error: linker `i386-linux-gnu-gcc` not found
  |
  = note: No such file or directory (os error 2)

To fix it, I added _get_linker method to adjust linker name.
@sergiusens
Copy link
Collaborator

Hi there, thank you for your contribution.
The static tests for this PR are currently failing as we do require a signed CLA to be able to contribute, this is the current output:

dalance@gmail.com (https://api.launchpad.net/1.0/~dalance) has NOT signed the CLA

The checklist mentions you have signed the CLA though, if so, was it with another account?

@dalance
Copy link
Contributor Author

dalance commented Jun 6, 2019

The account is correct. At the time of CI, CLA may be under checking.
I received e-mail "You have been added to contributor-agreement-canonical" at 2019/6/5 14:37 UTC.
Could you re-run the check?

@sergiusens
Copy link
Collaborator

that did the trick @dalance

@sergiusens
Copy link
Collaborator

Failed tests are not relevant and being dealt with elsewhere:

  • google:ubuntu-16.04-64:tests/spread/plugins/catkin/legacy-pull
  • google:ubuntu-16.04-64:tests/spread/plugins/plainbox/provider-with-deps

@sergiusens sergiusens merged commit 261ec59 into canonical:master Jun 7, 2019
sergiusens pushed a commit to sergiusens/snapcraft that referenced this pull request Jul 25, 2019
On i386 environment, linker becomes i386-linux-gnu-gcc according to
arch_triplet. It causes the following error on build.snapcraft.io:

    error: linker `i386-linux-gnu-gcc` not found
      |
      = note: No such file or directory (os error 2)

To fix it, I added _get_linker method to adjust linker name.
sergiusens pushed a commit to sergiusens/snapcraft that referenced this pull request Jul 25, 2019
On i386 environment, linker becomes i386-linux-gnu-gcc according to
arch_triplet. It causes the following error on build.snapcraft.io:

    error: linker `i386-linux-gnu-gcc` not found
      |
      = note: No such file or directory (os error 2)

To fix it, I added _get_linker method to adjust linker name.
sergiusens pushed a commit that referenced this pull request Sep 10, 2019
On i386 environment, linker becomes i386-linux-gnu-gcc according to
arch_triplet. It causes the following error on build.snapcraft.io:

    error: linker `i386-linux-gnu-gcc` not found
      |
      = note: No such file or directory (os error 2)

To fix it, I added _get_linker method to adjust linker name.
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