[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Manjusaka
Manjusaka added the comment: Finally, I must say when I first build the Python 3.7.0b5, I don't use Pyenv or others tools. As you say, It should be a PATH problem. I build success without no patch in a clean Mac. I think I will figure out what's wrong. But just as what I say, You can't ens

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Ned Deily
Ned Deily added the comment: As I said, I do not recall ever seeing a failure like this before and I regularly build and test Python on macOS in many different versions and environments. It would be very time-consuming to try to debug your environment remotely, time that would be better spe

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Manjusaka
Manjusaka added the comment: it seems like what you say but I think that you can't ensure everyone has a clean path especially when people use some tools such as pyenv or others to build Python from source code, but not get the binary package directly. Anyway, it's just a personal idea. Tha

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Ned Deily
Ned Deily added the comment: The only really suspicious thing I see is that your shell PATH is *gigantic*. pulling things in from all over the place including Homebrew. If you want to pursue further, suggest you try a clean build from the tarball without the modification and use a simple PA

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Manjusaka
Manjusaka added the comment: The result in here https://gist.github.com/Zheaoli/86b04395748b998ad7d870a927a95aea -- ___ Python tracker ___ __

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Ned Deily
Ned Deily added the comment: That change should not have affected the macOS build. Now that you have a working python, can you please run: ./python.exe -m test.pythoninfo and report the results here? -- ___ Python tracker

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Manjusaka
Manjusaka added the comment: Actually, I found some interesting problem. In Python 3.6.5 has declared the `extern pid_t forkpty(int *, char *, struct termios *, struct winsize *);` in here https://github.com/python/cpython/blob/3.6/Include/pyport.h#L532 and I add it into the Python 3.7.0b5

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Ned Deily
Ned Deily added the comment: Sorry, I can't reproduce it and I do not recall every seeing a failure like that. Just to be sure, you do mean ".configure" and not "./configuration"? Perhaps you are picking up an old, third-party version of libutil from /usr/local/lib and/or /usr/local/include

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Manjusaka
Manjusaka added the comment: Sure, I already set "xcode-select --install" in terminal Python 3.6.5 build success with a default setting when running ./configuration" command Xcode version is 9.3 System version 10.13.4 -- ___ Python tracker

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Ned Deily
Ned Deily added the comment: Have you run "xcode-select --install" to ensure system header files are installed? If so, what compiler are you using from what source? What version of macOS are you using? https://devguide.python.org/setup/#macos -- nosy: +ned.deily _

[issue33756] Python 3.7.0b5 build error

2018-06-03 Thread Manjusaka
New submission from Manjusaka : When I build 3.70.b5 in Mac , the compiler raise an error show that "./Modules/posixmodule.c:6018:11: error: implicit declaration of function 'forkpty' is invalid in C99 [-Werror,-Wimplicit-function-declaration] pid = forkpty(&master_fd, NULL, NULL, NULL);"