-
Notifications
You must be signed in to change notification settings - Fork 13k
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
"error occurred: unknown target" when trying to add a new target #135271
Comments
reproduced on nixos and debian by the way! |
Please include more specific repro steps. Best if you have some changes that we can checkout to try to repro locally or look at. The description as is is kinda vague ngl. |
oh the repo im using is on my profile! i havent actually done any porting of the std/pal stuff yet because i am first trying to take care of this error but the repro steps are really just following the docs on how to add a target -w- and setting up the usual information pertaining to one |
the ` is not a ', unfortunately |
oh , is that important , o////o sorry ,,, |
AFAICT this is emitted from |
oh ! i will look into forking cc! unless another solution pops up before i get to that |
not enormously, I was just noting for posterity's sake seems rust-lang/cc-rs#1317 |
Yeah, so:
|
when forking the rust-lang/rust repo and attempting to add support for a new target triple, x will fail to recognise the new target when trying to build the cross compiling rustc
this happens when exactly following the directions laid out by "adding a new target" on the rustc dev guide, so either x has an issue with building the new rustc, or the documentation needs updating!
i've added the target triple to the supported targets macro, included it in the stage0 missing targets array, and (not entirely sure if this is necessary but still did it) supplied a json file with a rough specification of the target platform
the exact error given by x (presumably coming from the rustc used for building) is:
error occurred: unknown target 'my-target-triple'
The text was updated successfully, but these errors were encountered: