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
A little list of build issues #21
Comments
Hey there, thanks for trying it and the report! About the forum, there is the oil-dev@ list, which is not very active at the moment, link on the home page: Until there are a lot of people using Oil, I think e-mail will work better than IRC. Can you first try the release tarball? I think you are building out of the repo, which is a bit more complicated. http://www.oilshell.org/blog/2017/07/23.html If you want to build out of the repo, try this: https://github.com/oilshell/oil/wiki/Contributing I would appreciate feedback on that, because I'm not sure if anyone has done it lately. There is the
Hm it doesn't print an error message? If so, that's a bug.
I don't quite understand why adding headers would make it NOT fail? It's definitely possible that the What platform are you building on? |
The platform is:
I'd personally prefer to not need to use a release tarball, a good litmus test of any project is how well maintained and simple their build infrastructure is. If I have to use a release tarball for a build system issue, I'd consider that an issue.
I think the release instructions should work as advertised. If this is still too early in the project's development then I can try again some other time.
It clearly tries to but the redirections in the
It mainly needs
Shame about IRC |
OK, thanks for the report about readline: There are two different sets of instructions:
This is a well-known distinction. If you use autoconf, then The release tarball directions have been fairly well tested, although there are bugs in issue #16. The dev instructions were changed recently and might need a little work. You actually don't need to run |
OK I changed the Makefile so the |
If you were going to use autotools then I'd have simply used |
Perhaps 373f06b fixed an issue with Apologies for not complying, but I'll perhaps try again in a few months or when there's no longer two different build systems. I'll close this for now as you have fixed the real main issue which was readline detection. Thanks. Edit: I've also updated my first reply to explain more clearly why no error messages are being printed in the |
Sure, but you said the instructions don't work, but I'm saying that every project has two sets of instructions, for a tarball vs. repo build. One of them might be implicit (do the standard autoconf thing), but it's still two different things. FWIW the script to build the release tarball is here: https://github.com/oilshell/oil/blob/master/scripts/release.sh Although this will evolve. It's an explicit two-step build:
The developer build system will be complex for the forseeable future, see: http://www.oilshell.org/blog/2017/05/05.html http://www.oilshell.org/blog/2017/04/25.html Unless someone wants to write an Python/Oil VM for me that is easy to build :) However, the user build system is simple. Almost all of the complexity is hidden behind the release tarball. If I didn't have this two-step build (which almost all other projects have), then you would need to install Python to build Oil. I took care to make sure that Python wasn't a build-time dependency for the tarball. |
OK, the |
Also I don't see an edit in the original message about why configure is silently failing? If |
I don't agree that the build system needs to be complex at all, but it's your project. Edit: Just to be clear, I was only trying to see how the build was coming since I had pretty high hopes for this effort. One of the main issues with I'm not much of a contributor, I had only noticed a few issues and wanted to quickly communicate my experience and IRC would have been a perfect channel for such inconsequential reporting. Either way, don't worry about me, focus your efforts on your proper contributors. |
Ah that configure bug is embarrassing. Thanks for the report! I think that was a record number of bugs reported and fixed at once :) The developer build system is complicated because I need Python to help me contain the complexity of bash. In other words, I shipped the Python prototype. There's no way I could have finished it in a reasonable amount of time in C or C++! But this complexity is only for Oil developers -- I hid all the complexity for the system packagers and end users. But I'm glad to get these little issues fixed so that people aren't put off from contributing. However, developers have a 3rd way of running the code: just use the system Python interpreter, rather than the one I bundled with the release to avoid a Python dependency. That is what's documented in the Contributing wiki page. I actually hadn't documented how to make the tarball, although I gave a link to Thanks for trying it! |
A couple of small issues related to distribution and packaging. This would ideally be handled on IRC but it appears oilshell doesn't advertise a channel anywhere I could find.
Currently using the commit a6bc98e
So far this in my experience trying to build this software. I start with
./configure --help
which tells me I can use--with-readline
and it appears to support the--prefix
mechanism.Running the command
./configure --prefix=/usr --with-readline
simply exits with a return status of 1.When using
sh -x
(since the script defines itself to be/bin/sh
) it seems to show the intended error indicating a failure to detect readline:This appears to be due to the
detect-readline.c
not including the relevant headers as documented in the manual (at least for readline 7.0):I wish readline would get a .pc file...
After fixing this the initial
./configure
command seems to succeed with the message:However when running
make
I am faced with the following issues:This is just a simple laundry list of issues which could have been discussed elsewhere but github seemed like the only place.
The text was updated successfully, but these errors were encountered: