Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
L ldpl
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Lartu
  • ldpl
  • Issues
  • #38

Closed
Open
Created Apr 05, 2019 by Lartu@lartu🐕Maintainer

LDPL generated binaries are not static

Created by: dvkt

I tried compiling a simple LDPL program on a linux-arm machine and, while it compiled and ran, it wouldn't run on a different linux-arm machine. I got this error:

$ ./hi-arm 
./hi-arm: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./hi-arm)

Adding compile_line+=" -static-libgcc -static-libstdc++ "; to ldpl.cpp and rebuilding the compiler fixed it:

$ ./hi-arm 
hi, arm!

However the binary size balloons from 90K to 1.5M.

Should LDPL programs be static, like the compiler itself? I think so yea?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking