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

No rule to make target ../../COPYRIGHT', needed by COPYRIGHT'. Stop. #16269

Closed
alvaradoo opened this issue Aug 20, 2020 · 8 comments
Closed

No rule to make target ../../COPYRIGHT', needed by COPYRIGHT'. Stop. #16269

alvaradoo opened this issue Aug 20, 2020 · 8 comments

Comments

@alvaradoo
Copy link

Summary of Problem

When running make, errors are returned saying:
***** main/ *****
make[3]: *** No rule to make target ../../COPYRIGHT', needed by COPYRIGHT'. Stop.
make[2]: *** [main.makedir] Error 2
make[1]: *** [compiler] Error 2
make: *** [comprt] Error 2

Configuration Information

  • Output of chpl --version:
    chpl version 1.22.1
    Copyright 2020 Hewlett Packard Enterprise Development LP
    Copyright 2004-2019 Cray Inc.
    (See LICENSE file for more details)

  • Output of $CHPL_HOME/util/printchplenv --anonymize:
    CHPL_TARGET_PLATFORM: darwin
    CHPL_TARGET_COMPILER: clang
    CHPL_TARGET_ARCH: x86_64
    CHPL_TARGET_CPU: native
    CHPL_LOCALE_MODEL: flat
    CHPL_COMM: none *
    CHPL_TASKS: fifo *
    CHPL_LAUNCHER: none
    CHPL_TIMERS: generic
    CHPL_UNWIND: none
    CHPL_MEM: cstdlib *
    CHPL_ATOMICS: cstdlib
    CHPL_GMP: none *
    CHPL_HWLOC: none
    CHPL_REGEXP: none *
    CHPL_LLVM: none *
    CHPL_AUX_FILESYS: none

  • Back-end compiler and version, e.g. gcc --version or clang --version:
    Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
    Apple clang version 11.0.3 (clang-1103.0.32.62)
    Target: x86_64-apple-darwin19.6.0
    Thread model: posix
    InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

@alvaradoo
Copy link
Author

Did normal source download without using brew install version and it built correctly. Closing issue.

@bradcray
Copy link
Member

@alvaradoo : Back from vacation and curious about this even though you self-resolved it: Was the idea that you did brew install chapel and then tried to do a make of the source as well? (which shouldn't be necessary with the homebrew installation). If so, is there anything in the documentation that you think could/should be clarified to prevent other users from going down this path? Thanks!

@alvaradoo
Copy link
Author

Hi, no the idea is exactly what you had mentioned. I tried to do a make of the source after doing a brew install chapel. I now realize that brew already builds chapel during installation.

I think my confusion arose from following the instructions here, which has the quickstart document in the fourth item, and, after clicking on the quickstart document, thinking I had to rebuild chapel when reading through those instructions.

@bradcray
Copy link
Member

bradcray commented Sep 1, 2020

Thanks for that feedback. So perhaps if the Mac-specific installation instructions only pointed to the Mac-specific documentation (since it in turn points to the Quickstart instructions) while also updating the Mac-specific docs to clarify that you can either install from homebrew or build from source, we'd prevent others from tripping over this. Does that sound right?

@alvaradoo
Copy link
Author

Yes, that sounds perfectly right. I believe that would prevent others from committing the same mistake I did.

bradcray added a commit to bradcray/chapel that referenced this issue Sep 3, 2020
As a result in some confusion expressed in
chapel-lang#16269, I've taken a pass
over the Mac documentation to try to clarify it.  I've also made
changes to the install-mac.html webpage in a separate effort to
avoid sending people to the Quickstart instructions prematurely,
which suggest they'll need to build from source.
@bradcray
Copy link
Member

bradcray commented Sep 3, 2020

Hi @alvaradoo: I ended up doing a bigger change than I'd intended, but I think the net result is still better than what we had before. Would you take a look at the screenshots at #16327 and see whether you think they're a step forward and would've helped with this confusion? Thanks!

@alvaradoo
Copy link
Author

Hi @bradcray. I just took a look at it, and I think that's good! That's much clearer and helps distinguish the Homebrew install & source install as two totally separate entities.

@bradcray
Copy link
Member

bradcray commented Sep 3, 2020

Great, thanks for the quick response! I'll get someone else on the team to review it tomorrow and then merge. Thanks for helping us catch this potential for confusion.

bradcray added a commit that referenced this issue Sep 4, 2020
Refactor Mac docs for clarity

[reviewed by @e-kayrakli]

As a result in some confusion expressed in issue #16269, I've taken
a pass over the Mac documentation to try to clarify it. I've also made
changes to the install-mac.html webpage in a separate effort to
avoid sending people to the Quickstart instructions prematurely,
which suggest they'll need to build from source.  See
#16327 for screenshots of the
changes.

I spent some time thinking about what it would take to eliminate the arguable redundancy between these two pages, but ended up keeping it because I think the right way to get rid of the redundancy would be to eliminate the install-mac.html web page and have it point directly at the Mac-specific docs; but I think that this has the downside of not having a short-and-sweet version of the installation instructions for people who don't need much hand-holding (say, experienced Chapel + homebrew users trying it on a Mac for the first time).
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

No branches or pull requests

2 participants