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

STINK - Linker #45

Merged
merged 2 commits into from
Dec 9, 2016
Merged

STINK - Linker #45

merged 2 commits into from
Dec 9, 2016

Conversation

larsbrinkhoff
Copy link
Member

@larsbrinkhoff larsbrinkhoff commented Dec 9, 2016

SYS1; TS STINK
SYSEN2; STINK 200
.INFO.; STINK DOC
.INFO.; STINK RECENT

@eswenson1
Copy link
Member

The version of sys1;ts stink in the PI distribution was built from STINK 201. We only have the source for STINK 200. Should we build the executable from this source, or should we use the binary from the PI distribution?

@larsbrinkhoff
Copy link
Member Author

I see three options:

  • Use the 201 binary as is.
  • Build the 200 version from source.
  • Attempt to recreate the 201 source.

I think the last one is the long-term solution. But in the interim any of the fist two is ok.

@larsbrinkhoff
Copy link
Member Author

DRAW; D INFO explains how to use STINK to link a new TS D.

@larsbrinkhoff larsbrinkhoff self-assigned this Dec 9, 2016
@larsbrinkhoff
Copy link
Member Author

I disassembled the built 200 with the binary 201. It was a really small fix, so I'll include it in this pull request.

Fixes #189.

@eswenson1 eswenson1 merged commit e1281db into master Dec 9, 2016
@larsbrinkhoff larsbrinkhoff deleted the lars/stink branch December 9, 2016 19:09
@larsbrinkhoff larsbrinkhoff mentioned this pull request Dec 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants