Re: gEDA-user: sot23 diode symbol
All, Thanks for the help on the sot23 diode. The symbol with just two pins numbered 1 and 3 went into the layout tool just fine. I really thought I needed to have a virtual pin 2 specified somehow but this seems to not be the case. I will also check out the symbols created by others to see how they have been built. I have run into sot23 numbering inconsistencies between manufacturers in the past and had to respin a board as a result so I'm picky when it comes to this package. Thanks again. Best Regards, Ed Schurig - Original Message - From: Dan McMahill [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Wednesday, August 06, 2008 3:37 PM Subject: Re: gEDA-user: sot23 diode symbol DJ Delorie wrote: gschem symbols do not have to have the same number of pins as the footprints you use. Feel free to put a diode in a DIP-40 footprint. The only key is that the pin *numbers* have to match. So, if you have a sot-23 footprint diode that uses pins 1 and 3, you can't use a gschem diode that uses pins 1 and 2. Be careful of anode/cathode matching too. Especially be careful about anode/cathode matching in an SOT-23. That particular package is notorious for having a whole bunch of minor mechanical and pinout (if a pinout difference can ever be considered minor) changes across vendors. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: sot23 diode symbol
I know through the years there has been a lot of discussion on this issue but I haven't been able to find the answer to my problem after searching the archives. I'm wondering how to refer to a 3 pin footprint with a two pin schematic symbol as is the case for a sot23 diode. My actual question is probably simple for the experts out there. I've already created a special symbol for a sot23 diode. The actual symbol graphic is a normal diode that has 2 pins, pin 1 and pin3. I believe I need to specify a pin 2 in the symbol textually somehow so that PCB layout software will match its 3 pin footprint to a schematically defined 3 pin device. How do I annotate the gschem symbol for a pin 2 without a graphical entity to assign the pin to. It's a no connect or unused pin so it needs no graphic but the symbol does need to have 3 pins when the netlist is generated for layout. Thanks Ed ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: bom2 gnetlist
I've seen some recent posts regarding the bom2 gnetlist report. I didn't see an answer to my question so I'm writing to beg for help. I've played with bom2 and the attribs file and it seems to work for me. One thing bom2 does is put all of the reference designators on one line which is what I want. Is there a way to get a quantity for each line in the bom? I've tried adding the word quantity to the attribs file but this has no effect. I thought maybe there was a special word or syntax for the attribs file that might make this work. I've been using the partslist3 option to generate my bom but it is nice to be able to use the attribs file to customize things. In the future, I would like to be able to modify the scripts to generate boms in different ways. If someone could point me to an example file and a resource to learn the language I think I could figure it out. Thanks. Best Regards, Ed Schurig ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: gschem allegro output
I've created schematics using gschem and plan to out source the board layout to an allegro shop. I've generated the allegro files using a statement similar to what the one below: gnetlist -g allegro -o allegro_netlist.out page1.sch page2.sch page3.sch I'm using the CD version of gEDA dated 02/21/2007. The PCB layout shop from which I have obtained a quote told me that the netlist I generated could be used but that it would be easier for them if I could generate the following allegro pst files: pstchip.dat, pstxnet.dat, and pstxprt.dat. They said this would save them the effort of having to generate device files. My question then is whether anyone else has run into this issue and if so are there any conversion scripts to generate these files. Thanks for any help you can give. Best regards, Ed ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Multiple symbol gschem components
I looked at the autonumber feature briefly but with a preconceived notion that it wouldn't do all of the pages of a flat schematic. From your comment it seems maybe this is wrong. If I select the whole hierarchy instead of current page will autonumber number reference designators across all pages of a flat schematic? Ed - Original Message - From: Levente [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 06, 2007 12:21 PM Subject: Re: gEDA-user: Multiple symbol gschem components Ed Angie S. [EMAIL PROTECTED] wrote: I used grenum to initially set the bulk my reference designators. This seemed to be the way to go since I had other components that were slotted and had U1 which used multiple symbols for which I manually set reference designator values prior to running grenum. As I understand, grenum would not overwrite the preassigned reference designators like refdes_renum. Oddly, grenum seemed to work fine with the exception that it assigned U1 to an additional component even though U1 had already been used for my multiple symbol component. Initially I thought this was the cause of the duplicate references above but manually changing the erroneous U1 assignment didn't fix the duplicate references problem. I wanted to point this issue out in case there might be an issue with grenum. Yes, it seems to be a grenum bug. Thanks for reporting it, I check it later on. However, you can use the renumber mechanism inside gschem i.e. Attributes-Autonumber text. Just run as it is at the first time, then clarify slotted issues, then make sure you have the Override existing numbers unchecked. I am the author of grenum, but I have to admit that I use the Autonumber feature instead of grenum. -- Levente http://web.interware.hu/lekovacs ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: geda install on Ubuntu
Peter, I installed the packages we talked about below. I also added libxaw7-dev and libbz2-dev which were two Stuart Brorson helped me identify as problems for ngspice and verilog on my previous machines gEDA installation a while back. After installing those packages, the gEDA installation completed successfully. I've at least brought up gschem and pcb as a test and they both started so that seems like a good sign. I'm looking forward to playing with spice and verilog one of these days. Thanks for your help. Best Regards, Ed - Original Message - From: Peter Clifton [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Monday, September 17, 2007 4:05 PM Subject: Re: gEDA-user: geda install on Ubuntu On Mon, 2007-09-17 at 14:38 -0500, Ed Angie S. wrote: Peter, Thanks for the quick response. 1. Is it ok to have both libgtk2.0-dev and libgtk1.2-dev installed? Should be fine. I don't have, but the libraries are versioned such that they won't clash. 2. You are correct, g++ is not installed but will be shortly. 3. I will install libgd2-xpm-dev I think libgd2-xpm-dev is what you want... I build PCB on my box without problems, so that is likely the libgd it is picking up. Peter ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: geda install on Ubuntu
Peter, Thanks for the quick response. 1. Is it ok to have both libgtk2.0-dev and libgtk1.2-dev installed? 2. You are correct, g++ is not installed but will be shortly. 3. I will install libgd2-xpm-dev Ed - Original Message - From: Peter Clifton [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Monday, September 17, 2007 2:14 PM Subject: Re: gEDA-user: geda install on Ubuntu On Mon, 2007-09-17 at 13:54 -0500, Ed Angie S. wrote: Peter, Thanks for the reply. My initial email was lacking that I am trying to install from the gEDA 20070221 CD. My new Ubuntu machine will be my second gEDA installation and I would like it to be the same version of gEDA as my original debian machine. I thought the installer installed the dependencies the first time through but I guess it didn't. I have subsequently installed the following packages using aptitude: It is always best to install the distributions version of these packages if possible. I'm not familiar with where the installer CD puts them, but it would have to be elsewhere than /usr/bin /usr/lib etc.. to avoid conflicts with ubuntu's package managed versions. guile1.6-dev libwxgtk2.8-dev tcl8.4 tcl8.4-dev tk8.4 tk8.4-dev libgtk2.0-dev libreadline5-dev flex bison gperf libjpeg62-dev I then re-ran the installer and geda/gaf seems to have installed ok. pcb, ngspice, gnucap, icarus, and gspiceui are not installed correctly yet. I would like to get them all working but pcb is my critical issue for an ongoing project. I have attached the install.log and pcb config.log files. The installer no longer asks if I want to install any software so I'm hoping I am far closer to working than I was previously. However, the Install.log file indicates that my machine is missing gtk-config. I've found some discussion on this issue but I'm still not sure what to do or if I need this with libgtk2.0-dev installed. gtk-config was from back in the gtk-1.x days. It might be that the installer is trying to install an old app which wants it - in which case, try: sudo apt-get install libgtk1.2-dev For pcb, the error indicates that my gd installation does not include support for jpeg. For other programs the message error trying to exec 'cc1plus': execvp: No such file or directory seems to be a problem. I suspect I'm missing some required packages but I'm not sure what to install to fix these problems. ok - next step for PCB, get hold of a copy of libgd which has jpeg support. I have libgd2-xpm-dev installed: sudo apt-get install libgd2-xpm-dev with the cc1plus error, it looks like you might not have a C++ compiler installed. Try: sudo apt-get install g++ Any help would be much appreciated. Thanks. Let us know how it goes. Ubuntu takes a little bit of apt-get install bootstrapping to become a usable development platform, however its pretty good once you've got the required packages. Regards, Peter C. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: schematic symbol text size for printing
I recently upgraded gEDA to the 02212007 CD release. I hadn't printed anything right after the upgrade but noticed today that the text size for schematic symbols when printed is much smaller than before the upgrade. The problem is very evident for symbols which use a line above part of the signal name text to indicate negated because the line is no longer located in the correct place relative to the text. All symbol text looks fine on the screen; the problem is only with printed schematics. The problem occurs if I print the symbol directly or if the symbol has been placed in a schematic page and then printed. The problem is evident for symbols created before and after the upgrade. Any advice would be much appreciated. Regards, Ed ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: schematic symbol text size for printing
Ben, Thanks for the response. I may have more than one issue because I haven't addressed the anchor point issue at all. However, when I compare schematics printed out before and after the upgrade the text size (not just position) is significantly smaller for the post upgrade schematic page. The post upgrade text size in the print out is quite hard to read. I'm printing on A size sheets and before the upgrade my schematics were quite readable. The individual characters are smaller so it's not simply a proportional verses non proportional font issue either. It's possible that the screen font was slightly larger than the print font for the old gEDA version also but the difference must have been so slight as to not be noticeable. Note that the gEDA version I was using previously was a year or two old. Ed - Original Message - From: Ben Jackson [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Monday, June 04, 2007 9:43 AM Subject: Re: gEDA-user: schematic symbol text size for printing On Mon, Jun 04, 2007 at 09:50:24AM -0600, Ed Angie S. wrote: the text size for schematic symbols when printed is much smaller than before the upgrade. The problem is very evident for symbols which use a line above part of the signal name text to indicate negated because the line is no longer located in the correct place relative to the text. All symbol text looks fine on the screen; the problem is only with printed schematics. When text looks different when printed it's usually because the anchor point for the text is not where you want. I seem to recall a mention of an automatic anchor point moving feature, which is possibly affecting you. Since gschem does not print using its internal vector font, if the anchor point for your text is not toward the symbol, the smaller printed font means that the gap between the edge of the text and the symbol will increase. In the case of a hand-drawn overbar, you'd have to make the anchor top/center (in the default rotation) in order to have the bar stay in approximately the right place. It will still be too big for the printed text. If the bar is supposed to go over only one word of the text it's probably impossible to ensure it prints correctly. (and the print font has always been smaller since I started using gschem!) -- Ben Jackson AD7GD [EMAIL PROTECTED] http://www.ben.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: schematic symbol text size for printing
Mike, Thanks for the info. I didn't know about the adjustment you mentioned; it seems to work as you describe. While playing with the adjustment I've learned a bit more about my situation. All of the symbols I had created with the old gEDA used a font size of 8. Symbols created with the new gEDA use a font size of 10. Thus, schematic pages I create with all new symbols in the new version of gEDA look great. Schematics created with the new gEDA using my older symbols are the problem. The system-gschemrc for my older gEDA version does not seem to have the same adjustment so maybe it was hard coded to something higher than the new gEDA system-gschemrc default value of 1.0. I only have a few symbols in my library so I will change them all to a size 10 font. I didn't really have a standard for creating the symbols because I always started by using a similar symbol from the gEDA library as a template. Thus, I never really set the text size for any of my symbols. I wonder if font size 8 was the size of choice for the older versions of gEDA. I probably should have been working with a newer version of gEDA anyway but I simply used the package that came with Debian Sarge. As always, thanks for the quick response from the gEDA user group. Best Regards, Ed - Original Message - From: Mike Jarabek [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Monday, June 04, 2007 11:00 AM Subject: Re: gEDA-user: schematic symbol text size for printing Hi, Besides the font anchor point, there's also a fudge-factor adjustment you can apply in the system-gschemrc. This sets a scaling factor between gschem's internal units and the font size. This is needed because not all fonts are created equal. If this does not do the trick for you, can you send me the postscipt output and the schematic/symbol that's causing you grief and I will look into it. Also, gschem supports overbars natively, and the PS code automatically makes them look nice. Just put a '_' where you want it to start and another '_' where you want it to end. -- Mike Jarabek FPGA/ASIC Designer, DSP Firmware Designer http://www.sentex.ca/~mjarabek -- -Original Message- From: Ed Angie S. [EMAIL PROTECTED] Date: Mon, 4 Jun 2007 11:17:42 To:gEDA user mailing list geda-user@moria.seul.org Subject: Re: gEDA-user: schematic symbol text size for printing Ben, Thanks for the response. I may have more than one issue because I haven't addressed the anchor point issue at all. However, when I compare schematics printed out before and after the upgrade the text size (not just position) is significantly smaller for the post upgrade schematic page. The post upgrade text size in the print out is quite hard to read. I'm printing on A size sheets and before the upgrade my schematics were quite readable. The individual characters are smaller so it's not simply a proportional verses non proportional font issue either. It's possible that the screen font was slightly larger than the print font for the old gEDA version also but the difference must have been so slight as to not be noticeable. Note that the gEDA version I was using previously was a year or two old. Ed - Original Message - From: Ben Jackson [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Monday, June 04, 2007 9:43 AM Subject: Re: gEDA-user: schematic symbol text size for printing On Mon, Jun 04, 2007 at 09:50:24AM -0600, Ed Angie S. wrote: the text size for schematic symbols when printed is much smaller than before the upgrade. The problem is very evident for symbols which use a line above part of the signal name text to indicate negated because the line is no longer located in the correct place relative to the text. All symbol text looks fine on the screen; the problem is only with printed schematics. When text looks different when printed it's usually because the anchor point for the text is not where you want. I seem to recall a mention of an automatic anchor point moving feature, which is possibly affecting you. Since gschem does not print using its internal vector font, if the anchor point for your text is not toward the symbol, the smaller printed font means that the gap between the edge of the text and the symbol will increase. In the case of a hand-drawn overbar, you'd have to make the anchor top/center (in the default rotation) in order to have the bar stay in approximately the right place. It will still be too big for the printed text. If the bar is supposed to go over only one word of the text it's probably impossible to ensure it prints correctly. (and the print font has always been smaller since I started using gschem!) -- Ben Jackson AD7GD [EMAIL
Re: gEDA-user: schematic symbol text size for printing
I just thought I would make one more comment. After experimenting with the postscript-font-scale setting in system-gschemrc, I found a setting of 1.5 to result in near WYSIWIG between display and printer on my system. This makes 8 or 10 point font symbol text very readable on an A size printout. Using \_xxx\_ to create overbars works great to eliminate the need for WYSIWIG for overbars but it is still nice to see on the screen what you will see in the printout. Regards, Ed Schurig - Original Message - From: Ed Angie S. [EMAIL PROTECTED] To: [EMAIL PROTECTED]; gEDA user mailing list geda-user@moria.seul.org Sent: Monday, June 04, 2007 1:17 PM Subject: Re: gEDA-user: schematic symbol text size for printing Mike, Thanks for the info. I didn't know about the adjustment you mentioned; it seems to work as you describe. While playing with the adjustment I've learned a bit more about my situation. All of the symbols I had created with the old gEDA used a font size of 8. Symbols created with the new gEDA use a font size of 10. Thus, schematic pages I create with all new symbols in the new version of gEDA look great. Schematics created with the new gEDA using my older symbols are the problem. The system-gschemrc for my older gEDA version does not seem to have the same adjustment so maybe it was hard coded to something higher than the new gEDA system-gschemrc default value of 1.0. I only have a few symbols in my library so I will change them all to a size 10 font. I didn't really have a standard for creating the symbols because I always started by using a similar symbol from the gEDA library as a template. Thus, I never really set the text size for any of my symbols. I wonder if font size 8 was the size of choice for the older versions of gEDA. I probably should have been working with a newer version of gEDA anyway but I simply used the package that came with Debian Sarge. As always, thanks for the quick response from the gEDA user group. Best Regards, Ed - Original Message - From: Mike Jarabek [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Monday, June 04, 2007 11:00 AM Subject: Re: gEDA-user: schematic symbol text size for printing Hi, Besides the font anchor point, there's also a fudge-factor adjustment you can apply in the system-gschemrc. This sets a scaling factor between gschem's internal units and the font size. This is needed because not all fonts are created equal. If this does not do the trick for you, can you send me the postscipt output and the schematic/symbol that's causing you grief and I will look into it. Also, gschem supports overbars natively, and the PS code automatically makes them look nice. Just put a '_' where you want it to start and another '_' where you want it to end. -- Mike Jarabek FPGA/ASIC Designer, DSP Firmware Designer http://www.sentex.ca/~mjarabek -- -Original Message- From: Ed Angie S. [EMAIL PROTECTED] Date: Mon, 4 Jun 2007 11:17:42 To:gEDA user mailing list geda-user@moria.seul.org Subject: Re: gEDA-user: schematic symbol text size for printing Ben, Thanks for the response. I may have more than one issue because I haven't addressed the anchor point issue at all. However, when I compare schematics printed out before and after the upgrade the text size (not just position) is significantly smaller for the post upgrade schematic page. The post upgrade text size in the print out is quite hard to read. I'm printing on A size sheets and before the upgrade my schematics were quite readable. The individual characters are smaller so it's not simply a proportional verses non proportional font issue either. It's possible that the screen font was slightly larger than the print font for the old gEDA version also but the difference must have been so slight as to not be noticeable. Note that the gEDA version I was using previously was a year or two old. Ed - Original Message - From: Ben Jackson [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Monday, June 04, 2007 9:43 AM Subject: Re: gEDA-user: schematic symbol text size for printing On Mon, Jun 04, 2007 at 09:50:24AM -0600, Ed Angie S. wrote: the text size for schematic symbols when printed is much smaller than before the upgrade. The problem is very evident for symbols which use a line above part of the signal name text to indicate negated because the line is no longer located in the correct place relative to the text. All symbol text looks fine on the screen; the problem is only with printed schematics. When text looks different when printed it's usually because the anchor point for the text is not where you want. I seem to recall a mention
Re: gEDA-user: Install Log
Stuart, Thanks for the quick response. I checked my system and libxaw7 is installed. There is a package called libxaw7-dev that is not installed; could this be the problem? I don't know whether Debian removed bzlib recently or not but I can get it installed I think. Once these dependency issues are solved, how should I go about reinstalling ngspice and icarus verilog? Can I simply rerun the installer and it will figure out which is already installed correctly? ngspice doesn't seem to have any files under bin. There are couple iverilog files under bin so it seems it was partially installed. Should I delete the verilog binaries? Ed - Original Message - From: Stuart Brorson [EMAIL PROTECTED] To: gEDA user mailing list geda-user@moria.seul.org Sent: Tuesday, May 08, 2007 9:01 AM Subject: Re: gEDA-user: Install Log Thanks for the report. Here are the two failures I found: Ngspice: --- /home/ed/gEDA/geda-sources/ngspice/ng-spice-rework-17 ./configure --prefix=/home/ed/gEDA/geda-install --enable-xspice --with-readline=yes [ snip! ] checking for main in -lXaw... no configure: error: Couldn't find Xaw library This one is very strange! AFAIK, the Xaw library is a base library used for X windows. Why is this missing from Debian? I don't know what to tell you.. Icarus Verilog: - [ snip! .] make install for dir in vvp vpi tgt-stub tgt-null tgt-vvp libveriuser cadpli; do (cd $dir ; make all); done make[1]: Entering directory `/home/ed/gEDA/geda-sources/icarus/verilog-20061210/vvp' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/ed/gEDA/geda-sources/icarus/verilog-20061210/vvp' make[1]: Entering directory `/home/ed/gEDA/geda-sources/icarus/verilog-20061210/vpi' gcc -DHAVE_CVS_IDENT=1 -I. -I./.. -I. -I.. -D_LARGEFILE_SOURCE=1 -D_FILE_OFFSET_BITS=64 -DHAVE_CONFIG_H -fPIC -Wall -g -O2 -MD -c sys_lxt.c -o sys_lxt.o In file included from sys_lxt.c:24: lxt_write.h:33:19: bzlib.h: No such file or directory sys_lxt.c: In function `install_dumpvars_callback': sys_lxt.c:296: warning: long unsigned int format, different type arg (arg 3) make[1]: *** [sys_lxt.o] Error 1 make[1]: Leaving directory `/home/ed/gEDA/geda-sources/icarus/verilog-20061210/vpi' You system is lacking the bzlib (a library used for compression). I suggest Googling around to see if you can find it and install it. I don't know if the error in sys_lxt is caused by the missing bzlib or somethign else. Maybe I need to put a dependency check into the installer for bzlib? I haven't seen this dependency missing before? Did Debian remove this lib? Or did Steve put a new dependency into Icarus? Stuart ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: installer question
I'm trying to install geda on a debian sarge linux system. Previously, I've installed the Sarge debian geda package successfully and have been using gschem and pcb. I would like to install the cd released in February but my limited linux experience is showing up quickly in the process. I receive the following error message when running installer --log --verbose: /usr/bin/env: bad interpreter: permission denied My debian system does not have a /user/bin/env directory which explains why the error is generated from the first line of the installer script. What should I do to correct the problem? Also, I noticed on the message board that libwxgtk2.6-dev needs to be installed. The debian Sarge CD has version 2.4. Do I need to get a later version for this new version of geda to work. Ed ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: installer question
Never mind the first part of my question, I found the debian install notes on the cd which solved the problem. I am still wondering about libwxgtk2.6-dev verses 2.4. Ed - Original Message - From: Ed Angie S. To: gEDA user mailing list Sent: Monday, May 07, 2007 11:18 AM Subject: gEDA-user: installer question I'm trying to install geda on a debian sarge linux system. Previously, I've installed the Sarge debian geda package successfully and have been using gschem and pcb. I would like to install the cd released in February but my limited linux experience is showing up quickly in the process. I receive the following error message when running installer --log --verbose: /usr/bin/env: bad interpreter: permission denied My debian system does not have a /user/bin/env directory which explains why the error is generated from the first line of the installer script. What should I do to correct the problem? Also, I noticed on the message board that libwxgtk2.6-dev needs to be installed. The debian Sarge CD has version 2.4. Do I need to get a later version for this new version of geda to work. Ed -- ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gEDA upgrade
Thanks, I will proceed with the installation. Ed - Original Message - From: al davis [EMAIL PROTECTED] To: geda-user@moria.seul.org Sent: Wednesday, May 02, 2007 12:00 PM Subject: Re: gEDA-user: gEDA upgrade On Wednesday 02 May 2007, Ed Angie S. wrote: Can I install the newer version into a single directory so as to not overwrite any of the previous version and then simply change my search path to prioritize the new version? The usual procedure for things like this is that stuff installed by the package manager goes in /usr (that is .. /usr/bin, /usr/share, and so on) and stuff installed separately without the package manager goes in /usr/local (that is .. /usr/local/bin, /usr/local/share, and so on). Most tarballs, install disks, and the like default to doing exactly this. Therefore, just install it. It will do what you want. Just make sure that /usr/local/bin appears in the $PATH before /usr/bin . ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
