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

4.0 Windows local build is broken (Trac #556) #688

Closed
smk78 opened this issue Mar 30, 2019 · 3 comments
Closed

4.0 Windows local build is broken (Trac #556) #688

smk78 opened this issue Mar 30, 2019 · 3 comments
Labels
Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour
Milestone

Comments

@smk78
Copy link
Contributor

smk78 commented Mar 30, 2019

Since the last few days of Code Camp I have been unable to locally build !Sasview using setup.py

I am compiling with disable_openmp build -cmingw32 on W7

Eclipse console returns:

running disable_openmp
running build
running build_py
package init file 'src\sas\sascalc\dataloader\readers\schema_init_.py' not found (or not a regular file)
running build_ext
Compiling with mingw32 (64bit=False)

and then terminates.

Putting in a trap show the problem occurs when the build branches into

build_ext.build_extensions(self)

Migrated from http://trac.sasview.org/ticket/556

{
    "status": "closed",
    "changetime": "2016-03-24T18:52:52",
    "_ts": "2016-03-24 18:52:52.593970+00:00",
    "description": "Since the last few days of Code Camp I have been unable to locally build !Sasview using setup.py\n\nI am compiling with disable_openmp build -cmingw32 on W7\n\nEclipse console returns:\n\nrunning disable_openmp\nrunning build\nrunning build_py\npackage init file 'src\\sas\\sascalc\\dataloader\\readers\\schema\\__init__.py' not found (or not a regular file)\nrunning build_ext\nCompiling with mingw32 (64bit=False)\n\nand then terminates.\n\nPutting in a trap show the problem occurs when the build branches into\n\nbuild_ext.build_extensions(self)\n",
    "reporter": "smk78",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "SasView Bug Fixing",
    "time": "2016-03-24T12:31:36",
    "component": "SasView",
    "summary": "4.0 Windows local build is broken",
    "priority": "blocker",
    "keywords": "",
    "milestone": "SasView 4.0.0",
    "owner": "",
    "type": "defect"
}
@smk78 smk78 added this to the SasView 4.0.0 milestone Mar 30, 2019
@smk78 smk78 added Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour Incomplete Migration and removed Incomplete Migration labels Mar 30, 2019
@sasview-bot
Copy link

Trac update at 2016/03/24 17:37:32: krzywon commented:

I just ran setup.py without deleting the old build directory and saw the exact behavior you saw. Try cleaning out the existing one and rerun.

This suggests we might want to do this during setup, or have a clean option for this. We didn't before because of the amount of c compiling that was required.

@smk78
Copy link
Contributor Author

smk78 commented Mar 30, 2019

Trac update at 2016/03/24 18:52:45: smk78 commented:

Nice one Jeff. Your right!

Have committed a change to setup.py to force removal of the build directory before sasview builds.

Am closing this ticket.

@smk78
Copy link
Contributor Author

smk78 commented Mar 30, 2019

Trac update at 2016/03/24 18:52:52:

  • smk78 changed resolution from "" to "fixed"
  • smk78 changed status from "new" to "closed"

@smk78 smk78 closed this as completed Mar 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocker Prevents a different issue from being resolved Defect Bug or undesirable behaviour
Projects
None yet
Development

No branches or pull requests

2 participants