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
gd does not build after relocation #18816
Comments
comment:1
Hi Arvind, I highly suspect your problem is related to this sage-devel discussion. Is this a binary, as I assume it is? It's interesting that you were able to update 6.2 to 6.4 on it! Volker or Jeroen, I'm wondering whether there is anything else we can do (in your experience with releasing) to avoid this kind of thing, or whether it's just not possible. These things always seem to come up but apparently we haven't gotten the "don't develop with binaries" out enough - and apparently some people do experience success there. |
comment:2
IMHO it is a mistake to ship "binary tarballs" consisting of source code and random build artifacts. Can't work reliably, which is why nobody else does that. Thats not to say that it isn't the fault of our build system, which it totally is. Others have solved binary packaging before so you don't have to compile everything from scratch all the time. Hashdist is working on it (https://github.com/hashdist/hashdist/wiki/HDEP-1:-Crating-System-for-Redistributing-Packages) A kind of bandaid would be to have some makefile rule that runs "make distclean" before "make" in a binary build. |
comment:3
Could you please explain more in detail what you mean with this? Which commands did you execute? There are two things you could try:
This will force rebuilding of every package. With some luck, it will solve your problem. |
comment:4
Replying to @vbraun:
...assuming a fixed installation directory. |
comment:5
So much stuff already said. I seem to have been added from the start. As Jeroen said not long ago running The problem here is almost certainly that you get the include directory from |
comment:6
Replying to @jdemeyer:
That has been solved for a long time, but that is not what I meant. The destination directory in Conda and the Hashdist proposal is not tied to the build directory. |
comment:7
Dear Karl (and others), Thanks for your prompt replies. I will follow the instructions from your sage-devel link tonight and see if it works. Maybe I am misunderstanding what "binary" means, but I don't think I am doing that. I am using git and I followed the procedures exactly from the http://wiki.sagemath.org/TentativeConventions#Get_the_latest_official_stable_version_and_development_version_of_Sage document (in response to jdemeyer's comment). I have followed them in the past without troubles. More updates in 10-12 hours! |
comment:8
Replying to @ayyer:
I am afraid that you are then doing something different from what you think you are doing. The path you are seeing refers to the OS X buildbot. The only way how that can appear in your install is if you downloaded a binary build of Sage. It's impossible for that path to appear if you're building from the git sources. |
comment:9
Replying to @jdemeyer:
I am sorry, but I don't see how that is possible. This is exactly what I did in this order.
Karl-Dieter helped me set up xcode and git on my Mac last July and I have never downloaded the binaries since. I will run make distclean and make start as suggested in the link. |
comment:10
|
comment:11
PS: You can use |
comment:12
Replying to @ayyer:
What matters is what you did before the above commands. How did you obtain the sources in the first place? Also, are you sure that you have only one Sage installation on your system? |
comment:13
Replying to @ayyer:
The "since" seems to imply that you did at one point install a Sage binary. |
comment:14
Replying to @jdemeyer:
I didn't do anything related to the installation of sage before typing those commands, if that's what you mean. If I understand vbraun 's comments above, then git fetch origin would fetch the latest sources, right?
Yes.
I was just trying to be precise. I don't remember any more, but I highly doubt it. |
comment:15
Replying to @ayyer:
You certainly must have. The command So there is still the question of how you obtained that original git tree. And, despite what you think, the answer is that you downloaded a binary (possibly by mistake). In any case, did you try the suggestions in [comment:3]? |
comment:16
Replying to @vbraun:
make distclean followed by make start did the trick. Thanks everyone. How do I mark that this ticket is solved? |
Reviewer: Jeroen Demeyer, Arvind Ayyer, Karl-Dieter Crisman |
comment:17
We can do that. Moral of the story is for us to have people avoid developing with binaries... |
comment:20
I think there really is a bug here... |
comment:21
Okay, but we need a new title then. Modify if this isn't accurate. |
comment:23
Replying to @ayyer:
Oops! Question-mark help does not work within sage anymore. Could you help me fix this? I find this feature extremely useful. Thanks. If you like, I can open this as a separate ticket. search_src() works properly though. Here is the error I get.
|
comment:24
Relocation is no longer support anyway. |
Hi,
I'm having trouble upgrading from Sage-6.4 to Sage-6.7 on my Macbook Pro. The installation aborts at the libgd-2.1.1.p0 stage with the following error:
The ft2build.h file is in the local/include/freetype2 subdirectory.
I think the problem is in the -I/Users/buildbot/build/sage/bsd-1/sage_git/build/local/include/freetype2 part, which seems incorrectly copy-pasted from someone else's computer (I don't have the buildbot directory on my computer!). I'm too much of a newbie to fiddle with it, so could someone tell me what to do? I tried to do
from the root directory, but that failed too.
Here is the link to the log file if it helps: https://www.dropbox.com/s/hal4fp0p3rb2hrw/libgd-2.1.1.p0?dl=0
Thanks for your help.
PS: Sage-6.7 installed perfectly well on my linux desktop. I'm surprised that other people are not having this issue.
CC: @ppurka @kiwifb @kcrisman @vbraun @jdemeyer
Component: relocation
Reviewer: Jeroen Demeyer, Arvind Ayyer, Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/18816
The text was updated successfully, but these errors were encountered: