Thread: [A-a-p-user] i must be the unluckiest aap user ever
Brought to you by:
vimboss
From: Geoff G. <ge...@ge...> - 2003-03-30 19:59:53
|
It seems like every time I try to build vim using aap, it doesn't work out so good for me. Looking over the list, I'm guessing this has something to do with the scoping, but whenever I try to run aap fetch, I get "Aap: Error in recipe "/home/geoff/src/aap-builds/main.aap" line 32: NameError: name 'CVS' is not defined". I think if line 32 were changed to read @if $CVS == "yes" and CVSPATH: that woudl account for the scoping rules? But I have no luck testing so far, because I d/l the recipe every time. --G. -- Geoff Gerrietts <geoff at gerrietts dot net> "Ordinarily he was insane, but he had lucid moments when he was merely stupid." --Heinrich Heine |
From: Geoff G. <ge...@ge...> - 2003-03-30 20:05:10
|
Ahhh, there we go. Line 32 in the vim bootstrap recipe needs to be changed to read: @if _no.CVS == "yes" and CVSPATH: Thanks, --G. -- Geoff Gerrietts <geoff @ gerrietts.net> "Many a man's reputation would not know his character if they met on http://www.gerrietts.net/ the street." --Elbert Hubbard |
From: Geoff G. <ge...@ge...> - 2003-03-30 20:48:03
|
New problem while building vim: error: Error in recipe "/home/geoff/src/aap-builds/vim/src/main.aap" line 87: NameError: name 'BDIR' is not defined Looks like vim/src/main.aap wants a build directory variable called BDIR. To my eyes, this isn't a scoping problem, it's an inappropriate name, but I can't tell what was intended in this case. Anyone? Thanks, --G. -- Geoff Gerrietts "information 'wants' to be free in the same way nature <ge...@ge...> 'abhors' a vacuum: it's not some moral view, it's http://www.gerrietts.net/ just the natural state of affairs." -- jwz |
From: Bram M. <Br...@mo...> - 2003-03-30 21:19:59
|
Geoff Gerrietts wrote: > New problem while building vim: > > error: Error in recipe "/home/geoff/src/aap-builds/vim/src/main.aap" > line 87: NameError: name 'BDIR' is not defined > > Looks like vim/src/main.aap wants a build directory variable called > BDIR. To my eyes, this isn't a scoping problem, it's an inappropriate > name, but I can't tell what was intended in this case. This is a scope problem as well. Using "BDIR" in a Python command only finds it in the current scope. "_no.BDIR" should be used instead. That also applies to the Python code generated by Aap internally. I need to fix that. It should work when you do: cd vim/src aap -- hundred-and-one symptoms of being an internet addict: 267. You get an extra phone line so you can get phone calls. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html /// |
From: Geoff G. <ge...@ge...> - 2003-03-30 21:57:33
|
Quoting Bram Moolenaar (Br...@mo...): > > It should work when you do: > > cd vim/src > aap > Not a complaint -- I'm happy to give you your few days, I was just looking to build NetBeans support in, and thought I'd try AAP again -- but this didn't work either, and I thought you should know that it didn't. New error: Aap: Error in recipe "/home/geoff/src/aap-builds/vim/src/main.aap" line 583: Unknown variable: "exe.rm" I assume this is also scope stuff, but I haven't so much as tried to look. I'm going to give it a few days and try again -- my in-laws are in town right now so it's pretty awkward for me to be working at my workstation anyway. :) Thanks for taking the time to help me. I'll keep an eye out for when you think the scope stuff is under control again. --G. -- Geoff Gerrietts "People talk fundamentals and superlatives <geoff at gerrietts net> and then make some changes of detail." http://www.gerrietts.net --Oliver Wendell Holmes Jr |
From: Bram M. <Br...@mo...> - 2003-03-30 22:45:43
|
Geoff Gerrietts wrote: > Quoting Bram Moolenaar (Br...@mo...): > > It should work when you do: > > > > cd vim/src > > aap > > Not a complaint -- I'm happy to give you your few days, I was just > looking to build NetBeans support in, and thought I'd try AAP again -- > but this didn't work either, and I thought you should know that it > didn't. Yes, I certainly like to hear about something that isn't working. Adding scopes was quite a big changes, existing recipes need to be tested. > New error: > > Aap: Error in recipe "/home/geoff/src/aap-builds/vim/src/main.aap" > line 583: Unknown variable: "exe.rm" > > I assume this is also scope stuff, but I haven't so much as tried to > look. I'm going to give it a few days and try again -- my in-laws are > in town right now so it's pretty awkward for me to be working at my > workstation anyway. :) This one is quite easy: change "$exe.rm" to "$(exe).rm". The dot is now a valid character in a variable name. > Thanks for taking the time to help me. I'll keep an eye out for when > you think the scope stuff is under control again. It should be working tomorrow. -- hundred-and-one symptoms of being an internet addict: 268. You get up in the morning and go online before getting your coffee. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html /// |
From: Bram M. <Br...@mo...> - 2003-03-31 10:38:44
|
Geoff Gerrietts wrote: > Not a complaint -- I'm happy to give you your few days, I was just > looking to build NetBeans support in, and thought I'd try AAP again -- > but this didn't work either, and I thought you should know that it > didn't. I have fixed all the problems you reported and tested it works OK for me. When you now get the latest version of Aap from CVS you should be able to build Vim without problems. Let me know if you run into a problem anyway. -- This sentence is not sure that it exists, but if it does, it will certainly consider the possibility that other sentences exist. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html /// |
From: Bram M. <Br...@mo...> - 2003-03-30 21:06:54
|
Geoff Gerrietts wrote: > It seems like every time I try to build vim using aap, it doesn't work > out so good for me. > > Looking over the list, I'm guessing this has something to do with the > scoping, but whenever I try to run aap fetch, I get "Aap: Error in > recipe "/home/geoff/src/aap-builds/main.aap" line 32: NameError: name > 'CVS' is not defined". > > I think if line 32 were changed to read > @if $CVS == "yes" and CVSPATH: > that woudl account for the scoping rules? But I have no luck testing > so far, because I d/l the recipe every time. This problem is indeed caused by the change to introduce scopes. You need to change the line to: @if _no.CVS == "yes" and CVSPATH: There is a similar problem in the vim/src/main.aap recipe. I'll fix that as well. But this also requires a change to Aap, please wait a day until I have fixed this. I think it does work if you execute the recipe "vim/src/main.aap" directly. Sorry about this. We didn't manage to make the scopes search work in Python, since the "exec" command only accepts a real dictionary, not the simulated one that we provide. -- Two fish in a tank. One says to the other: "Do you know how to drive this thing?" /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html /// |
From: Geoff G. <ge...@ge...> - 2003-03-30 22:02:08
|
Quoting Bram Moolenaar (Br...@mo...): > > Sorry about this. We didn't manage to make the scopes search work in > Python, since the "exec" command only accepts a real dictionary, not the > simulated one that we provide. No problem at all. I keep trying because I want to help find problems; I understand that "experimental" means "this might not work". Have you considered wrapping exec with a custom function that produces a "real" dictionary out of your "simulated" one? There are some hacky ways to do that (eg, __builtins__.exec = my_exec), and some not-so-hacky ways (eg, :%s/exec/my_exec/g). But I suspect I'm probably making this too simple.... --G. -- Geoff Gerrietts <geoff at gerrietts dot net> http://www.gerrietts.net/ "If I were two-faced, would I be wearing this one?" --Abraham Lincoln |
From: Bram M. <Br...@mo...> - 2003-03-30 22:45:42
|
Geoff Gerrietts wrote: > Have you considered wrapping exec with a custom function that produces > a "real" dictionary out of your "simulated" one? There are some hacky > ways to do that (eg, __builtins__.exec = my_exec), and some > not-so-hacky ways (eg, :%s/exec/my_exec/g). But I suspect I'm probably > making this too simple.... We do need our special kind of dictionary to make accessing a variable like "CFLAGS" search in several scopes. Re-implementing the "exec" command is probably too complicated. That goes into the core of python. -- hundred-and-one symptoms of being an internet addict: 269. You receive an e-mail from the wife of a deceased president, offering to send you twenty million dollar, and you are not even surprised. /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\ \\\ Project leader for A-A-P -- http://www.A-A-P.org /// \\\ Help AIDS victims, buy at Amazon -- http://ICCF.nl/click1.html /// |