From tim at opencircuitdesign.com Thu Jan 6 16:15:27 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:49 2008 Subject: [Magic-dev] Re: Magic & wide metal rule Message-ID: <200501062115.j06LFROe023538@opencircuitdesign.com> Dear Emerson, Sorry, it appears that mail on the magic mailing list was hung up for some time since October and has only just been fixed. So I'm about a month late answering your question. > I would like to know if there are any plans to implement "wide metal > check rules" in future MAGIC updates. If this vital check rule already > exist, how does one go about getting this file? Yes, I implemented such a rule in magic-7.1, 7.2, and 7.3. It is not a file, but an extension to the technology file syntax. Unfortunately, due to the ambiguity of the wide metal rule, and the difficulty of implementation, it is not possible for magic to catch all wide metal rule errors. At present, I would guess that it finds about 80% of the errors that would be flagged by DRACULA. To implement the rule, it is only necessary to add the wide metal rule to any technology file. For example: widespacing *m1 112 *m1 7 touching_ok \ "Wide metal1 (> 10um) spacing < 7 (M1.S.2)" Indicates that m1 (using my implementation of "*m1" to refer to m1 plus all contacts to m1) of wider than 112 units must be 7 units away from other m1 (this is a 0.18 process with lambda=0.09, so 112 lambda is approximately 10um). Hopefully I can find a way to up the rate of error-catching from 80% to 100%, but this is still better than 0%. Regards, Tim From tim at opencircuitdesign.com Thu Jan 6 16:36:43 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:49 2008 Subject: [Magic-dev] Re: IRSIM on Mac OS-X Message-ID: <200501062136.j06LahDH023774@opencircuitdesign.com> Dear Kevin, > ld: warning suggest use of -bind_at_load, as lazy binding may result in > errors or different symbols being used If I take this message at face value, then "configure.in" should be changed from (line 997): LDDL_FLAGS="-dynamiclib -flat_namespace -undefined suppress -noprebind" to LDDL_FLAGS="-dynamiclib -flat_namespace -undefined suppress \ -noprebind -bind_at_load" This option may be mutually exclusive with "-noprebind" (I thought they were the same, but apparently not). Problems sometimes occur depending on what linker (GNU or Mac) is being used by gcc. Do "autoconf" and run "configure" again (alternately, the change can be made to "configure" instead of "configure.in" and you can avoid the autoconf step). The "configure" script is nearly identical to that used for magic, and has been known to work on at least some configurations of OS-X. Check the mailing list archive for discussions of compiling magic under OS-X, because these discussions will be relevant to irsim-9.7.1. Regards, Tim From tim at opencircuitdesign.com Thu Jan 6 16:44:39 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:49 2008 Subject: [Magic-dev] Re: Dual-VT technology in magic Message-ID: <200501062144.j06LidNo023872@opencircuitdesign.com> Dear Wei, > This question may not be asked here, but I just don't know where to ask. > > I'm looking for the technology file for both high-Vt and low-Vt for > 0.18/0.13 technology. I think I can't just changed the Vth value, right? Unfortunately, the standard set of 0.18 tech files (SCN6M_DEEP.09.tech27, and variants) do not have any high-voltage devices. Normally these would appear in the techfile as layers with "hv" prepended (hvntransistor, hvndiffusion, etc.). They appear in a number of the larger-feature-size technology files. It is possible to get a technology file for TSMC 0.18 with high-voltage devices (and intrinsic devices) because I am working on one right now. However, I have to finish it up, document it, and pass it on to Wes Hansford at MOSIS so it can be made available for download from their secure document server. The slowest part of this process so far has been me getting around to writing the documentation. I have not seen any 0.13 technology files for magic at this point. At one time I was prepared to create one for the Chartered Semiconductor process, but we have sort of passed that opportunity by and will probably go to TSMC 90nm when it comes time to design and test something smaller than 0.18. Regards, Tim From vamsi.krishnak at gmail.com Fri Jan 7 09:53:47 2005 From: vamsi.krishnak at gmail.com (vamsi krishna) Date: Thu Oct 30 14:32:49 2008 Subject: [Magic-dev] Benchmark physical designs Message-ID: <3faf056805010620236303697b@mail.gmail.com> Hello all, I have modified magic's source code to change the existing inmemory corner stitch datastructure to an external memory datastructure which can handle more rectangles than the inmemory corner stitch. But I need help in testing this on some large physical desgins, can some one please help me in finding some big physical desgins so that I can test my implementation. Looking forward to hear from you. With Regards Vamsi Kundeti From adl35 at cornell.edu Fri Jan 7 03:34:15 2005 From: adl35 at cornell.edu (Andrew Luciere) Date: Thu Oct 30 14:32:49 2008 Subject: [Magic-dev] installing magic on Fedora Core 3 Message-ID: <1105086855.28382.3.camel@localhost.localdomain> Hello, Is magic compatible with Fedora Core 3? im trying to install it and i get through the config ok but when i run gmake install i get the following [adl35@localhost magic-7.1]$ gmake install --- installing to /home/adl35/cad ext2sim.c:17:9: warning: extra tokens at end of #endif directive In file included from ext2sim.c:22: /usr/lib/gcc/i386-redhat-linux/3.4.2/include/varargs.h:4:2: #error "GCC no lo nger implements ." ................................ .................................. ............................... ../extflat/extflat.h:24:8: warning: extra tokens at end of #endif directive extcheck.c:93:8: warning: extra tokens at end of #endif directive gmake[2]: *** [extcheck.o] Error 1 gmake[2]: *** No rule to make target `../tech/libtech.o', needed by `libmpack .a'. Stop. [adl35@localhost magic-7.1]$ Thanks -- Andrew Luciere From tim.edwards at multigig.com Fri Jan 7 13:50:25 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Magic w/external memory data structure Message-ID: <200501071850.j07IoP7m003667@khachaturian.tim.linglan.net> Dear Vamsi, > I have modified magic's source code to change the existing inmemory > corner stitch datastructure to an external memory datastructure which > can handle more rectangles than the inmemory corner stitch. > But I need help in testing this on some large physical desgins, can > some one please help me in finding some big physical desgins so that > I can test my implementation. This sounds like an interesting project. I have some huge files that are around 1-2GB of rectangle data. However, they are the property of LSI Logic. But, I can run tests for you and help you with the development. Let me know if you're interested. Technically, it should not be very difficult to generate a huge random routing job or even a random layout, such as auto-generating fill patterns over a large area, which should be able to aid in debugging the method. Regards, Tim From tim at opencircuitdesign.com Fri Jan 7 13:55:04 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] installing magic on Fedora Core 3 In-Reply-To: <1105086855.28382.3.camel@localhost.localdomain> References: <1105086855.28382.3.camel@localhost.localdomain> Message-ID: <41DEDB08.4070407@opencircuitdesign.com> Dear Andrew, > Is magic compatible with Fedora Core 3? Magic versions 7.2 and 7.3 are compatible with Fedora Core 3, which is what I have on my laptop. The "varargs" thing became incompatible with the introduction of gcc version 3. One way to get around it is to get gcc version 2.95 from gnu.org; otherwise, you'll find that many packages break when compiled from source with gcc-3. I'm about to move magic version 7.3 from "alpha" to "beta", just haven't gotten around to it yet, in case you're worried about the reliability of the newer versions. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 3600 Glen Canyon Road | phone: (831) 440-0600 ext. 20 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From mark.chang at gmail.com Wed Jan 12 17:15:35 2005 From: mark.chang at gmail.com (Mark Chang) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Magic 7.2 hangs on exit (ubuntu linux) Message-ID: <26ccc9e5050112141570f4072@mail.gmail.com> Just coming back to the magic fold to teach some students without using commercial tools. Installed Magic 7.2 smoothly on my ubuntulinux machine (kernel 2.6, gcc 3.3.4). Magic seems to work as I remember it, however, upon :quit, it just hangs. A 'kill' quits magic, however the command line that remains needs a 'reset' to get back to 'normal'. Any suggestions? Upgrade to 7.3? I'm using the latest magic-7.2 as of today. Thanks (Tim!) Mark -- Mark L. Chang From tim at opencircuitdesign.com Thu Jan 13 18:15:57 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Magic 7.2 hangs on exit (ubuntu linux) In-Reply-To: <26ccc9e5050112141570f4072@mail.gmail.com> References: <26ccc9e5050112141570f4072@mail.gmail.com> Message-ID: <41E7012D.6050100@opencircuitdesign.com> Dear Mark, > Magic seems to work as I remember it, however, upon :quit, it just > hangs. A 'kill' quits magic, however the command line that remains > needs a 'reset' to get back to 'normal'. > > Any suggestions? Upgrade to 7.3? I'm using the latest magic-7.2 as > of today. Version 7.3 only differs from 7.2 in technical ways, such as the database representation of stacked contacts. Upgrading is not going to help in this case. I have kernel 2.6 and gcc-3.4.2 on my machine and have no such problems. It is likely a window manager thing. I have run it under Gnome on the Opteron machine in my basement, but it is usually just to prove that the compile was successful, not to do any real work. I should first ask how magic is compiled: Are you running under the Tcl/Tk interpreter, are you running with the "tkcon" console or the terminal, and are you running the GUI-wrapped version (magic -w)? Any of these might have an effect on the behavior upon exit. Tracking it down probably requires running the debugger, e.g., do ps -C wish to get the process ID (or "ps -C magicexec" if not compiled w/Tcl), then do gdb program with the returned value for the process ID. When it hangs on exit, do a control-C in the terminal to get back to gdb, and figure out where it thinks it is. Unfortunately, 1) gdb may prevent the problem from showing up, 2) the program may actually have already exited, and the terminal is somehow getting hung up because it was reset to the wrong values, and 3) the terminal may be so hosed that you can't do control-C to get back to the debugger. Still, it's worth a try. Please tell me what the name of the terminal program is. I use xterm, but I think there are a number of variants out there, and they may behave differently when their settings are forcibly whacked, which is what magic does just before exiting (see TxSetTerminal() and TxResetTerminal() in textio/txInput.c). Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 3600 Glen Canyon Road | phone: (831) 440-0600 ext. 20 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From mark.chang at gmail.com Mon Jan 24 19:45:37 2005 From: mark.chang at gmail.com (Mark Chang) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Magic 7.2 hangs on exit (ubuntu linux) In-Reply-To: <41E7012D.6050100@opencircuitdesign.com> References: <26ccc9e5050112141570f4072@mail.gmail.com> <41E7012D.6050100@opencircuitdesign.com> Message-ID: <26ccc9e50501241645a615f0@mail.gmail.com> Tim et. al. - Thanks for the suggestions. I got the 7.2 branch to compile cleanly and work great with Ubuntu and TCL after a little monkeying around. It seems that Ubuntu Warty release doesn't put the tclConfig.sh in the path. Instead, this configure line is needed: ./configure --with-tcl=/usr/lib/tcl8.4 --with-tk=/usr/lib/tk8.4 I didn't try further without TCL, so I don't know what that bug is. I can easily compile it without tcl and try it, if you'd like me to do some debuggin. mark On Thu, 13 Jan 2005 18:15:57 -0500, R. Timothy Edwards wrote: > Dear Mark, > > > Magic seems to work as I remember it, however, upon :quit, it just > > hangs. A 'kill' quits magic, however the command line that remains > > needs a 'reset' to get back to 'normal'. > > > > Any suggestions? Upgrade to 7.3? I'm using the latest magic-7.2 as > > of today. -- Mark L. Chang From sexygirl56 at hotmail.com Fri Feb 4 01:59:35 2005 From: sexygirl56 at hotmail.com (La supreme Poofias) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Method of storing layer information in MAGIC files Message-ID: Hi, I'm running in to a problem regarding the way layers are stored in .MAG files. The basic problem is that certain layers drawn over other layers cause the underlying layer information to be deleted. For example, if I were to draw an n-diffusion to metal1 contact, the underlying information about the ndiff is deleted. That is to say, if I were to erase the contact, the ndiff which was underneath the contact is gone, as well. I thought I was making a mistake with erasing vs. deletion, but I looked at the actual MAG files, and the ndiff information was gone. To me, this seems like an inherent flaw in the file format, and it's contrary with the concept of "layers." If I place a contact above a diffusion, it doesn't mean that the diffusion is gone, even though I can't see it anymore from the 2D overhead view. If I delete a top layer, I expect the bottom layers to remain intact. I'm sure that there are quick hacks around this situation, such as using the stretch and move tools, but I run in to a lot of problems with those, as well (eg: one layer moves on top of another layer, and then the bottom layer information seems to disappear). However, is there a way to force MAGIC to retain true layer information? Regards, -K.S. From pai at softjin.com Sat Feb 5 00:15:44 2005 From: pai at softjin.com (Ravi R Pai) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] request for sample GDSII files Message-ID: <4203C2D8.7080605@softjin.com> Hi, I am working at SoftJin. We have recently released source code libraries of GDSII and OASIS to be freely available. It can be downloaded from http://www.softjin.com/html/anuvad.htm At present, we are looking for some large GDSII files for testing out our tools based on GDSII. If such files are available with you or if you can suggest some other sites where GDSII files are available, please let me know. It will be of great help. Regards, Ravi Pai SoftJin Infotech -------------- next part -------------- ----------------------------------------- (softjin.com) This message and any attachment contained is scanned by InterScan VirusWall in SoftJin and No virus found. --------------------------------------------------------- From philippe at alpha.ece.jhu.edu Fri Feb 4 09:50:25 2005 From: philippe at alpha.ece.jhu.edu (Philippe Pouliquen) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Method of storing layer information in MAGIC files In-Reply-To: References: Message-ID: <20050204094007.Q694@alpha.ece.jhu.edu> Hi K.S. On Fri, 4 Feb 2005, La supreme Poofias wrote: > I'm running in to a problem regarding the way layers are stored in .MAG > files. The basic problem is that certain layers drawn over other layers > cause the underlying layer information to be deleted. The short answer to your question is that you need to rewrite the technology file to your liking. In your example of drawing ndc over ndiff, if you visualize ndc as being the combination of m1, ndiff, and a contact, then you will see that the ndiff is not really gone. The reason that the drawn ndiff rectangle is converted to ndc is to speed up design rule checking. Speeding up DRC is key to allowing Magic to check for design rule violations on the fly. You can certainly create a Magic technology files that doesn't do this. However, you will lose a lot of the design rule checking abilities of Magic. If you really want just the fabrication layers, perhaps you should look at the CIF output instead. Philippe Pouliquen The Johns Hopkins University From rajit at csl.cornell.edu Fri Feb 4 09:34:26 2005 From: rajit at csl.cornell.edu (Rajit Manohar) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Method of storing layer information in MAGIC files In-Reply-To: References: Message-ID: Hello, Magic treats a contact differently from other programs. Suppose I wanted to draw an n-diffusion to metal1 contact (ndc). If you paint one, magic draws metal1, n-diffusion, as well as the appropriate via. If you draw a large contact, the vias are converted into an array of small vias. So when a contact is selected, everything magic drew for you is selected; this is why when a contact is erased, you see the effect you were pointing out. If you didn't, then painting an isolated contact (not near anything) and deleting it would leave residual paint. In other drawing editors such as ledit, to draw an ndc you would have to draw metal1, n-diffusion, as well as the vias in the correct configuration---which might take longer, depending on what you are trying to do. You can also delete the via without deleting any of the surrounding material. From what you said, it appears that you do not want to delete the contact; rather, you'd like to delete the via. I know some (all?) technology files support both methods of connections between layers, and so if you draw the vias yourself you can delete them as well. Regards, -Rajit From s.robert at usherbrooke.ca Fri Feb 4 09:37:38 2005 From: s.robert at usherbrooke.ca (Stefan Robert) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Method of storing layer information in MAGIC files In-Reply-To: References: Message-ID: <8848da1bd77de97a6c9f84ade6954e15@usherbrooke.ca> Ah, this behaviour is normal and is a feature of the magic tech file. You need to understand the concept behind the "compose" section of the tech file (which defines wich layers are either added or deleted when one is created on top of the other one) and the "cifoutput" section where it defines which layer are exported in gds format when you use the "calma" function. Why was this behaviour chosen over retaining all layer information in the MAG file? Well I cannot answer this in full, but I can easily imagine that this can save a lot of disk space and speed-up the responsiveness of magic because, when you have a properly defined "compose" and cifoutput section, you do not need "real layer" information in the layout view. It is just a matter of understanding how magic works comparatively to Cadence for example. Do notexpect Magic to behave like Cadence Virtuoso Layout (or other commercial layout tool), Magic has a different philosophy that has its drawbacks and advantages... and not having "real layer" information is not really "drawback" in Magic because actually "real layer" information is accessible. St?fan Le 05-02-03, ? 20:59, La supreme Poofias a ?crit : > Hi, > > I'm running in to a problem regarding the way layers are stored in > .MAG files. The basic problem is that certain layers drawn over other > layers cause the underlying layer information to be deleted. > > For example, if I were to draw an n-diffusion to metal1 contact, the > underlying information about the ndiff is deleted. That is to say, if > I were to erase the contact, the ndiff which was underneath the > contact is gone, as well. I thought I was making a mistake with > erasing vs. deletion, but I looked at the actual MAG files, and the > ndiff information was gone. > > To me, this seems like an inherent flaw in the file format, and it's > contrary with the concept of "layers." If I place a contact above a > diffusion, it doesn't mean that the diffusion is gone, even though I > can't see it anymore from the 2D overhead view. If I delete a top > layer, I expect the bottom layers to remain intact. > > I'm sure that there are quick hacks around this situation, such as > using the stretch and move tools, but I run in to a lot of problems > with those, as well (eg: one layer moves on top of another layer, and > then the bottom layer information seems to disappear). However, is > there a way to force MAGIC to retain true layer information? > > Regards, > > -K.S. > > > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev > From tim at opencircuitdesign.com Fri Feb 4 11:37:43 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Method of storing layer information in MAGIC files In-Reply-To: References: Message-ID: <4203A4D7.7050509@opencircuitdesign.com> Dear K.S., > For example, if I were to draw an n-diffusion to metal1 contact, the > underlying information about the ndiff is deleted. That is to say, if > I were to erase the contact, the ndiff which was underneath the contact > is gone, as well. I thought I was making a mistake with erasing vs. > deletion, but I looked at the actual MAG files, and the ndiff information > was gone. This is an inherent error in the way the paint/erase tables are constructed in magic-7.2 and earlier. I fixed this in magic-7.3 such that if you do "erase m1" on top of the ndiffusion contact, the contact will be erased but the ndiffusion will remain. I've found the additional annoyance that if you say "see no *; see ndiff", you get blank spaces where all the contacts are. Usually, the intent of "see ndiff" is to see all areas containing diffusion, including areas under contacts. I will have to address this problem sometime soon. The "usual hack" in versions 7.2 and earlier is to define vias on separate planes. This method has a number of drawbacks as well as the advantages, but does retain the concept of "layers" where there are contact cuts. None of the standard "scmos" tech files uses this method. There's nothing wrong with the layer concept in the database; it's mostly an issue of how the data are presented to and manipulated by the end-user. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 3600 Glen Canyon Road | phone: (831) 440-0600 ext. 20 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From nestorj at lafayette.edu Tue Feb 8 17:17:54 2005 From: nestorj at lafayette.edu (John Nestor) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] SCNA.80 and Magic 7.2: Segmentation Fault Message-ID: Hello, I just tried installing Jeff Sondeen's SCNA.80 technology file under Magic 7.2 (on RedHat Linux 7.2). When I fire it up (magic -T SCNA.80) I get the message that it is using this file, and then Magic has a segmentation fault. Any suggestions or workarounds? Thanks, John Nestor From tim at opencircuitdesign.com Wed Feb 9 13:09:46 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Re: Magic & SCNA.80 Message-ID: <200502091809.j19I9k31010429@opencircuitdesign.com> Dear John, > I just tried installing Jeff Sondeen's SCNA.80 technology file under > Magic 7.2 (on RedHat Linux 7.2). When I fire it up (magic -T SCNA.80) > I get the message that it is using this file, and then Magic has a > segmentation fault. You might try magic-7.3; we (MultiGiG) just taped out an AMI 1.5 chip using 7.3 and SCNA.80 without any troubles (although we'll see what happens with my hack to SCNA.80 to get n-diff-in-n-well varactors. Otherwise, I'll need to see a stack trace from running magic under a debugger. Instructions are on my website, and vary depending on how magic was compiled (e.g., with or without Tcl). It is probably a good idea to do the debug session, as I don't like having a distribution version that segfaults on a standard- issue technology file. But the error may be system-dependent. Regards, Tim From sondeen at ISI.EDU Wed Feb 9 11:32:49 2005 From: sondeen at ISI.EDU (Jeff Sondeen) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] SCNA.80 and Magic 7.2: Segmentation Fault In-Reply-To: References: Message-ID: <16906.25953.568431.104935@vapor.isi.edu> well i compiled magic version 7.3.65 on solaris 5.8 and it works ok with that techfile. assuming the magic you compiled works with the distributions's default techfiles, maybe you can edit the techfile to find what limits are being reached (in older magics, several of the SCN* techfiles define too many planes/types for use without first expanding the limits and recompiling magic, discussed i think the the README and/or CHANGELOG file). /jeff John Nestor writes: > Hello, > > I just tried installing Jeff Sondeen's SCNA.80 technology file under Magic > 7.2 (on RedHat Linux 7.2). When I fire it up (magic -T SCNA.80) I get the > message that it is using this file, and then Magic has a segmentation fault. > > Any suggestions or workarounds? > > Thanks, > > John Nestor > > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev From mark.chang at gmail.com Thu Feb 10 15:03:38 2005 From: mark.chang at gmail.com (Mark Chang) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] PNM output in 7.2.70 Message-ID: <26ccc9e50502101203695f42eb@mail.gmail.com> Executing :plot pnm foo.pnm 0.3 or, for just an inverter blown up to size :plot pnm foo.pnm 50 gives me PNM module given negative scale; cannot plot Works in the latest 7.3, but I haven't been ready to upgrade to the "alpha" stuff. Any thoughts? -- Mark L. Chang From tim.edwards at multigig.com Fri Feb 11 12:04:34 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Re: plot PNM in magic-7.2 Message-ID: <200502111704.j1BH4Y2O003867@khachaturian.tim.linglan.net> Dear Mark, > Executing > :plot pnm foo.pnm 0.3 > > or, for just an inverter blown up to size > :plot pnm foo.pnm 50 > > gives me > PNM module given negative scale; cannot plot "plot PNM" was originally designed for scaling down huge layouts to a manageable plot size, and was not capable of exceeding 1 pixel per magic unit. I sort of hacked in the capability in 7.2, but I didn't really get it working right until 7.3. The above problem, however, has a very simple fix, although I failed to transfer the fix back to magic-7.2 (which I will now do). It should be fixed by adding #include "utils/utils.h" to plot/plotCmd.c; the header gives the return type for MagAtof() as type double; otherwise, the compiler assumes type float, and a wrong value gets passed to PlotPNM(). > Works in the latest 7.3, but I haven't been ready to upgrade > to the "alpha" stuff. Version 7.3 is now considerably more trustworthy than 7.2, in my opinion. I have taped out four chips with version 7.3. One of these, a 5mm x 5mm rotary clock test chip, used virtually every novel feature I've thrown into 7.3---grid subdivision, non-Manhattan geometry, stacked contacts, Tcl-script-generated subcells, etc., etc. The last one of these was a more standard AMI 1.5um process chip using the SCNA80 techfile (albeit I hacked the techfile in an attempt to get varactor devices). I intend to redesignate 7.3 as "beta", not "alpha", but have not yet done so. Regards, Tim From tim at opencircuitdesign.com Fri Feb 11 13:15:23 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] SCNA.80 and Magic 7.2: Segmentation Fault In-Reply-To: References: Message-ID: <420CF63B.1090206@opencircuitdesign.com> Dear John, > I also tried downloading and compiling magic 7.3, but compilation quit in > the graphics module with an error: > grOGL1.c:37: variable-sized type declared outside of any function. > > Any suggestions how to fix this? Magic-7.3 will compile without the Tcl option if you change line 37 of graphics/grOGL1.c to: GLubyte **grOGLStipples; > I just tried installing Jeff Sondeen's SCNA.80 technology file under Magic > 7.2 (on RedHat Linux 7.2). When I fire it up (magic -T SCNA.80) I get the > message that it is using this file, and then Magic has a segmentation fault. I looked at your debug session from 7.2 and the SCNA80 file, but, unfortunately, it's one of those things where the error shows up deep in the memory allocation. These errors are notoriously difficult to trace. The only hint is: > #8 0x080f2cb2 in mzBuildPlanes () at mzInit.c:317 > #9 0x080f29c9 in MZInit () at mzInit.c:128 > #10 0x0809a213 in mainInitAfterArgs () at main.c:650 so the error occurred when the "mzrouter" section was encountered in the tech file. I would guess that the source of the error happened while processing the "cifinput" section. But I can't find anything obvious there. I ran magic-7.2 on the SCNA.80 tech file and it just came up and ran. However, this was compiled under Fedora Core 3 with gcc-3.3, so that introduces a number of differences in the compiled code. I was using "version 2002a" of SCNA.80.tech27. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 3600 Glen Canyon Road | phone: (831) 440-0600 ext. 20 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From mark.chang at gmail.com Fri Feb 11 14:15:08 2005 From: mark.chang at gmail.com (Mark Chang) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Re: plot PNM in magic-7.2 In-Reply-To: <200502111704.j1BH4Y2O003867@khachaturian.tim.linglan.net> References: <200502111704.j1BH4Y2O003867@khachaturian.tim.linglan.net> Message-ID: <26ccc9e5050211111561f23dc1@mail.gmail.com> Thanks for the feedback, Tim. I will try and transition to 7.3 and see how it goes down. Mark -- Mark L. Chang From mark.chang at gmail.com Fri Feb 11 18:00:47 2005 From: mark.chang at gmail.com (Mark Chang) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Bug in cif write 7.3 Message-ID: <26ccc9e505021115004e21b0e2@mail.gmail.com> Built latest 7.3, ubuntu, with tcl. Opening magic on a .mag file not in the current directory with a command like: magic -w magic/inv yields an error on a plain :cif write Cannot open /inv.cif to write CIF Not a big deal with :cif write filename.cif. Just $0.02. -- Mark L. Chang From parimi_pavan at yahoo.com Sun Feb 13 01:36:49 2005 From: parimi_pavan at yahoo.com (pavan) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] How to get .LEF and .DEF files Message-ID: <20050213093649.68038.qmail@web50904.mail.yahoo.com> Hi, Iam doing M.Tech in IIT Madras.For my project work I need 0.18 and 0.13 technology files.I wish to know where I can get them from? Also,can anybody please say me how to get .LEF and .DEF files when I have .LIB and .DB format files of my technology files.Actually I need to use Cadence Place and route tool Silicon Ensemble in my project work.For this tool I need .LEF and .DEF files. ---- Pavan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From naseer at usc.edu Fri Mar 4 14:51:23 2005 From: naseer at usc.edu (Riaz Naseer) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] extracting parasitic resistances and capacitances for spice deck Message-ID: <001401c5210c$b119cf30$0200a8c0@Shayaan> Hi All, I am wondering if someone can help me in getting parasitic resistances and capacitances from magic layout for spice deck. I have tried using extresis and it does generate resistances and capacitances. When I use ext2sim, it works fine. But when I use ext2spice it drops some of the capacitances when converting to spice format. I will greatly appreciate any help. Thanks Riaz Naseer -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050304/159c80ea/attachment.html From tim.edwards at multigig.com Mon Mar 7 14:46:24 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] maxwidth, widespacing rules fixed Message-ID: <200503071946.j27JkOce004228@khachaturian.tim.linglan.net> I have just posted magic version 7.3.68, and I can report that I have invented a completely new algorithm for the "maxwidth" rule that catches all violations (in contrast to the old algorithm, which would only catch violations if the wide metal was a single tile in the database. It was easily subverted, for instance, by having a contact in the middle of a large metal area). I also incorporated the new algorithm into the "widespacing" drc rule, so that one now catches all wide-metal spacing violations (previously, it missed quite a few instances). ---Tim From naseer at usc.edu Tue Mar 8 22:00:45 2005 From: naseer at usc.edu (riaz naseer) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] parasitic resistances from layout Message-ID: <6ccf115e132a.422e208d@usc.edu> Hi All, I have done some experimentation with an inverter. I am doing experiments for assessing how the parasitic resistances will affect the delay. Here is my problem that I am not able to understand: The simple inverter circuit without extracting resistors runs faster than the version with extracted resistances. (There is no difference for the capacitor values in the netlist). My expectation is that a circuit with having more resistors should incur more RC delay and hence should be slower. I will greatly appreciate if anyone can shed some light on this. Thanks and Regards, Riaz Naseer From singh at primecircuits.com Mon Mar 14 17:57:47 2005 From: singh at primecircuits.com (Satpal Singh) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Broken Nets Message-ID: <5.2.1.1.0.20050314174623.02b60948@primecircuits.com> I recently downloaded Magic 7.1 and am using the tech file SCN3ME_SUBM.30.tech27 to design for AMI 0.5 um process. On extraction (ext all) and running ext2spice to generate a netlist, I occasionally (not always) find that a single net in the layout has been broken into 2 different nets in the spice file, this leads to the failure of simulation. Sometimes by moving one of the cells in the design a bit, or changing the position of the label on some random net, seems to fix the problem, and at times it might create additional broken nets. Some of the nets which are broken involve a m1 to m2 connection, though I feel there may be other situations too. In one of the situations I was able to get round the problem by reducing the step size in the extract section of the tech file from 100 to 50, but then it did not solve the problem for some other examples. This seems to be a random problem ! I would greatly appreciate if you can help. Thanks, Satpal Singh Prime Circuits Inc. 301 286 7086 From tim.edwards at multigig.com Tue Mar 15 11:56:44 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] RE: Broken nets Message-ID: <200503151656.j2FGuiaJ003675@khachaturian.tim.linglan.net> Dear Satpal, > I recently downloaded Magic 7.1 and am using the tech file > SCN3ME_SUBM.30.tech27 to design for AMI 0.5 um process. On extraction > (ext all) and running ext2spice to generate a netlist, I occasionally > (not always) find that a single net in the layout has been broken > into 2 different nets in the spice file, this leads to the failure of > simulation. There are a number of reasons this sort of thing can occur. The reason that they seem "random" is that the extractor is not to blame---the extraction algorithm in magic is surprisingly robust--- but there are a number of other subtle errors that can occur. One of them, which may have caused at least one of your broken simulations, is that labels can get copied from one cell into another, and end up on separate layer types (e.g., metal1 and metal2) that are not connected. Extraction will short nets having the same (labeled) name. Usually it is a good idea to ensure that the circuit layout is correct by doing LVS (layout vs. schematic) as well as extraction+simulation. Regards, Tim From singh at primecircuits.com Tue Mar 15 14:26:07 2005 From: singh at primecircuits.com (Satpal Singh) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] RE: Broken nets In-Reply-To: <200503151656.j2FGuiaJ003675@khachaturian.tim.linglan.net> Message-ID: <5.2.1.1.0.20050315141306.00beb200@primecircuits.com> Dear Tim, Thanks for your quick reply. I do agree with you that magic is probably quiet robust, I have been using magic 6.4 and then 6.5 since 1995 and never had this problem before, and I actually love magic to the point where I walked away from other tools. I am not doing anything different from what I have been all these years, and don't understand how labels can get copied from one cell to another, I have always used same label, for example "vin" and "vout" in numerous of my cells where the design is hierarchical. Also, in one instance, i had m2 track of a parent cell overlap by a few lambdas the m2 within a cell, and yet the track in the parent cell came out in the extracted net list as "Floating". In the past, I have extracted the design, then used "ext2spice" to generate a net list on which I have run the simulations and do the LVS, but if I cant even get a proper net list out, I cant do LVS. Please advise, I will greatly appreciate your help here. Satpal At 11:56 AM 3/15/2005 -0500, R. Timothy Edwards wrote: >Dear Satpal, > > > I recently downloaded Magic 7.1 and am using the tech file > > SCN3ME_SUBM.30.tech27 to design for AMI 0.5 um process. On extraction > > (ext all) and running ext2spice to generate a netlist, I occasionally > > (not always) find that a single net in the layout has been broken > > into 2 different nets in the spice file, this leads to the failure of > > simulation. > >There are a number of reasons this sort of thing can occur. The >reason that they seem "random" is that the extractor is not to >blame---the extraction algorithm in magic is surprisingly robust--- >but there are a number of other subtle errors that can occur. > >One of them, which may have caused at least one of your broken >simulations, is that labels can get copied from one cell into another, >and end up on separate layer types (e.g., metal1 and metal2) that >are not connected. Extraction will short nets having the same >(labeled) name. > >Usually it is a good idea to ensure that the circuit layout is correct >by doing LVS (layout vs. schematic) as well as extraction+simulation. > > > Regards, > Tim From singh at primecircuits.com Thu Mar 17 12:41:16 2005 From: singh at primecircuits.com (Satpal Singh) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Broken Nets Message-ID: <5.2.1.1.0.20050317110449.02a1d8c0@primecircuits.com> Dear Tim, The problem of broken nets disappears if I extract the design using the same technology file (SCN3ME_SUBM.30.tech27) but use magic 6.5 instead of 7.1 The problem also disappeared when using magic 7.1, I used the option, "extract no capacitance". The problem of broken nets was that on some designs, it appears to be random, on extraction and ext2spice, one net is broken into 2 nets, which leads to failure of simulation. In reality, there is only one net as can be verified by highlighting the net on the layout. Also using the "getnode" by selecting different portions of the net, the same node name is returned, however the "ext all" followed by ext2spice shows 2 nets. It also seems that sometimes by shifting the position of the label with the same cell, or shifting part of the track in the layout, the problem goes away while it may appear at other areas. I had also extracted the design using the standard scmos tech file with magic 7.1, and I still had the same nets shown as 2 nets, so the problem does not seem to be tech file specific. I am not a programming expert, but I know enough to install Linux and magic, I have used magic 6.4 and 6.5 for 10 years now and have done several designs, so I do not think I am doing something terribly wrong (or may be I am and I was just lucky all along !! ). Do you recommend that I dump magic 7.1 (which I had downloaded only recently) and move on to higher versions, my choice of 7.1 was because it said its a stable version. I would greatly appreciate your advise. Regards, Satpal Singh Prime Circuits Inc. / GSFC >X-POP3-Rcpt: singh@primecircuits.com >Date: Tue, 15 Mar 2005 11:56:44 -0500 >From: "R. Timothy Edwards" >To: singh@primecircuits.com >Subject: RE: Broken nets >Cc: magic-dev@csl.cornell.edu > >Dear Satpal, > > > I recently downloaded Magic 7.1 and am using the tech file > > SCN3ME_SUBM.30.tech27 to design for AMI 0.5 um process. On extraction > > (ext all) and running ext2spice to generate a netlist, I occasionally > > (not always) find that a single net in the layout has been broken > > into 2 different nets in the spice file, this leads to the failure of > > simulation. > >There are a number of reasons this sort of thing can occur. The >reason that they seem "random" is that the extractor is not to >blame---the extraction algorithm in magic is surprisingly robust--- >but there are a number of other subtle errors that can occur. > >One of them, which may have caused at least one of your broken >simulations, is that labels can get copied from one cell into another, >and end up on separate layer types (e.g., metal1 and metal2) that >are not connected. Extraction will short nets having the same >(labeled) name. > >Usually it is a good idea to ensure that the circuit layout is correct >by doing LVS (layout vs. schematic) as well as extraction+simulation. > > > Regards, > Tim From tim.edwards at multigig.com Thu Mar 17 15:23:25 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Re: broken nets in magic Message-ID: <200503172023.j2HKNPtV003998@khachaturian.tim.linglan.net> Dear Satpal, > Do you recommend that I dump magic 7.1 (which I had downloaded only > recently) and move on to higher versions, my choice of 7.1 was because > it said its a stable version. It would be a good idea to check if the extraction was fixed between versions 7.1 and 7.3, by installing a version of 7.3 (locally, so as not to overwrite your working version) and comparing the extraction results to 7.1. If it's still broken, I'd like you to send me an example layout that shows the behavior so that I can debug it. At this time, I have taped out a 5mm x 5mm chip in TSMC 0.18 and another 5mm x 5mm chip in Jazz 0.18 using magic-7.3, so it is at least as reliable as 7.1. > I have used magic 6.4 and 6.5 for 10 years now and have done several > designs, so I do not think I am doing something terribly wrong True, it looks like magic is probably doing something terribly wrong, but I like to make sure it's not driver error before I spend a lot of time tracking down the problem (also, in this case, I want to make sure that it's not something I already fixed between 7.1 and 7.2/7.3). Regards, Tim From rajit at csl.cornell.edu Fri Mar 18 08:44:25 2005 From: rajit at csl.cornell.edu (Rajit Manohar) Date: Thu Oct 30 14:32:50 2008 Subject: [Magic-dev] Broken Nets In-Reply-To: <5.2.1.1.0.20050317110449.02a1d8c0@primecircuits.com> References: <5.2.1.1.0.20050317110449.02a1d8c0@primecircuits.com> Message-ID: <78a718c62117eb37d589e88c8988d1ef@csl.cornell.edu> Hi, Would it be possible to get a copy of the .mag file that causes the problem? When we went from 6.5 -> 7.1, all that happened was various bug-fixes from multiple groups were merged, and some extensions to the command interpreter were included. So the fact that it works in 6.5 but not 7.1 is interesting... Regards, -Rajit On Mar 17, 2005, at 12:41 PM, Satpal Singh wrote: > Dear Tim, > > The problem of broken nets disappears if I extract the design using > the same technology file (SCN3ME_SUBM.30.tech27) but use magic 6.5 > instead of 7.1 > > The problem also disappeared when using magic 7.1, I used the option, > "extract no capacitance". > > The problem of broken nets was that on some designs, it appears to be > random, on extraction and ext2spice, one net is broken into 2 nets, > which leads to failure of simulation. In reality, there is only one > net as can be verified by highlighting the net on the layout. Also > using the "getnode" by selecting different portions of the net, the > same node name is returned, however the "ext all" followed by > ext2spice shows 2 nets. > > It also seems that sometimes by shifting the position of the label > with the same cell, or shifting part of the track in the layout, the > problem goes away while it may appear at other areas. > > I had also extracted the design using the standard scmos tech file > with magic 7.1, and I still had the same nets shown as 2 nets, so the > problem does not seem to be tech file specific. > > I am not a programming expert, but I know enough to install Linux and > magic, I have used magic 6.4 and 6.5 for 10 years now and have done > several designs, so I do not think I am doing something terribly wrong > (or may be I am and I was just lucky all along !! ). > > Do you recommend that I dump magic 7.1 (which I had downloaded only > recently) and move on to higher versions, my choice of 7.1 was > because it said its a stable version. > > I would greatly appreciate your advise. > > Regards, > Satpal Singh > Prime Circuits Inc. / GSFC > > > > >> X-POP3-Rcpt: singh@primecircuits.com >> Date: Tue, 15 Mar 2005 11:56:44 -0500 >> From: "R. Timothy Edwards" >> To: singh@primecircuits.com >> Subject: RE: Broken nets >> Cc: magic-dev@csl.cornell.edu >> >> Dear Satpal, >> >> > I recently downloaded Magic 7.1 and am using the tech file >> > SCN3ME_SUBM.30.tech27 to design for AMI 0.5 um process. On >> extraction >> > (ext all) and running ext2spice to generate a netlist, I >> occasionally >> > (not always) find that a single net in the layout has been broken >> > into 2 different nets in the spice file, this leads to the failure >> of >> > simulation. >> >> There are a number of reasons this sort of thing can occur. The >> reason that they seem "random" is that the extractor is not to >> blame---the extraction algorithm in magic is surprisingly robust--- >> but there are a number of other subtle errors that can occur. >> >> One of them, which may have caused at least one of your broken >> simulations, is that labels can get copied from one cell into another, >> and end up on separate layer types (e.g., metal1 and metal2) that >> are not connected. Extraction will short nets having the same >> (labeled) name. >> >> Usually it is a good idea to ensure that the circuit layout is correct >> by doing LVS (layout vs. schematic) as well as extraction+simulation. >> >> >> Regards, >> Tim > > > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev From piyushsood at gmail.com Thu Mar 24 22:36:35 2005 From: piyushsood at gmail.com (Piyush Sood) Date: Thu Oct 30 14:32:51 2008 Subject: [Magic-dev] Magic 7.1 for Windows on Cygwin - no toolbars Message-ID: <4243a35e.08e13add.515c.fffff43f@mx.gmail.com> Hi, I installled Magic on my PC using the follow method: Magic Quick Install (standard version): (You can try this if the Tcl-based version is not working.) 1. Download magic_win.zip here. Unzip it in the Windows root directory containing Cygwin (by default, C:). 2. From this zip file, executables will appear in /usr/local/bin relative to the Cygwin root directory ("/" in the Cygwin terminal, C:\cygwin\ in Windows, by default). The magic run-time files (tech files, etc.) are in /usr/local/lib/magic/. 3. Start the Cygwin X server by bringing up a Cygwin terminal, and typing "XWin_GL -multiwindow". This window will grab all sorts of debugging output, so it's best to iconify this window. 4. Run magic by bringing up a new Cygwin terminal. Type "export DISPLAY=:0" then "magic" or "magic -d OGL". as described on http://bach.ece.jhu.edu/~tim/programs/magic/windows/windows.html After a little tinkering, I was able to get magic to launch. 1. But when it launches, all i can see is the background. Where are the toolbars etc? There's nothing to allow me to me view any options or bring up the pallette, etc. I can zoom in and out etc in the main window. 2. Also, there is no console. Where can I type the commands? Thanks in advance for your help. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050324/578ad5be/attachment.html From piyushsood at gmail.com Thu Mar 24 22:44:38 2005 From: piyushsood at gmail.com (Piyush Sood) Date: Thu Oct 30 14:32:51 2008 Subject: [Magic-dev] Magic 7.1 for Windows on Cygwin - no toolbars - part 2 Message-ID: <4243a540.2850c7f8.0f81.0786@mx.gmail.com> Further to my previous question, here is some more information: When magic launches, the following message shows up in the xserver window: _____________________________________________________________ Magic 7.2 - Compiled on Sat Apr 10 11:45:24 EST 2004. Input style lambda=1.0(gen): scaleFactor=100, multiplier=1 Using technology "scmos", version 8.2.8. MOSIS Scalable CMOS Technology for Standard Rules Unknown command: 'magic::plot' 'parameter' 'spoolCommand' 'echo use 'lpr -P%s -v -s -JMagic %s' to print plot' at (100, 100) Did you point to the correct window? Unknown command: 'magic::plot' 'parameter' 'directory' '.' at (100, 100) Did you point to the correct window? _____________________________________________________________ I hope this can offer some more clues in answering my original questions. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050324/2582d943/attachment.html From srbu81 at gmail.com Fri Mar 25 20:16:14 2005 From: srbu81 at gmail.com (Saurabh Upadhyay) Date: Thu Oct 30 14:32:52 2008 Subject: [Magic-dev] magic7.2.68 installation on Linux 9.2 Message-ID: These are installation instructions, as specified at http://vlsi.cornell.edu/magic/ 1. mkdir ~/cad-try ~/cad-try/src # start with a fresh directory, or existing ~cad directory 2. gunzip magic-xxx.tar.gz # uncompress the distribution 3. cd ~/cad-try/src; tar xvf - < ~/magic-xxx.tar # un'tar the files 4. cd magic-xxx; setenv CAD_HOME ~/cad-try 5. gmake config # configure for your machine & OS 6. gmake install # compile & install in CAD_HOME Did you set environment variable CAD_HOME? In Linux you can do that with following command: export CAD_HOME="" From spaceborne_calin at yahoo.com Tue Mar 29 12:47:31 2005 From: spaceborne_calin at yahoo.com (Spaceborne Calin) Date: Thu Oct 30 14:32:52 2008 Subject: [Magic-dev] Magic 7.1 for Windows on Cygwin - no toolbars In-Reply-To: <4243a35e.08e13add.515c.fffff43f@mx.gmail.com> Message-ID: <20050329104732.75827.qmail@web53907.mail.yahoo.com> --- Piyush Sood a ?crit?: > Hi, > > I installled Magic on my PC using the follow method: > > Magic Quick Install (standard version): > (You can try this if the Tcl-based version is not working.) > > 1. Download magic_win.zip > > here. Unzip it in the Windows root directory containing Cygwin (by > default, C:). > 2. From this zip file, executables will appear in /usr/local/bin > relative to the Cygwin root directory ("/" in the Cygwin terminal, > C:\cygwin\ in Windows, by default). The magic run-time files (tech > files, > etc.) are in /usr/local/lib/magic/. > 3. Start the Cygwin X server by bringing up a Cygwin terminal, and > typing "XWin_GL -multiwindow". This window will grab all sorts of > debugging > output, so it's best to iconify this window. > 4. Run magic by bringing up a new Cygwin terminal. Type "export > DISPLAY=:0" then "magic" or "magic -d OGL". > > as described on > http://bach.ece.jhu.edu/~tim/programs/magic/windows/windows.html > > After a little tinkering, I was able to get magic to launch. > > 1. But when it launches, all i can see is the background. Where are > the > toolbars etc? There's nothing to allow me to me view any options or > bring up > the pallette, etc. I can zoom in and out etc in the main window. > > 2. Also, there is no console. Where can I type the commands? > the command should be usually typed in the main window of magic and should appear in the terminal window from which the magic is started. To start magic with a toolbar you should write magic -w -d OGL this however works only with the Tcl version of Magic __________________________________________________________________ D?couvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Cr?ez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ From piyushsood at gmail.com Tue Mar 29 20:58:43 2005 From: piyushsood at gmail.com (Piyush Sood) Date: Thu Oct 30 14:32:52 2008 Subject: [Magic-dev] Magic 7.1 for Windows on Cygwin - no toolbars In-Reply-To: <20050329104732.75827.qmail@web53907.mail.yahoo.com> References: <4243a35e.08e13add.515c.fffff43f@mx.gmail.com> <20050329104732.75827.qmail@web53907.mail.yahoo.com> Message-ID: <67f4a84c05032919585b846dc0@mail.gmail.com> Hi, Since I was unable to install the TCL version correctly at first, I had to resort to installing this version. But then I went back and managed to install the TCl version correctly. I am able to launch magic properly now and see all the toolbars etc (I understand that the toolbars are only available as a convenience in the TCL version, all the commands still exist in the other version). There are still some compatibility issues in working on the windows version and using those layouts on the solaris version and vice versa, but I think I've figured out a workaround. Thank you to everyone for your replies. -Piyush. -----Original Message----- From: Spaceborne Calin [mailto:spaceborne_calin@yahoo.com] Sent: Tuesday, March 29, 2005 3:48 AM To: Piyush Sood; magic-dev@vlsi.cornell.edu Subject: Re: [Magic-dev] Magic 7.1 for Windows on Cygwin - no toolbars the command should be usually typed in the main window of magic and should appear in the terminal window from which the magic is started. To start magic with a toolbar you should write magic -w -d OGL this however works only with the Tcl version of Magic --- Piyush Sood a ?crit : > Hi, > > I installled Magic on my PC using the follow method: > > Magic Quick Install (standard version): > (You can try this if the Tcl-based version is not working.) > > 1. Download magic_win.zip > > here. Unzip it in the Windows root directory containing Cygwin (by > default, C:). > 2. From this zip file, executables will appear in /usr/local/bin > relative to the Cygwin root directory ("/" in the Cygwin terminal, > C:\cygwin\ in Windows, by default). The magic run-time files (tech > files, > etc.) are in /usr/local/lib/magic/. > 3. Start the Cygwin X server by bringing up a Cygwin terminal, and > typing "XWin_GL -multiwindow". This window will grab all sorts of > debugging > output, so it's best to iconify this window. > 4. Run magic by bringing up a new Cygwin terminal. Type "export > DISPLAY=:0" then "magic" or "magic -d OGL". > > as described on > http://bach.ece.jhu.edu/~tim/programs/magic/windows/windows.html > > After a little tinkering, I was able to get magic to launch. > > 1. But when it launches, all i can see is the background. Where are > the > toolbars etc? There's nothing to allow me to me view any options or > bring up > the pallette, etc. I can zoom in and out etc in the main window. > > 2. Also, there is no console. Where can I type the commands? > __________________________________________________________________ D?couvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Cr?ez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ From ceklock at gmail.com Wed Mar 30 23:25:34 2005 From: ceklock at gmail.com (Carlos Klock) Date: Thu Oct 30 14:32:53 2008 Subject: [Magic-dev] Problems creating .mag file by hand Message-ID: <61d405e505033018256d1f2911@mail.gmail.com> Hello, my name is Carlos and I am working on a tool that generates a simple IC layout. The tool must generate as output a magic file, but this file is failing to be opened by Magic. I am sending the sample file for you, I really dont know why magic is not opening it. Thank you for any help, Carlos. -------------- next part -------------- z'??mj?Zr?????+???t??z?????? >gmake[2]: *** No rule to make target `../tech/libtech.o', needed by `libmpack .a'. Stop. >From this line it seems that in addition to what Timothy suggested you also need to install Technical Libraries. Technical Libraries contain rules and standards for semiconductor process technology. Goto home page of Magic, http://vlsi.cornell.edu/magic/ and under the following section you will find information about technical libraries. Downloading / Getting Magic -> Useful links -> Tech files for MOSIS-supported processes From rajit at csl.cornell.edu Thu Mar 31 09:20:43 2005 From: rajit at csl.cornell.edu (Rajit Manohar) Date: Thu Oct 30 14:32:53 2008 Subject: [Magic-dev] Problems creating .mag file by hand In-Reply-To: <61d405e505033018256d1f2911@mail.gmail.com> References: <61d405e505033018256d1f2911@mail.gmail.com> Message-ID: Hi, The syntax of the "rect" statement is rect llx lly urx ury where (llx, lly) is the lower-left coordinate, and (urx,ury) is the upper-right coordinate. The file you sent seems to have lly and ury reversed in its "rect" lines, so they are being interpreted as zero height rectangles. Regards, -Rajit On Mar 30, 2005, at 9:25 PM, Carlos Klock wrote: > From j_gurumallesh at yahoo.co.in Thu Mar 31 20:29:22 2005 From: j_gurumallesh at yahoo.co.in (gurumallesh j) Date: Thu Oct 30 14:32:54 2008 Subject: [Magic-dev] PLEASE HELP Message-ID: <20050331192922.66120.qmail@web8502.mail.in.yahoo.com> DEAR SIR, I AM UNABLE TO FIND THE 0.18 TECH FILE AND LVS(LAYOUT VS SCHEMATIC) FOR MAGIC.PLEASE HELP ME REGARDING THIS. THANK YOU IN ADVANCE Yahoo! India Matrimony: Find your life partneronline.-------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050331/b8735596/attachment.html From tim at opencircuitdesign.com Thu Mar 31 12:15:49 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:54 2008 Subject: [Magic-dev] installing magic on Fedora Core 3 In-Reply-To: References: Message-ID: <424C3045.8010607@opencircuitdesign.com> (I have no idea where the original message came from. What I saw was an apparent reply from Saurabh Upadhyay to a message that I didn't see posted on magic-dev.) >> gmake[2]: *** No rule to make target `../tech/libtech.o', needed by > `libmpack .a'. Stop. There hasn't been a libtech.c or libmpack.a since somewhere back in version 6.5 or 7.0. If you're trying to compile these on Fedora Core, you had better be an expert in porting source code, because you're going to have a lot of work to do. Stick with magic-7.1, 7.2, or 7.3, all of which configure and compile readily on Linux. The development platform for 7.3 (i.e., my laptop) is a Fedora Core 3 system. ---Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 3600 Glen Canyon Road | phone: (831) 440-0600 ext. 20 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From mika at async.caltech.edu Fri Apr 1 07:55:28 2005 From: mika at async.caltech.edu (Mika Nystroem) Date: Thu Oct 30 14:32:54 2008 Subject: [Magic-dev] installing magic on Fedora Core 3 In-Reply-To: Your message of "Thu, 31 Mar 2005 12:15:49 EST." <424C3045.8010607@opencircuitdesign.com> Message-ID: <200504011555.j31FtTlF014170@boron.async.caltech.edu> Does this mean that mpla, mquilt, et al., are dusty decks now, or have they been ported too? (I recall they use mpack.) Mika "R. Timothy Edwards" writes: >(I have no idea where the original message came from. What I saw was >an apparent reply from Saurabh Upadhyay to a message that I didn't >see posted on magic-dev.) > > >> gmake[2]: *** No rule to make target `../tech/libtech.o', needed by > > `libmpack .a'. Stop. > >There hasn't been a libtech.c or libmpack.a since somewhere back in >version 6.5 or 7.0. If you're trying to compile these on Fedora Core, >you had better be an expert in porting source code, because you're >going to have a lot of work to do. Stick with magic-7.1, 7.2, or 7.3, >all of which configure and compile readily on Linux. The development >platform for 7.3 (i.e., my laptop) is a Fedora Core 3 system. > > ---Tim > >+--------------------------------+-------------------------------------+ >| Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | >| MultiGiG, Inc. | web: http://www.multigig.com | >| 3600 Glen Canyon Road | phone: (831) 440-0600 ext. 20 | >| Scotts Valley, CA 95066 | cell: (240) 401-0616 | >+--------------------------------+-------------------------------------+ >_______________________________________________ >magic-dev mailing list >magic-dev@vlsi.cornell.edu >http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev From tim at opencircuitdesign.com Fri Apr 1 11:25:01 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:54 2008 Subject: [Magic-dev] Re: mpla et al. In-Reply-To: <200504011555.j31FtTlF014170@boron.async.caltech.edu> References: <200504011555.j31FtTlF014170@boron.async.caltech.edu> Message-ID: <424D75DD.80402@opencircuitdesign.com> Dear Mika, > Does this mean that mpla, mquilt, et al., are dusty decks now, or > have they been ported too? (I recall they use mpack.) They're not yet "dusty decks", and I have a port for Magic-7.1 (it's on my magic-7.1 web page). However, when I switched to the Tcl-based version, the static-linked mpack library was not possible to build, and I have not yet gotten around to porting it. I think it would be nice to have the platools programs be Tcl object files that would load into magic (or rather, both would load into Tcl, so that the subroutines in magic are available to platools). This avoids a lot of the problems of creating an independent library of duplicate routines. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 3600 Glen Canyon Road | phone: (831) 440-0600 ext. 20 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From jwwebb at ece.ucdavis.edu Sat Apr 2 00:31:51 2005 From: jwwebb at ece.ucdavis.edu (Jeremy W. Webb) Date: Thu Oct 30 14:32:56 2008 Subject: [Magic-dev] Install issues with Magic ver 7.2 on Fedora Core 3 Message-ID: <1112430711.12483.5.camel@localhost.localdomain> Hi, I was having tons of issues installing Magic version 7.1 on my Fedora Core 3 Linux machine, so I tried to install version 7.2. The install for ver 7.2 made it a lot farther through the install process, but there was one glitch. I got the following error: ext2spice.c:1291: error: conflicting types for 'topVisit' ext2spice.c:874: error: previous implicit declaration of 'topVisit' was here It looks like it was related to the RSIM package. Do you know why it failed, or what I can do to fix the issue? This is my first time installing Magic, so I'm sure I'm doing something wrong. I've attached the make.log for your reference. I also attached my defs.mak file. I changed the -m486 to -march=i386. Does that seem correct? Thanks for your help, Jeremy Webb Graduate Student University of California, Davis Electrical & Computer Engineering Dept. -------------- next part -------------- A non-text attachment was scrubbed... Name: make.log Type: text/x-log Size: 125688 bytes Desc: not available Url : http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050402/57b66f2e/make.bin -------------- next part -------------- # This file was auto-generated by running the scripts/config program. Feel free # to change the values in here to suit your needs. Beware that running scripts/config # again will overwrite any changes! SHELL = /bin/sh VERSION = 7.2 # Change CADDIR to install in a different place CADDIR = /home/jeremywebb/cad/magic BINDIR = ${CADDIR}/bin LIBDIR = ${CADDIR}/lib MANDIR = ${CADDIR}/man SYSDIR = ${CADDIR}/lib/magic/sys SCMDIR = ${CADDIR}/lib/magic/scm TCLDIR = ${CADDIR}/lib/magic/tcl SCRIPTS = ${MAGICDIR}/scripts MAIN_EXTRA_LIBS = ${MAGICDIR}/calma/libcalma.o ${MAGICDIR}/cif/libcif.o ${MAGICDIR}/plot/libplot.o ${MAGICDIR}/garouter/libgarouter.o ${MAGICDIR}/mzrouter/libmzrouter.o ${MAGICDIR}/router/librouter.o ${MAGICDIR}/irouter/libirouter.o ${MAGICDIR}/grouter/libgrouter.o ${MAGICDIR}/gcr/libgcr.o ${MAGICDIR}/lef/liblef.o MODULES += calma cif plot garouter grouter irouter mzrouter router gcr lef UNUSED_MODULES += lisp PROGRAMS += magicusage extcheck graphics net2ir INSTALL_CAD_DIRS += # Define your make environment # MAKE = gmake # MAKEFLAGS = -j4 M4 = m4 RM = rm -f CP = cp AR = ar ARFLAGS = crv LD = ld -r LINK = ld -r SHDLIB_EXT = .so LDDL_FLAGS = -shared -Wl,--version-script=${MAGICDIR}/magic/symbol.map RANLIB = ranlib EXEEXT = CC = gcc CPP = /lib/cpp -P -traditional CPPFLAGS = -I. -I${MAGICDIR} DFLAGS = -DSHDLIB_EXT=\".so\" -DHAVE_LIMITS_H -Dlinux -DSYSV -DF_OK=0 -DW_OK=2 -D__NO_STRING_INLINES -DISC -DHAVE_VA_COPY -DCALMA_MODULE -DCIF_MODULE -DPLOT_MODULE -DROUTE_MODULE -DRSIM_MODULE -DLEF_MODULE -DUSE_NEW_MACROS -DCAD_DIR=\"${CADDIR}\" CFLAGS = -g -march=i386 # These CFLAGS may include switches for an optimized compile # CFLAGS = -g -m486 -O6 -fomit-frame-pointer READLINE_DEFS = READLINE_LIBS = DEPEND_FLAG = -MM DEPEND_FILE = Depend GR_CFLAGS = -I/usr/X11R6/include GR_DFLAGS = -DX11 -DXLIB -DX11HELP_PROG=\"${X11HELP_PROG}\" -DHAVE_PTHREADS GR_LIBS = -lX11 -L/usr/X11R6/lib/ -lbsd-compat -lpthread GR_SRCS = ${X11_SRCS} grX11thread.c GR_HELPER_SRCS = GR_HELPER_PROG = ALL_TARGET = tcl INSTALL_TARGET = install-tcl OBJS = ${SRCS:.c=.o} LIB_OBJS = ${LIB_SRCS:.c=.o} CLEANS = ${OBJS} ${LIB_OBJS} lib${MODULE}.a lib${MODULE}.o ${MODULE} From faithnomore182 at gmail.com Fri Apr 15 00:45:39 2005 From: faithnomore182 at gmail.com (Piyush Sood) Date: Thu Oct 30 14:32:56 2008 Subject: [Magic-dev] creation of extra nodes in .ext files? Message-ID: <8663850405041422452a20842f@mail.gmail.com> Hi all, I'm working on Magic 7.2 on Sun Solaris. Can anyone possibly shed some light on why the following happens? When I draw a simple layout like this: ------------------------------------------------------------------------------------------------------------ magic tech scmos timestamp 1113543856 << nwell >> rect -45 10 -20 20 rect -11 10 7 20 << polysilicon >> rect -38 15 -36 17 rect -29 15 -27 17 rect -4 15 -1 17 rect -38 -6 -36 12 rect -29 -6 -27 12 rect -4 0 -1 12 rect -4 -5 -1 -3 rect -38 -11 -36 -9 rect -29 -11 -27 -9 << ndiffusion >> rect -5 -3 -4 0 rect -1 -3 0 0 rect -39 -9 -38 -6 rect -36 -9 -29 -6 rect -27 -9 -26 -6 << pdiffusion >> rect -39 12 -38 15 rect -36 12 -35 15 rect -31 12 -29 15 rect -27 12 -26 15 rect -5 12 -4 15 rect -1 12 0 15 << metal1 >> rect -43 20 15 23 rect -43 16 -40 20 rect -26 16 -23 20 rect -9 16 -6 20 rect -34 7 -31 12 rect -49 3 -42 6 rect -34 4 -8 7 rect -1 4 23 7 rect -49 -12 -46 3 rect -34 0 -31 4 rect -42 -3 -31 0 rect -42 -5 -39 -3 rect -9 -6 -6 -3 rect -22 -9 -6 -6 rect 6 -9 15 -6 rect 20 -12 23 4 rect -49 -15 23 -12 << ntransistor >> rect -4 -3 -1 0 rect -38 -9 -36 -6 rect -29 -9 -27 -6 << ptransistor >> rect -38 12 -36 15 rect -29 12 -27 15 rect -4 12 -1 15 << polycontact >> rect -42 3 -38 7 rect -8 4 -4 8 << ndcontact >> rect -43 -9 -39 -5 rect -9 -3 -5 1 rect 0 -3 4 1 rect -26 -9 -22 -5 << pdcontact >> rect -43 12 -39 16 rect -35 12 -31 16 rect -26 12 -22 16 rect -9 12 -5 16 rect 0 12 4 16 << labels >> rlabel polysilicon -28 1 -28 1 1 enable rlabel metal1 -20 -8 -20 -8 1 gnd rlabel metal1 -23 4 -23 4 1 nandout rlabel metal1 -42 22 -42 22 5 vdd rlabel polycontact -41 4 -41 4 1 en2 rlabel metal1 7 6 7 6 1 test << end >> ------------------------------------------------------------------------------------------------------------ When I extract it using "extract", I get the following .ext file: ------------------------------------------------------------------------------------------------------------ timestamp 1113543856 version 7.2 tech scmos style lambda=1.0(scna20_orb) scale 1000 1 100 resistclasses 26670 59550 23860 19690 27260 2000000 49 26 2505830 node "m1_6_n9#" 0 1269 6 -9 m1 0 0 0 0 0 0 0 0 0 0 0 0 27 24 0 0 0 0 node "a_n36_n9#" 62 0 -36 -9 ndiff 21 20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 node "a_n1_n3#" 44 752 -1 -3 ndiff 19 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 node "gnd" 170 4183 -27 -9 ndiff 38 36 0 0 0 0 0 0 0 0 0 0 57 44 0 0 0 0 node "a_n1_12#" 99 752 -1 12 pdiff 0 0 19 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 node "enable" 334 4764 -29 -11 p 0 0 0 0 56 60 0 0 0 0 0 0 0 0 0 0 0 0 node "nandout" 384 13486 -43 -9 ndc 19 18 25 22 82 58 0 0 0 0 0 0 144 102 0 0 0 0 node "test" 336 25674 -42 3 pc 0 0 0 0 72 68 0 0 0 0 0 0 402 274 0 0 0 0 equiv "test" "en2" node "vdd" 638 10434 -43 12 pdc 0 0 57 54 0 0 0 0 0 0 0 0 210 146 0 0 0 0 node "w_n11_10#" 4510 0 -11 10 nw 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 180 56 node "w_n45_10#" 6265 0 -45 10 nw 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 250 70 cap "nandout" "enable" 180 cap "vdd" "w_n11_10#" 564 cap "w_n45_10#" "vdd" 1128 cap "w_n45_10#" "enable" 1432 cap "nandout" "w_n11_10#" 1828 cap "w_n45_10#" "nandout" 282 cap "test" "nandout" 180 cap "w_n45_10#" "test" 1432 device mosfet nfet -29 -9 -28 -8 2 3 "Gnd!" "enable" 4 0 "a_n36_n9#" 3 0 "gnd" 3 0 device mosfet nfet -38 -9 -37 -8 2 3 "Gnd!" "test" 4 0 "nandout" 3 0 "a_n36_n9#" 3 0 device mosfet nfet -4 -3 -3 -2 3 3 "Gnd!" "nandout" 6 0 "gnd" 3 0 "a_n1_n3#" 3 0 device mosfet pfet -4 12 -3 13 3 3 "w_n11_10#" "nandout" 6 0 "vdd" 3 0 "a_n1_12#" 3 0 device mosfet pfet -29 12 -28 13 2 3 "w_n45_10#" "enable" 4 0 "nandout" 3 0 "vdd" 3 0 device mosfet pfet -38 12 -37 13 2 3 "w_n45_10#" "test" 4 0 "vdd" 3 0 "nandout" 3 0 ------------------------------------------------------------------------------------------------------------ So my question is that where do these nodes "a_n36_n9#" and "a_n1_n3#" etc come from? When I do a exttosim on this file and then run irsim, it shows all these extra nodes that i never put in there. where are they coming from? I have redrawn this layout in 4 separate files but eventually, some random nodes start to show up. I have been troubleshooting this extensively (deleting selected portions of the layout and then re-extracting, deleting selected lines from the .ext and .sim files etc). That seems to help temprorarily, until i put certain sections like ndiff back, in which case the nodes come back or worse, there are now even more random nodeswhen i re-extract Does anyone have any ideas on what the problem might be? Thanks in advance. -Piyush Sood. From tim at opencircuitdesign.com Fri Apr 15 23:18:12 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:56 2008 Subject: [Magic-dev] RE: "extra" nodes from magic extract Message-ID: <200504160218.j3G2ICNI023572@opencircuitdesign.com> Dear Piyush, > So my question is that where do these nodes "a_n36_n9#" and > "a_n1_n3#" etc come from? Magic's names for unlabeled nodes can be interpreted as: (plane_short_name)_(x_position)_(y_position)# where the 'plane short name' is found in scmos.tech but generally follows the convention w=well, a=active, m1=metal1, etc., and "n" in front of a number means negative. So you can track down the node "a_n36_n9#" by looking for the layer on active (diffusion or poly) at position (-36, -9). There really are 12 nodes in your layout. In addition to the labeled nodes, two transistors have unconnected ends (which were presumably intended to attach to "test", perhaps by the misplaced piece of metal1, which gets counted as another node). There is also one internal node in the AND gate between the two nMOS transistors, and then there are the two wells which will be considered isolated until connected to vdd with a "nsc" contact. It is not necessary to have drawn wells for an extraction, but it is necessary to have the well and substrate contacts in a circuit if you want it to work correctly. If you put both nwell and pwell and connect both with contacts, you will get the proper substrate (bulk) contacts to the transistor devices in the netlist. If you leave the wells undrawn, you will get the default nodes "Vdd!" and "Gnd!" in those positions, which must be equated somehow with the power and ground networks. In magic-7.1, you would need to label your power and ground networks "Vdd!" and "Gnd!", resepectively. In the Tcl/Tk versions of magic-7.2 and 7.3, you can just put the Tcl commands "set VDD vdd" and "set GND gnd" to denote that your default well and substrate nodes are connected to those nets (which is, of course, a misleading idealization if you don't have the well and substrate ties). Regards, Tim From tim.edwards at multigig.com Sat Apr 16 14:56:09 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:32:56 2008 Subject: [Magic-dev] Magic-7.3.83 Message-ID: <200504161756.j3GHu98F011424@khachaturian.tim.linglan.net> Hello everyone, I don't know how many people have been paying close attention to my release notes on magic-7.3, but I'd like to point out some exciting new features that I added in the last two weeks, for which I have worked out pretty much all of the bugs, leaving once again a reasonably stable distribution. The "new" magic uses an internal backing-store mechanism on the graphics to do a quick save of the layout drawing. The so- called "highlights" like the box and selections are drawn after the save. So the box can be moved around by replacing the layout underneath from backing store, rather than redrawing the layout underneath from the database. The result is that boxes and other highlights can be moved around so fast that certain functions can be made interactive (see below). In addition, the backing store is used to map portions of the layout as one scrolls around the layout, so only that part of the layout that was previously off-screen needs to be redrawn. Needless to say, this makes scrolling very fast (are you aware that you can do short scrolling motions with the mouse wheel?). So, what can now be done interactively? Well, first there is (in the Tcl/Tk GUI version (magic -w)) a menu item "Options-> Crosshair" that implements a crosshair cursor on the screen. Second, there is a new tool called the "pick tool" that allows one to grab a selection and move it around the screen with the mouse (a "drag and drop" type mechanism). Finally, I have revamped the "wire tool" with an interactive feature that shows where magic is going to place the next wire (plus, shift-Button bindings can be used to move up and down the metal routing layers, and the scroll wheel changes the width of the wire used for routing). I think that anyone who deigns to get used to the new methods will find that wiring things up is relatively painless (although it still needs a feature to automatically enforce spacing design rules). Comments and suggestions are always welcome. Enjoy! By the way, I am moving to California on a semi-permanent basis beginning May 1. Due to the move, I and my Open Circuit Design, Inc., operation will be effectively unavailable between roughly April 24 to May 3. MultiGiG is also moving at the same time to the Borland building in Scotts Valley, up the road from where we are now. My new home address will be in Cupertino, but hopefully everything else will be the same (email, cell phone, etc.). If you want to get in touch with me between now and early May, please write to me at the multigig.com address only, as that mail server is the only on sitting on a computer that will not be moved during that timeframe. ---Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 3600 Glen Canyon Road | phone: (831) 440-0600 ext. 20 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From faithnomore182 at gmail.com Mon Apr 18 23:59:44 2005 From: faithnomore182 at gmail.com (Piyush Sood) Date: Thu Oct 30 14:32:56 2008 Subject: [Magic-dev] Re: "extra" nodes from magic extract In-Reply-To: <200504160218.j3G2ICNI023572@opencircuitdesign.com> References: <200504160218.j3G2ICNI023572@opencircuitdesign.com> Message-ID: <8663850405041821597bd89f4e@mail.gmail.com> Tim, Thanks very much for your detailed reply. It all makes perfect sense now. I was under the impression that these nodes might somehow be interfering with the simulation and implementation of my designs/layouts. After completing the layout and running the simulation, I realized that in fact they don't. Thanks again, Piyush. On 4/15/05, R. Timothy Edwards wrote: > Dear Piyush, > > > So my question is that where do these nodes "a_n36_n9#" and > > "a_n1_n3#" etc come from? > > Magic's names for unlabeled nodes can be interpreted as: > > (plane_short_name)_(x_position)_(y_position)# > > where the 'plane short name' is found in scmos.tech but generally > follows the convention w=well, a=active, m1=metal1, etc., and "n" > in front of a number means negative. > > So you can track down the node "a_n36_n9#" by looking for the > layer on active (diffusion or poly) at position (-36, -9). > > There really are 12 nodes in your layout. In addition to the > labeled nodes, two transistors have unconnected ends (which were > presumably intended to attach to "test", perhaps by the misplaced > piece of metal1, which gets counted as another node). There is > also one internal node in the AND gate between the two nMOS > transistors, and then there are the two wells which will be > considered isolated until connected to vdd with a "nsc" contact. > > It is not necessary to have drawn wells for an extraction, but it > is necessary to have the well and substrate contacts in a circuit > if you want it to work correctly. If you put both nwell and pwell > and connect both with contacts, you will get the proper substrate > (bulk) contacts to the transistor devices in the netlist. If you > leave the wells undrawn, you will get the default nodes "Vdd!" and > "Gnd!" in those positions, which must be equated somehow with > the power and ground networks. In magic-7.1, you would need to > label your power and ground networks "Vdd!" and "Gnd!", resepectively. > In the Tcl/Tk versions of magic-7.2 and 7.3, you can just put the > Tcl commands "set VDD vdd" and "set GND gnd" to denote that your default > well and substrate nodes are connected to those nets (which is, > of course, a misleading idealization if you don't have the well > and substrate ties). > > Regards, > Tim > From diogenes at cpdee.ufmg.br Tue Apr 19 14:25:37 2005 From: diogenes at cpdee.ufmg.br (Diogenes C. da Silva Jr.) Date: Thu Oct 30 14:32:56 2008 Subject: [Magic-dev] Magic 7.1 and RH9 Message-ID: <5.2.0.9.0.20050419131754.02945ec0@pop.cpdee.ufmg.br> Hi all, I succesfully installed MAgic 7.1 on a RH9 running on a notebook. Just to check the installation I ran it while logged as root. It worked fine, but I typed something and magic exited. After rebooting the system later, I could not log on the system again. The system keeps trying to load gnome and just blinks the screen. Then gives up and linux enters in a text screen. The error log says "couldn't find local XKB keymap" and "fatal IO error 104 Xserver ":0.0" among other messages. Any help?? TIA, -- Diogenes C da Silva Jr., Ph.D. Prof. Adjunto Depto. Engenharia Eletrica - UFMG Brazil Telefone: (31) 3499-4835 From gopinath.vb at ge.com Sun Apr 24 16:51:52 2005 From: gopinath.vb at ge.com (VB, Gopinath (GE Infrastructure)) Date: Thu Oct 30 14:32:57 2008 Subject: [Magic-dev] Magic VLSI for windows Message-ID: Hi, How to install the windows version of MAGIC? Regards V.B. Gopinath -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050424/250d6e29/attachment.html From faithnomore182 at gmail.com Tue Apr 26 12:44:25 2005 From: faithnomore182 at gmail.com (Piyush Sood) Date: Thu Oct 30 14:32:57 2008 Subject: [Magic-dev] Magic VLSI for windows In-Reply-To: References: Message-ID: <866385040504261044413b825b@mail.gmail.com> All the instrutctions are on this page: http://bach.ece.jhu.edu/~tim/programs/magic/windows/windows.html On 4/24/05, VB, Gopinath (GE Infrastructure) wrote: > > > Hi, > > How to install the windows version of MAGIC? > > Regards > > V.B. Gopinath > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev > > > From fang at csl.cornell.edu Wed Apr 27 18:26:34 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:32:57 2008 Subject: [Magic-dev] magic 7.1 on Mac OS X 10.3 (darwin) Message-ID: <20050427171735.N90594-100000@shannon.csl.cornell.edu> Magic-folks, I've assembled some instructions for installing the current CVS snapshot of magic-7.1 on Mac OS X 10.3. The current state of the CVS head does not compile out-of-the-box and needs some patching. The instructions and patch can be found at: http://www.csl.cornell.edu/~fang/sw/magic-7.1-osx.html Hope this is of some use. If mac-users could give me some feedback on the instructions (corrections, especially), I'll update the page accordingly. If any of the developers could review the patch for commit into CVS that'd be even better. David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- *gag* work in progress From graham.petley at vlsitechnology.org Sun May 1 13:45:05 2005 From: graham.petley at vlsitechnology.org (Graham Petley) Date: Thu Oct 30 14:32:57 2008 Subject: [Magic-dev] Updated release of standard cell libraries Message-ID: <20050501194505.80394.qmail@web204.biz.mail.re2.yahoo.com> Hallo, A new version of my open-source standard cell library can now be downloaded from http://www.vlsitechnology.org I have done work on which cells to include in the library and used this to increase the vsclib up to 209 cells. The work is documented on my web site. The library uses open source software. The layout has been drawn in Alliance Graal, imported into Magic and extracted to a Spice deck. The cell schematics are drawn with Xcircuit. The spice simulation uses Winspice. There is an on-line data book. I'm happy to receive any comments, especially on the choice of cells. Best regards, Graham Petley From ganesh_ec at rediffmail.com Tue May 10 10:26:29 2005 From: ganesh_ec at rediffmail.com (ganesh r shamnur) Date: Thu Oct 30 14:32:58 2008 Subject: [Magic-dev] Magic Query Message-ID: <20050510092629.3199.qmail@webmail45.rediffmail.com> ? Hello, I have few queries regarding MAGIC software 1) To what technology features of transistors does the MAGIC layout support. 2) How do I get to know more about the pre-layout(Design) phase compatible with the MAGIC software 3) Why is metal1 drawn with 4lambda size while the actual textual size is 3lambda. thanks and regards Ganesh R Shamnur VLSI Student www.sjce.ac.in Mysore, INDIA-------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050510/e50b7a83/attachment.html From jmalik at du.edu Mon May 9 22:04:25 2005 From: jmalik at du.edu (Jemika Malik) Date: Thu Oct 30 14:32:59 2008 Subject: [Magic-dev] Diodes in Magic Message-ID: <001601c5550c$f9ac3bf0$6700a8c0@jemikamalik> Hi all, I am using magic 7.2 on sun-solaris. Can some one suggest me how I can extract diodes? I want p-type material and n-type material to be in different layers. Thank you very much, --Jemika Malik-------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050509/ffc8a279/attachment.html From jmalik at du.edu Mon May 9 22:04:25 2005 From: jmalik at du.edu (Jemika Malik) Date: Thu Oct 30 14:33:00 2008 Subject: [Magic-dev] Diodes in Magic Message-ID: <001601c5550c$f9ac3bf0$6700a8c0@jemikamalik> Hi all, I am using magic 7.2 on sun-solaris. Can some one suggest me how I can extract diodes? I want p-type material and n-type material to be in different layers. Thank you very much, --Jemika Malik-------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050509/ffc8a279/attachment-0001.html From tim at opencircuitdesign.com Wed May 11 12:36:59 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:00 2008 Subject: [Magic-dev] Magic Query In-Reply-To: <20050510092629.3199.qmail@webmail45.rediffmail.com> References: <20050510092629.3199.qmail@webmail45.rediffmail.com> Message-ID: <428250CB.7080605@opencircuitdesign.com> Dear Ganesh, > 1) To what technology features of transistors does the MAGIC layout > support. Magic-7.2 and magic-7.3 (and I think the feature was added to 7.1) support feature sizes down to 1 nanometer. Standard (scmos) technology files are available for processes down to 0.18um. Proprietary technology files can (sometimes, with NDAs, lawyers' agreement, etc.) be obtained for 90nm and 65nm processes. > 2) How do I get to know more about the pre-layout(Design) phase compatible > with the MAGIC software Depends on what you want to do. People have used all sorts of schematic and simulation tools with magic. Please be more specific. > 3) Why is metal1 drawn with 4lambda size while the actual textual size > is 3lambda. "textual size"? Requirements for feature sizes depend on the process, design rules, and choices made by whoever designs the technology files. Vendor design rules rarely ever fall neatly on lambda boundaries (except for poly gate width), so the technology file usually rounds the design rules up (conservatively) to the nearest lambda boundary. Typically for metal1 this is 3 lambda, but some process design rules require metal1 width to be slightly larger than 3 lambda, in which case the technology file may round up to 4 lambda. +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim at opencircuitdesign.com Wed May 11 12:43:45 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:00 2008 Subject: [Magic-dev] Diodes in Magic In-Reply-To: <001601c5550c$f9ac3bf0$6700a8c0@jemikamalik> References: <001601c5550c$f9ac3bf0$6700a8c0@jemikamalik> Message-ID: <42825261.3070600@opencircuitdesign.com> Dear Jemika, > I am using magic 7.2 on sun-solaris. Can some one suggest me how I > can extract diodes? > I want p-type material and n-type material to be in different layers. Magic versions 7.2 and 7.3 support extraction of diodes; however, these are very simple and probably need some tweaking in the resulting SPICE deck if you need a parameterized model. If you have just one kind of diode in the layout, you can adjust the model parameters to match the layout, then it works pretty well. In the "extract" section of the technology file, you need: device diode After doing "ext2spice", this will produce the line: D Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From mescobosa at Smarthome.com Wed May 11 18:27:12 2005 From: mescobosa at Smarthome.com (Marcus Escobosa) Date: Thu Oct 30 14:33:01 2008 Subject: [Magic-dev] supported Magic platforms Message-ID: What platforms is Magic typically compiled on? I have Fedora 3 and get build errors for Magic 6.5 and 7. I have followed the README instructions. On Magic 7 I get build errors involving gcc's lack of support for the varargs functions. Gcc now supports only stdarg, and some of the source use incompatible varargs function calls. On magic 6.5, I get a redefinition error for wchar_t. This problem kind of seems like a gcc issue, since the conflicting files seem to be in the gcc libraries. Any help is appreciated. Is there a need for a Fedora port person? I don't have much time, but maybe I can help. Thanks Marcus Escobosa From tim at opencircuitdesign.com Fri May 13 10:01:19 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:01 2008 Subject: [Magic-dev] supported Magic platforms In-Reply-To: References: Message-ID: <4284CF4F.4030908@opencircuitdesign.com> Dear Marcus, > What platforms is Magic typically compiled on? > I have Fedora 3 and get build errors for Magic 6.5 and 7. I have > followed the README instructions. Magic versions prior to 7.0 were not developed on Linux and need quite a bit of work to port---effectively, version 7.1 is the Linux port of 6.5 plus other fixes and improvements. However, gcc-3 breaks all versions except 7.2 and 7.3, in which I changed the varargs code. Either 1) get and install gcc-2.95 (always a useful idea, since gcc-3 breaks a lot of applications), or 2) get magic 7.3 from my website at http://bach.ece.jhu.edu/~tim/programs/magic/. Versions 7.2 and 7.3 have been regularly compiled and tested on Debian, RedHat, FC2, FC3, and FC2 on an AMD Opteron (64 bit). It is somewhat less often tested on other systems, but should compile and run on most any UNIX-like OS, including Cygwin. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From ejprinz at austin.rr.com Fri May 13 21:56:17 2005 From: ejprinz at austin.rr.com (Erwin J. Prinz) Date: Thu Oct 30 14:33:01 2008 Subject: [Magic-dev] supported Magic platforms In-Reply-To: References: Message-ID: <42855AC1.9030509@austin.rr.com> Marcus: I believe most people using Magic these days use Tim Edwards et al.'s 7.2 or 7.3, see http://bach.ece.jhu.edu/~tim/programs/magic/magic7_3.html I've been using 7.3 for a couple of months and 7.2 for more than a year for a large project (90nm Flash test structure layout, 1000's of cells) and only found one "serious" bug which by now has been fixed. So, you are much better off using 7.3 compared to anything earlier. If you want to give it a quick try use the Fedora Core 3 rpm at http://home.austin.rr.com/prinz/magic-7.3.84-1.ejp.fc3.i386.rpm which is signed with my public key http://home.austin.rr.com/prinz/ejprinz.txt There is nothing to port for Fedora Core 3 because 7.3 builds out of the box. Best regards, and good luck, Erwin Prinz From f.mardini at gmail.com Sat May 14 15:45:50 2005 From: f.mardini at gmail.com (Fouad Mardini) Date: Thu Oct 30 14:33:01 2008 Subject: [Magic-dev] Re: supported Magic platforms In-Reply-To: <200505131600.j4DG06GY041082@vlsi.csl.cornell.edu> References: <200505131600.j4DG06GY041082@vlsi.csl.cornell.edu> Message-ID: <4020f8470505140545539490be@mail.gmail.com> Make sure you have the gcc readline library and the x11 development libraries. Also tcl won't hurt. Hope it helps! -fouad > Message: 3 > > What platforms is Magic typically compiled on? > I have Fedora 3 and get build errors for Magic 6.5 and 7. I have followed > the README instructions. On Magic 7 I get build errors involving gcc's lack > of support for the varargs functions. Gcc now supports only stdarg, and > some of the source use incompatible varargs function calls. On magic 6.5, I > get a redefinition error for wchar_t. This problem kind of seems like a gcc > issue, since the conflicting files seem to be in the gcc libraries. > > Any help is appreciated. > > Is there a need for a Fedora port person? I don't have much time, but maybe > I can help. > > Thanks > > Marcus Escobosa > > ------------------------------ > > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev > > End of magic-dev Digest, Vol 11, Issue 3 > **************************************** > From sondeen at ISI.EDU Fri May 13 12:08:51 2005 From: sondeen at ISI.EDU (Jeff Sondeen) Date: Thu Oct 30 14:33:01 2008 Subject: [Magic-dev] supported Magic platforms In-Reply-To: References: Message-ID: <17028.60723.624612.33140@vapor.isi.edu> the Tcl version of magic-7.3.83 built fine on a standard FC3 after make clean ./configure --with-tcl=/usr/lib --with-tk=/usr/lib --with-tclincls=/usr/include --with-tkincls=/usr/include --with-tcllibs=/usr/lib --with-tklibs=/usr/lib --pre fix=/home/sondeen/linux/install make make install-tcl /jeff Marcus Escobosa writes: > What platforms is Magic typically compiled on? > I have Fedora 3 and get build errors for Magic 6.5 and 7. I have followed > the README instructions. On Magic 7 I get build errors involving gcc's lack > of support for the varargs functions. Gcc now supports only stdarg, and > some of the source use incompatible varargs function calls. On magic 6.5, I > get a redefinition error for wchar_t. This problem kind of seems like a gcc > issue, since the conflicting files seem to be in the gcc libraries. > > Any help is appreciated. > > Is there a need for a Fedora port person? I don't have much time, but maybe > I can help. > > Thanks > > Marcus Escobosa > > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev From fang at csl.cornell.edu Sat May 14 18:07:30 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:01 2008 Subject: [Magic-dev] supported Magic platforms In-Reply-To: <4284CF4F.4030908@opencircuitdesign.com> Message-ID: <20050514165654.V7324-100000@shannon.csl.cornell.edu> > Magic versions prior to 7.0 were not developed on Linux and need quite > a bit of work to port---effectively, version 7.1 is the Linux port of > 6.5 plus other fixes and improvements. However, gcc-3 breaks all > versions except 7.2 and 7.3, in which I changed the varargs code. > Either 1) get and install gcc-2.95 (always a useful idea, since gcc-3 > breaks a lot of applications), or 2) get magic 7.3 from my website > at http://bach.ece.jhu.edu/~tim/programs/magic/. For those who are feeling nostalgic for 7.1, I have a patch pending for 7.1 (http://www.csl.cornell.edu/~fang/sw/magic-7.1-osx.html) that took care of varargs and other minor portability issues, and compiles and runs with {gcc-3.x, 4.0} on {FreeBSD (4.3), Mac OS X (10.3)}. It'd be nice to have a final 7.1.x release that's 'stable' on all popular platforms and compilers before leaving it in the dust. And yes, we intend to migrate to 7.3 eventually. > Versions 7.2 and 7.3 have been regularly compiled and tested on > Debian, RedHat, FC2, FC3, and FC2 on an AMD Opteron (64 bit). It is > somewhat less often tested on other systems, but should compile and > run on most any UNIX-like OS, including Cygwin. Both also compile on Mac OS X, last time I checked. Cheers. David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- *gag* work in progress From mika at async.caltech.edu Sat May 14 13:27:24 2005 From: mika at async.caltech.edu (Mika Nystroem) Date: Thu Oct 30 14:33:01 2008 Subject: [Magic-dev] Re: supported Magic platforms In-Reply-To: Your message of "Sat, 14 May 2005 14:45:50 +0200." <4020f8470505140545539490be@mail.gmail.com> Message-ID: <200505141927.j4EJROLv078783@camembert.async.caltech.edu> Hmm, I was just reading the code, trying to install the latest Magic on FreeBSD-4.11, and I noticed that Magic comes with its own copy of readline 4.3, so you shouldn't need to provide it yourself. Unfortunately, compiling on my system, it sees that I have readline installed (default with 4.11 I think), so it tries to use the system readline, but it's older, and missing rl_filename_completion_function, so the compile fails. Not a difficult to thing to fix, but still. I also wonder how well it'll deal with tcl/tk on FreeBSD, which aren't installed the default way (as this would permit only one version to be installed---I remember this used to be a nightmare with tcl/tk, when certain programs would require an older version and others a newer, and you tried to get everything to work on a single system!) But I'm not there yet. Mika Fouad Mardini writes: >Make sure you have the gcc readline library and the x11 development >libraries. Also tcl won't hurt. Hope it helps! > >-fouad > > >> Message: 3 >> >> What platforms is Magic typically compiled on? >> I have Fedora 3 and get build errors for Magic 6.5 and 7. I have followed >> the README instructions. On Magic 7 I get build errors involving gcc's lack >> of support for the varargs functions. Gcc now supports only stdarg, and >> some of the source use incompatible varargs function calls. On magic 6.5, I >> get a redefinition error for wchar_t. This problem kind of seems like a gcc >> issue, since the conflicting files seem to be in the gcc libraries. >> >> Any help is appreciated. >> >> Is there a need for a Fedora port person? I don't have much time, but maybe >> I can help. >> >> Thanks >> >> Marcus Escobosa >> >> ------------------------------ >> >> _______________________________________________ >> magic-dev mailing list >> magic-dev@vlsi.cornell.edu >> http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev >> >> End of magic-dev Digest, Vol 11, Issue 3 >> **************************************** >> > >_______________________________________________ >magic-dev mailing list >magic-dev@vlsi.cornell.edu >http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev From fang at csl.cornell.edu Mon May 16 13:26:21 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:01 2008 Subject: [Magic-dev] Re: supported Magic platforms In-Reply-To: <200505141927.j4EJROLv078783@camembert.async.caltech.edu> Message-ID: <20050516122048.L21714-100000@shannon.csl.cornell.edu> Hi, According to the headers I've checked, the 'completion_function' methods were prefixed with "rl_" sometime between 4.1 and 4.2. > Hmm, I was just reading the code, trying to install the latest Magic > on FreeBSD-4.11, and I noticed that Magic comes with its own copy > of readline 4.3, so you shouldn't need to provide it yourself. > Unfortunately, compiling on my system, it sees that I have readline > installed (default with 4.11 I think), so it tries to use the system > readline, but it's older, and missing rl_filename_completion_function, > so the compile fails. Not a difficult to thing to fix, but still. I've found that the following patchlet takes care of readline portability, whether it's version 4.x or 5.x. -------------% snip %-------------- -#ifdef READLINE_4_DOT_2_PLUS +#if defined(READLINE_4_DOT_2_PLUS) || (RL_VERSION_MAJOR >= 5) || (RL_VERSION_MAJOR == 4 && RL_VERSION_MINOR >= 2) #define filename_completion_function rl_filename_completion_function #define username_completion_function rl_username_completion_function #endif -------------% snip %-------------- Incidentally, no problems with readline-5.0 so far. David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- *gag* work in progress From ram_krec at rediffmail.com Tue May 17 05:15:02 2005 From: ram_krec at rediffmail.com (Ramakrishnan Krishnan) Date: Thu Oct 30 14:33:03 2008 Subject: [Magic-dev] Extraction of resistance and capacitance? Message-ID: <20050517041502.4048.qmail@webmail35.rediffmail.com> Hi all, I have few doubts regarding the extraction of resistance and capacitance in MAGIC. Few questions regarding them are 1. How is AD,AS,PD,PS calculated from the .EXT file and put in .SP file? 2. The capacitance values listed for a node in the .EXT file is extracted to .SP file and shows the caps between the node and ground. What happened to the resistance of the node ? For example in the follwoing .SP file and .EXT file, the 2 caps C0 and C1 for o1 and vdd are listed in the .SP file while what happens to the resistances of the nodes o1,in etc in the .SP file while neing extracted from .EXT? .ext file ---------- timestamp 1115769301 version 5.0 tech mmi07 scale 1000 1 1 resistclasses 115 115 115 115 115 115 115 node "gnd" 2 570 406 55 ndif 0 0 3848 53 0 0 0 0 0 0 0 0 0 0 node "gnd" 2 621 56 54 ndif 0 0 4145 58 0 0 0 0 0 0 0 0 0 0 node "out" 3 1115 449 55 ndif 0 0 9576 102 0 0 0 0 0 0 0 0 0 0 node "vdd" 3 1018 406 241 pdif 0 0 8272 94 0 0 0 0 0 0 0 0 0 0 node "vdd" 3 1086 56 240 pdif 0 0 8656 100 0 0 0 0 0 0 0 0 0 0 node "o1" 8 2210 99 54 ndif 1961 45 13360 163 0 0 0 0 0 0 0 0 0 0 node "in" 5 948 47 183 poly 1961 45 2824 48 0 0 0 0 0 0 0 0 0 0 fet nfet 442 55 442 55 700 214 "GND!" "o1" 14 0 "gnd" 100 0 "out" 100 0 fet nfet 92 54 92 54 700 214 "GND!" "in" 14 0 "gnd" 100 0 "o1" 100 0 fet pfet 442 241 442 241 2100 614 "Vdd!" "o1" 14 0 "vdd" 300 0 "out" 300 0 fet pfet 92 240 92 240 2100 614 "Vdd!" "in" 14 0 "vdd" 300 0 "o1" 300 0 .sp file --------- * HSPICE file created from test2.ext - technology: mmi07 * * Header file for an ASIC circuit HSPICE run * .option post .option post_version=9007 $ mmi's nst program require this .option ACCT=1 BRIEF=1 .option NUMDGT=8 MEASDGT=8 $ for output printing .option ACCURATE $ this is for transient analysis only * VVDD Vdd 0 1.00 Vin in 0 PWL 0.01NS 0.00V 1.00NS 0.00V 1.01NS 1.00V 2.00NS 1.00V + 2.01NS 0.00V 3.00NS 0.00V 3.01NS 1.00V 4.00NS 1.00V + 4.01NS 0.00V 5.00NS 0.00V 5.01NS 1.00V 6.00NS 1.00V + 6.01NS 0.00V 7.00NS 0.00V 7.01NS 1.00V 8.00NS 1.00V .TRANS 0.1NS 8.00NS * HSPICE file created from test2.ext - technology: mmi07 .option scale=0.01u m0 o1 in vdd Vdd pch w=300 l=7 + ad=13360 pd=163 as=16928 ps=194 m1 out o1 vdd Vdd pch w=300 l=7 + ad=9576 pd=102 as=0 ps=0 m2 o1 in gnd GND nch w=100 l=7 + ad=1961 pd=45 as=0 ps=0 m3 out o1 gnd GND nch w=100 l=7 + ad=0 pd=0 as=0 ps=0 C0 vdd GND 2.1fF C1 o1 GND 2.2fF ** hspice subcircuit dictionary * * Tail file for an ASIC circuit HSPICE run * .protect .LIB '/home/users2/kyusun/tool/model/libcmos007ucb.sp' CMOS1 .unprotect * .end Thanks in advance. Regards, Ramki.K Ramakrishnan Krishnan, Graduate Student, Dept of Electrical Engg, Pennsylvania State University,University Park, State College, PA 16801. Ph : 001-814-237-4538 Email : ruk142@psu.edu ram_krec@yahoo.com-------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050517/30547054/attachment.html From fang at csl.cornell.edu Tue May 17 13:52:09 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:03 2008 Subject: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X Message-ID: <20050517123916.W29481-100000@shannon.csl.cornell.edu> Hi all, I've discovered that a .magic file sitting in one's home directory can break the UNIX 'file' command which is frequently used to check the contents of libraries during compiles/builds. (Incidentally, this isn't mentioned in the FILES section of the 'file' man pages I've checked.) Those of you who use fink (http://fink.sourceforge.net/) on OS X may encounter problems building packages with shared libraries because the builds depend on a working 'file' command, somewhere during linking. (You'll see a verbose warning about libraries missing functionality, and only static libraries being generated -- then later, death when it can't mv a missing .dylib.) I suspect that this may affect other variants of 'file' on other *nix,*BSD platforms, but I haven't confirmed. If your 'file' command returns: % file file: could not find any magic files! then you have a problem. The obvious workaround of course, is to move .magic out of the way during such compiles. Has this been a known problem? Perhaps someone with more knowledge on the subject could offer a better solution? David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- *gag* work in progress From ram_krec at rediffmail.com Tue May 17 18:04:21 2005 From: ram_krec at rediffmail.com (Ramakrishnan Krishnan) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] Ectraction of resistance and capacitance? Message-ID: <20050517170421.13368.qmail@webmail25.rediffmail.com> Hi all, I have few doubts regarding the extraction of resistance and capacitance in MAGIC. Few questions regarding them are 1. How is AD,AS,PD,PS calculated from the .EXT file and put in .SP file? 2. The capacitance values listed for a node in the .EXT file is extracted to .SP file and shows the caps between the node and ground. What happened to the resistance of the node ? For example in the follwoing .SP file and .EXT file, the 2 caps C0 and C1 for o1 and vdd are listed in the .SP file while what happens to the resistances of the nodes o1,in etc in the .SP file while neing extracted from .EXT? .ext file ---------- timestamp 1115769301 version 5.0 tech mmi07 scale 1000 1 1 resistclasses 115 115 115 115 115 115 115 node "gnd" 2 570 406 55 ndif 0 0 3848 53 0 0 0 0 0 0 0 0 0 0 node "gnd" 2 621 56 54 ndif 0 0 4145 58 0 0 0 0 0 0 0 0 0 0 node "out" 3 1115 449 55 ndif 0 0 9576 102 0 0 0 0 0 0 0 0 0 0 node "vdd" 3 1018 406 241 pdif 0 0 8272 94 0 0 0 0 0 0 0 0 0 0 node "vdd" 3 1086 56 240 pdif 0 0 8656 100 0 0 0 0 0 0 0 0 0 0 node "o1" 8 2210 99 54 ndif 1961 45 13360 163 0 0 0 0 0 0 0 0 0 0 node "in" 5 948 47 183 poly 1961 45 2824 48 0 0 0 0 0 0 0 0 0 0 fet nfet 442 55 442 55 700 214 "GND!" "o1" 14 0 "gnd" 100 0 "out" 100 0 fet nfet 92 54 92 54 700 214 "GND!" "in" 14 0 "gnd" 100 0 "o1" 100 0 fet pfet 442 241 442 241 2100 614 "Vdd!" "o1" 14 0 "vdd" 300 0 "out" 300 0 fet pfet 92 240 92 240 2100 614 "Vdd!" "in" 14 0 "vdd" 300 0 "o1" 300 0 .sp file --------- * HSPICE file created from test2.ext - technology: mmi07 * * Header file for an ASIC circuit HSPICE run * .option post .option post_version=9007 $ mmi's nst program require this .option ACCT=1 BRIEF=1 .option NUMDGT=8 MEASDGT=8 $ for output printing .option ACCURATE $ this is for transient analysis only * VVDD Vdd 0 1.00 Vin in 0 PWL 0.01NS 0.00V 1.00NS 0.00V 1.01NS 1.00V 2.00NS 1.00V + 2.01NS 0.00V 3.00NS 0.00V 3.01NS 1.00V 4.00NS 1.00V + 4.01NS 0.00V 5.00NS 0.00V 5.01NS 1.00V 6.00NS 1.00V + 6.01NS 0.00V 7.00NS 0.00V 7.01NS 1.00V 8.00NS 1.00V .TRANS 0.1NS 8.00NS * HSPICE file created from test2.ext - technology: mmi07 .option scale=0.01u m0 o1 in vdd Vdd pch w=300 l=7 + ad=13360 pd=163 as=16928 ps=194 m1 out o1 vdd Vdd pch w=300 l=7 + ad=9576 pd=102 as=0 ps=0 m2 o1 in gnd GND nch w=100 l=7 + ad=1961 pd=45 as=0 ps=0 m3 out o1 gnd GND nch w=100 l=7 + ad=0 pd=0 as=0 ps=0 C0 vdd GND 2.1fF C1 o1 GND 2.2fF ** hspice subcircuit dictionary * * Tail file for an ASIC circuit HSPICE run * .protect .LIB '/home/users2/kyusun/tool/model/libcmos007ucb.sp' CMOS1 .unprotect * .end Thanks in advance. Regards, Ramki.K Ramakrishnan Krishnan, Graduate Student, Dept of Electrical Engg, Pennsylvania State University,University Park, State College, PA 16801. Ph : 001-814-237-4538 Email : ruk142@psu.edu ram_krec@yahoo.com-------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050517/62fb4aa3/attachment.html From spaceborne_calin at yahoo.com Wed May 18 19:30:14 2005 From: spaceborne_calin at yahoo.com (Spaceborne Calin) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X In-Reply-To: <20050517123916.W29481-100000@shannon.csl.cornell.edu> Message-ID: <20050518163014.67162.qmail@web53901.mail.yahoo.com> --- David Fang a ?crit : > Hi all, > I've discovered that a .magic file sitting in one's home directory > can break the UNIX 'file' command which is frequently used to check > the > contents of libraries during compiles/builds. (Incidentally, this > isn't > mentioned in the FILES section of the 'file' man pages I've checked.) > Those of you who use fink (http://fink.sourceforge.net/) on OS X may > encounter problems building packages with shared libraries because > the > builds depend on a working 'file' command, somewhere during linking. > (You'll see a verbose warning about libraries missing functionality, > and > only static libraries being generated -- then later, death when it > can't > mv a missing .dylib.) > I suspect that this may affect other variants of 'file' on other > *nix,*BSD platforms, but I haven't confirmed. If your 'file' command > returns: > This is the first time i hear about it. Since is not documented in file man page on OSX it's a bug in file on OSX. On linux I never had that problem. I checked on internet for other systems and at least OpenBSD, HP-UX, IRIX, Solaris don't have the problem that you describe. > % file > file: could not find any magic files! > This is a bug. file on unix systems reads /etc/magic not ~/.magic > then you have a problem. The obvious workaround of course, is to > move > .magic out of the way during such compiles. Has this been a known > problem? Perhaps someone with more knowledge on the subject could > offer a > better solution? > This has never been a problem. I know magic from about 5 years and never heard of such a problem. Sidenote: maybe it's an undocumented behaviour if it doesn't have a /etc/magic file to look in home directory for a ~/.magic file. Do you have a /etc/magic file ? Calin _____________________________________________________________________________ D?couvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vid?os ! Cr?ez votre Yahoo! Mail sur http://fr.mail.yahoo.com From fang at csl.cornell.edu Wed May 18 14:28:35 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X In-Reply-To: <20050518163014.67162.qmail@web53901.mail.yahoo.com> Message-ID: <20050518130828.T37631-100000@shannon.csl.cornell.edu> Hi Calin, > This is the first time i hear about it. Since is not documented in file > man page on OSX it's a bug in file on OSX. Or just missing documentation. > On linux I never had that problem. I checked on internet for other > systems and at least OpenBSD, HP-UX, IRIX, Solaris don't have the > problem that you describe. Well not *every* unix variant is structured the same way. Mac OS X 10.4 (darwin 8) was derived from FreeBSD 5, but not every aspect was mirrored. > > % file > > file: could not find any magic files! > This is a bug. file on unix systems reads /etc/magic not ~/.magic According to my man file: FILES /usr/share/file/magic.mgc Default compiled list of magic numbers /usr/share/file/magic Default list of magic numbers /usr/share/file/magic.mime.mgc Default compiled list of magic numbers, used to output mime types when the -i option is specified. /usr/share/file/magic.mime Default list of magic numbers, used to output mime types when the -i option is specified. /etc/magic Local additions to magic wisdom. There is no /etc/magic on my system (10.4) nor on 10.3. It's merely optional for local extensions. One has to create it and put custom files there. No mention of $HOME/.magic, but my *observation* is that it somehow overrides the other file-magic paths. Even an empty .magic file breaks file. % ls -l /usr/share/file total 5104 -rw-r--r-- 1 root wheel 358659 Mar 20 19:03 magic -rw-r--r-- 1 root wheel 2100032 Mar 20 19:03 magic.mgc -rw-r--r-- 1 root wheel 30287 Mar 20 19:03 magic.mime -rw-r--r-- 1 root wheel 115104 Mar 20 19:03 magic.mime.mgc > > then you have a problem. The obvious workaround of course, is to > > move .magic out of the way during such compiles. Has this been a known > > problem? Perhaps someone with more knowledge on the subject could > > offer a better solution? > > This has never been a problem. I know magic from about 5 years and > never heard of such a problem. Tried using it on Mac OS X? :) I guess the conclusion is that other unices' `file' command just doesn't use $HOME/.magic, it may be as simple as that. Perhaps I'll poke around the Darwin newsgroups or look at the source myself. > Sidenote: maybe it's an undocumented behaviour if it doesn't have a > /etc/magic file to look in home directory for a ~/.magic file. > Do you have a /etc/magic file ? My feeling is that it's just plain undocumented. Thanks for the feedback. David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- *gag* work in progress From philippe at alpha.ece.jhu.edu Wed May 18 14:33:25 2005 From: philippe at alpha.ece.jhu.edu (Philippe Pouliquen) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X In-Reply-To: <20050517123916.W29481-100000@shannon.csl.cornell.edu> References: <20050517123916.W29481-100000@shannon.csl.cornell.edu> Message-ID: <20050518132316.P63502@alpha.ece.jhu.edu> Hi David, > I've discovered that a .magic file sitting in one's home directory can > break the UNIX 'file' command which is frequently used to check the > contents of libraries during compiles/builds. Yep, this is a known issue. The work-around is to define an alias for the 'file' command. I have the following line in my .bashrc (because I use bash as my shell): alias file="/usr/bin/file -m /usr/share/misc/magic" You may need to customize the path for your own environment. Perhaps Tim Edwards could add a "feature" so that Magic looks for .magic or .magicrc, that way we wouldn't need to worry about the 'file' command, while keeping things backwards compatible. Philippe Pouliquen The Johns Hopkins University From fang at csl.cornell.edu Wed May 18 14:45:18 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X In-Reply-To: <20050518132316.P63502@alpha.ece.jhu.edu> Message-ID: <20050518134201.I37631-100000@shannon.csl.cornell.edu> Philippe, Ah, excellent, thanks for the suggestion. I will give this a try. > > I've discovered that a .magic file sitting in one's home directory can > > break the UNIX 'file' command which is frequently used to check the > > contents of libraries during compiles/builds. > > Yep, this is a known issue. The work-around is to define an alias for the > 'file' command. I have the following line in my .bashrc (because I use > bash as my shell): > > alias file="/usr/bin/file -m /usr/share/misc/magic" > > You may need to customize the path for your own environment. > > Perhaps Tim Edwards could add a "feature" so that Magic looks for .magic > or .magicrc, that way we wouldn't need to worry about the 'file' command, > while keeping things backwards compatible. I vote for adding .magicrc, but also keeping around .magic as a secondary place to search (perhaps issue a warning at the prompt?). David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- *gag* work in progress From sondeen at ISI.EDU Thu May 19 13:01:29 2005 From: sondeen at ISI.EDU (Jeff Sondeen) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X In-Reply-To: <20050518163014.67162.qmail@web53901.mail.yahoo.com> References: <20050517123916.W29481-100000@shannon.csl.cornell.edu> <20050518163014.67162.qmail@web53901.mail.yahoo.com> Message-ID: <17036.57993.596498.348266@vapor.isi.edu> i'll add 2 cents to show that fedora3 /usr/ucb/file first looks at ~/.magic then the other locations... % strace file somefile ... stat64("/nfs/div1/sondeen/.magic", 0xbfffd7b0) = -1 ENOENT (No such file or directory) open("/usr/share/magic.mgc", O_RDONLY|O_LARGEFILE) = 3 /jeff Spaceborne Calin writes: > --- David Fang a ?crit : > > > Hi all, > > I've discovered that a .magic file sitting in one's home directory > > can break the UNIX 'file' command which is frequently used to check > > the > > contents of libraries during compiles/builds. (Incidentally, this > > isn't > > mentioned in the FILES section of the 'file' man pages I've checked.) > > Those of you who use fink (http://fink.sourceforge.net/) on OS X may > > encounter problems building packages with shared libraries because > > the > > builds depend on a working 'file' command, somewhere during linking. > > (You'll see a verbose warning about libraries missing functionality, > > and > > only static libraries being generated -- then later, death when it > > can't > > mv a missing .dylib.) > > I suspect that this may affect other variants of 'file' on other > > *nix,*BSD platforms, but I haven't confirmed. If your 'file' command > > returns: > > > > This is the first time i hear about it. Since is not documented in file > man > page on OSX it's a bug in file on OSX. > > On linux I never had that problem. I checked on internet for other > systems > and at least OpenBSD, HP-UX, IRIX, Solaris don't have the problem that > > you describe. > > > > % file > > file: could not find any magic files! > > > > This is a bug. file on unix systems reads /etc/magic not ~/.magic > > > then you have a problem. The obvious workaround of course, is to > > move > > .magic out of the way during such compiles. Has this been a known > > problem? Perhaps someone with more knowledge on the subject could > > offer a > > better solution? > > > > This has never been a problem. I know magic from about 5 years and > never > heard of such a problem. > > Sidenote: maybe it's an undocumented behaviour if it doesn't have a > /etc/magic file to look in home directory for a ~/.magic file. > Do you have a /etc/magic file ? > > Calin > > > > > > > _____________________________________________________________________________ > D?couvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vid?os ! > Cr?ez votre Yahoo! Mail sur http://fr.mail.yahoo.com > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev From tim at opencircuitdesign.com Thu May 19 16:02:45 2005 From: tim at opencircuitdesign.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X In-Reply-To: <20050518134201.I37631-100000@shannon.csl.cornell.edu> References: <20050518134201.I37631-100000@shannon.csl.cornell.edu> Message-ID: <428D0D05.6020109@opencircuitdesign.com> >> Perhaps Tim Edwards could add a "feature" so that Magic looks for .magic >> or .magicrc, that way we wouldn't need to worry about the 'file' command, >> while keeping things backwards compatible. > I vote for adding .magicrc, but also keeping around .magic as > a secondary place to search (perhaps issue a warning at the prompt?). That was my thought, too. Will have to wait for the Jazz tapeout next week, though. The proper procedure would be to change ".magic" to ".magicrc", and to check for ".magic" if ".magicrc" can't be found. If the change is not in the distribution in a couple of weeks, someone please send me a reminder. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From Mark.Martin at jhuapl.edu Fri May 20 11:10:57 2005 From: Mark.Martin at jhuapl.edu (Martin, Mark) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X Message-ID: <7E1D82EADE01E542AA57E940D38FD78D02F11D89@aplesliberty.dom1.jhuapl.edu> I think I first ran into this under RH linux 9.0. My solution was to set up an environmental variable to for file to look at right place. For my RH 9.0 system I have the following in my .bash_profile MAGIC=/usr/share/magic . . . export ... MAGIC ... - Mark > -----Original Message----- > From: magic-dev-bounces@csl.cornell.edu > [mailto:magic-dev-bounces@csl.cornell.edu] On Behalf Of Jeff Sondeen > Sent: Thursday, May 19, 2005 3:01 PM > To: Spaceborne Calin > Cc: magic-dev@csl.cornell.edu > Subject: Re: [Magic-dev] ~/.magic breaks UNIX 'file' command on OS X > > > > i'll add 2 cents to show that fedora3 /usr/ucb/file first > looks at ~/.magic then the other locations... > > % strace file somefile > ... > stat64("/nfs/div1/sondeen/.magic", 0xbfffd7b0) = -1 ENOENT > (No such file or directory) open("/usr/share/magic.mgc", > O_RDONLY|O_LARGEFILE) = 3 > > > /jeff > > Spaceborne Calin writes: > > --- David Fang a ?crit : > > > > > Hi all, > > > I've discovered that a .magic file sitting in one's > home directory > > > can break the UNIX 'file' command which is frequently > used to check > > the > > contents of libraries during > compiles/builds. (Incidentally, this > > isn't > > > mentioned in the FILES section of the 'file' man pages I've > checked.) > > Those of you who use fink > (http://fink.sourceforge.net/) on OS X may > > encounter > problems building packages with shared libraries because > > > the > > builds depend on a working 'file' command, somewhere > during linking. > > > (You'll see a verbose warning about libraries missing > functionality, > > and > > only static libraries being > generated -- then later, death when it > > can't > > mv a > missing .dylib.) > > > I suspect that this may affect other variants of 'file' on other > > > *nix,*BSD platforms, but I haven't confirmed. If your > 'file' command > > returns: > > > > > > > This is the first time i hear about it. Since is not > documented in file > man > page on OSX it's a bug in file on OSX. > > > > On linux I never had that problem. I checked on internet > for other > systems > and at least OpenBSD, HP-UX, IRIX, > Solaris don't have the problem that > > you describe. > > > > > > > % file > > > file: could not find any magic files! > > > > > > > This is a bug. file on unix systems reads /etc/magic not > ~/.magic > > > then you have a problem. The obvious > workaround of course, is to > > move > > .magic out of the > way during such compiles. Has this been a known > > > problem? Perhaps someone with more knowledge on the subject > could > > offer a > > better solution? > > > > > > > This has never been a problem. I know magic from about 5 > years and > never > heard of such a problem. > > > > Sidenote: maybe it's an undocumented behaviour if it > doesn't have a > /etc/magic file to look in home directory > for a ~/.magic file. > > Do you have a /etc/magic file ? > > > > Calin > > > > > > > > > > > > > > > ______________________________________________________________ > _______________ > > D?couvrez le nouveau Yahoo! Mail : 1 Go d'espace de > stockage pour vos mails, photos et vid?os ! > > Cr?ez votre Yahoo! Mail sur http://fr.mail.yahoo.com > > _______________________________________________ > > magic-dev mailing list > > magic-dev@vlsi.cornell.edu > > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev > > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev > From Ross at futuredevices.com Fri May 27 10:42:19 2005 From: Ross at futuredevices.com (Ross Baker) Date: Thu Oct 30 14:33:04 2008 Subject: [Magic-dev] Magic 7.3.86 - failure to load tclmagic.so Message-ID: <200505270942.19878.Ross@futuredevices.com> Hello, I am trying to test Magic, but I run into a problem right away. Using Suse 9.3 on an AMD64 (in 64-bit mode) I find that calling magic version 86 results in the following message: ------------------------------------------------------------------------------------------------------ error in slave eval: couldn't load file "/usr/local/lib/magic/tcl/tclmagic.so" cannot open shared object file: no such file or directory Main console display active (Tcl8.4.9 / TK8.4.9) ------------------------------------------------------------------------------------------------------ The file is clearly there. Running as root has no effect, so it is not a matter of incorrect permissions. I have switched back and forth between compiling version 74 and 86 -- always with the same result. Version 74 starts up properly, but 86 does not. Is it just me? Any suggestions? Oh, I understand that these versions of magic support non-manhattan drawing. Is non-manhattan parasitic extraction and connectivity working also? Thanks, --Ross Baker From manurastogi at gmail.com Thu Jun 9 14:19:53 2005 From: manurastogi at gmail.com (Manu Rastogi) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] Design Scratch Pad for MAGIC Message-ID: Dear Sir/Madam, I am a Research Engineer with Dhirubhai Ambani Institute of Information and Communication Technology (DA-IICT), India. I am trying to develop a design scratch pad for MAGIC. The design scratch pad would allow the user to copy a small section of the layout from the MAGIC window and paste on the scratch pad for various kinds of analysis. My first problem is that when I select an area and copy in MAGIC how do I paste to my scratch pad. Another is where (which pdf/paper/tutorial) do I read for the inter representation of MAGIC files. Thanking you in anticipation Sincerely Manu Rastogi From tim.edwards at multigig.com Thu Jun 9 13:38:03 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] Design Scratch Pad for MAGIC In-Reply-To: References: Message-ID: <42A89A9B.2090107@opencircuitdesign.com> Dear Manu, > I am trying to develop a design scratch pad for MAGIC. The design > scratch pad would allow the user to copy a small section of the layout > from the MAGIC window and paste on the scratch pad for various kinds > of analysis. My first problem is that when I select an area and copy > in MAGIC how do I paste to my scratch pad. Another is where (which > pdf/paper/tutorial) do I read for the inter representation of MAGIC > files. I'm a bit uncertain about what you are trying to do here. Do you want to create an extension to magic that makes use of magic's database and subroutines? Or is this a separate program? If a separate program, you will have to be prepared to take one of magic's output formats, such as GDS, CIF, or its own ".mag" format. You will have to figure out what format is useful to you, and go from there. Writing routines that access magic's internal database is a bit easier with the Tcl version of magic; "ext2spice" and "ext2sim" are written that way. Papers on magic's internal structure are on my website at http://bach.ece.jhu.edu/~tim/programs/magic Click on the "Documentation" button. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From vineet_choudhary at da-iict.org Sat Jun 11 18:27:52 2005 From: vineet_choudhary at da-iict.org (Vineet Choudhary) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] Regarding exttospice command Message-ID: <43153.10.100.56.25.1118491072.squirrel@10.100.56.25> Hello everyone, I am Vineet. I'll come straight to the topic. I would be grateful if anyone can give me any information on how the exttospice command exactly works. I need all the conversion formulae( their nature, use and description) used for converting from .ext to spice. I would be grateful if i can get any information on the same. Thanks Vineet From tim.edwards at multigig.com Sun Jun 12 11:06:55 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] Regarding exttospice command In-Reply-To: <43153.10.100.56.25.1118491072.squirrel@10.100.56.25> References: <43153.10.100.56.25.1118491072.squirrel@10.100.56.25> Message-ID: <42AC6BAF.703@opencircuitdesign.com> Dear Vineet, > I am Vineet. I'll come straight to the topic. I would be > grateful if anyone can give me any information on how the > exttospice command exactly works. I need all the conversion > formulae( their nature, use and description) used for > converting from .ext to spice. I would be grateful if i can > get any information on the same. Some of the more innovative aspects of magic were written up into publicly available documents. But, netlist format conversion was apparently too pedestrian to merit a paper. So you'll be stuck, like the rest of us, figuring out the algorithms from the source code. The source code for "netgen" (available from my website at http://bach.ece.jhu.edu/~tim/programs/magic/magic7_3.html (I haven't yet made a separate web page for it, though I should)) also has code that converts .ext format to an internal format and thence to SPICE. Magic's is a more direct conversion, but plugs into all of magic's internal subroutines, which can be difficult to navigate. Regards, Tim -- +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From chakrart at email.uc.edu Thu Jun 16 16:44:38 2005 From: chakrart at email.uc.edu (Ritochit Chakraborty) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] Resistance Extraction in Magic 7.1. Message-ID: <17298a36.d77c95b.8208f00@mirapoint.uc.edu> Hi All, I am trying to extract resistances using the "extresis" command. Magic splits each node into multiple wire segments and models each of them as a RC network. However, I face the following problem:- The extracted spice and sim files have no internodal coupling capacitances anymore. Is it a common problem, or is it that coupling capacitances lose significance when the nodes are split? From markus_nicke at yahoo.fr Thu Jun 23 13:00:33 2005 From: markus_nicke at yahoo.fr (Markus Nicke) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] Netgen -property check Message-ID: <42BA8841.90908@yahoo.fr> How can I do property checks with netgen? Best Regards, MArkus Nicke ___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com From mmsingh80 at yahoo.co.in Mon Jun 27 16:39:05 2005 From: mmsingh80 at yahoo.co.in (mohan singh) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] regarding magic cad comaptibility- with fedora core 3 Message-ID: <20050627143905.4735.qmail@web8601.mail.in.yahoo.com> sir, i am working in bellary engg college as instructor . we are trying to work with magic cad with fedora core 3 . but we are getting somany errors while installing. is it because of incompatible gcc and tcl/tk?? let us know what is the reason. thanking yu , mohan singh __________________________________________________________ How much free photo storage do you get? Store your friends 'n family snaps for FREE with Yahoo! Photos http://in.photos.yahoo.com From tim.edwards at multigig.com Mon Jun 27 09:47:32 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] Netgen -property check In-Reply-To: <42BA8841.90908@yahoo.fr> References: <42BA8841.90908@yahoo.fr> Message-ID: <42C01F94.9020007@opencircuitdesign.com> Dear Markus, > How can I do property checks with netgen? Unfortunately, this was not a part of the original "netgen", and as simple as it is to add (at least for certain formats like SPICE that declare component properties), I have not done so. The "gemini" netlist comparing program (by Carl Ebeling, U. Washington) handles properties. It can be obtained upon request to Carl Ebeling (ebeling@cs.washington.edu). Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From fang at csl.cornell.edu Mon Jun 27 14:14:24 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] regarding magic cad comaptibility- with fedora core 3 In-Reply-To: <20050627143905.4735.qmail@web8601.mail.in.yahoo.com> Message-ID: <20050627131043.M99162-100000@shannon.csl.cornell.edu> > i am working in bellary engg college as instructor . we are trying to > work with magic cad with fedora core 3 . but we are getting somany > errors while installing. is it because of incompatible gcc and > tcl/tk?? Can you tell us which version you're trying to compile? 7.{1,2,3.x}? I assume .2 or .3, because .1 has no Tcl/Tk. What options during configure and make? David Fang From tim.edwards at multigig.com Tue Jun 28 15:23:47 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:05 2008 Subject: [Magic-dev] Re: magic crash In-Reply-To: <7E1D82EADE01E542AA57E940D38FD78D03C2062D@aplesliberty.dom1.jhuapl.edu> References: <7E1D82EADE01E542AA57E940D38FD78D03C2062D@aplesliberty.dom1.jhuapl.edu> Message-ID: <42C1BFE3.2070800@opencircuitdesign.com> Dear Mark, > I have installed magic 7.3.89 and noticed it dies when I try > to open the special netlist tools. Oops, yes, I see that the great graphics backing-store mechanism was not meant to apply to non-layout windows, such as the netlist window, but the code doesn't check what kind of window it is. The fix is to add if (w->w_client != DBWclientID) return; at the top of grtkCreateBackingStore() in graphics/grTkCommon.c (before line 360), or wait for revision 90, which I will post as soon as I figure out the GDS negative-coordinate error that Mike Godfrey has presented me with (I came across the same error when doing our TSMC chip last year, but hadn't encountered an example since then). ---Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim at multigig.com Tue Jun 28 17:28:31 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:06 2008 Subject: [Magic-dev] Re: Update on GDS problem In-Reply-To: <42C1D250.2070404@isl.stanford.edu> References: <42BB21AD.2070700@isl.stanford.edu> <42C1CD12.4020407@opencircuitdesign.com> <42C1D250.2070404@isl.stanford.edu> Message-ID: <42C1DD1F.30708@opencircuitdesign.com> Dear Michael, > This is a little odd. I looked at the GDS (ESD_struct_2_neg.strm) and found > that the MAG record contained 0x41, 0x10. In ASCII this is A\lf. Maybe > the > "correct" interpretation is byte - " ", i.e A - " " = 1. If this is > true the MAG > record calls for a magnification of 1. And, your result makes sense. I ran the GDS file through "streamutils" sf2ascii and got an ascii dump of the file, then looked at the magnification records. Indeed, all of the magnification records call for scale=1.0 except for two instances in the *_neg.strm file, which call for scale=5.0 on a text record. Since transformations are ignored entirely by magic on text labels, it only complains about the scale=1.0 records, which it ignores in favor of the default (1), so the result is the same in any case. However, on our last tapeout I generated an "artifact" cell in Cadence with a copyright text. To get the DRC errors to disappear, I had to save the copyright text at scale=2. This gave me a good example to test GDS scale magnification in magic. I wrote a simple routine to multiply all elements of the transform by a constant factor (GeoScaleTrans()), and processed the magnification record directly. This worked perfectly without any other modifications to the code, amazingly enough. So the end result is that there was never any reason for the prohibition of scale records in the GDS input stream. I still have to disallow non-integer scales, or at least round to the nearest integer. This can potentially be worked around by subdividing magic's internal grid to compensate for fractional magnifications. Anyway, this extension (which I will post as 7.3.90, along with a fix to the backing store code that prevents magic from crashing when you open a non-layout window) verifies that the interpretation of the MAG record is correct. My suspicion about cells getting flipped in the GDS output is that for very large layouts at very tiny scales, some kind of integer overflow occurs. I have corrected some instances of integer overflow as I work with larger and larger layouts, but there are probably pathological cases that have not been caught. The last time I got bad GDS output was on a 5mm x 5mm chip in 0.18um technology. We used a vendor padframe that was off lambda by 0.01um, forcing magic to scale its internal grid by a factor of 9. So in integer units, the top-level cell was huge. Not enough to overflow a 32-bit integer, signed or unsigned, but clearly enough to overflow in some manipulation of the GDS output. The problem forced us to do the final layout assembly in Cadence (ugh), but I came up with a method of including vendor GDS that avoided the problem, so the last chip I could assemble the final GDS entirely in magic. ---Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim at multigig.com Wed Jun 29 14:10:48 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:06 2008 Subject: [Magic-dev] Re: magic-7.3 extraction ... In-Reply-To: <1120070138.9263.83.camel@bartman.ele.uri.edu> References: <200503082315.j28NFS5M010475@khachaturian.tim.linglan.net> <1110566731.24388.1.camel@bartman.ele.uri.edu> <4231F8C5.2030008@opencircuitdesign.com> <1120070138.9263.83.camel@bartman.ele.uri.edu> Message-ID: <42C30048.4000507@opencircuitdesign.com> Dear Alan, > I have been using the latest version of magic7.3 and I have been > extracting (using :ext & :exttospice) with the :exttospice format set to > hspice. When it extracts I get geometries scaled in lambda (which is > what I really want). > > Today I attempted to extract and just happened to notice that the scale > factor was set to 0.01u ?? The device geometries were very large and > this was the correct scale factor. I could not figure out what was > happening or what to change so I exited magic, restarted it, reset the > extraction parameters and it was back to scaling by 0.3 ... There is a line in the .ext file "scale ", where is the item of interest. The value is interpreted as "units per lambda" linear scaling for all lengths in the extract file. The ".option scale" line in the hspice deck is effectively this number divided by 100. The original number comes from the techfile, section "extract", for lines "lambda ". For my 0.18um tech files, I have in the extract section "lambda 9", corresponding to a scale factor of 0.09u in the hspice deck. I looked at the code and determined that if you read a .ext file that has a different scale factor from the current technology file, the internal scale factor gets set to 1, which would cause the hspice output to show a scale factor of 0.01u. So, for example, if you ran magic on your subm.30 techfile, extracted a circuit, quit magic, brought up magic again with the default techfile, then ran ext2spice, you would get what you saw. I did this because previously, ext2spice ran independently of magic. It could not make use of any information in the technology file, only what was saved in the .ext file. It became the responsibility of the end-user to pass all sorts of cryptic information about the technology to the ext2spice command line. By keeping ext2spice internal to the magic executable, ext2spice can use everything it knows about the technology file. But, if it reads a .ext file and discovers that the values don't match the current technology, then it reverts to a sort of "safe" mode where it assumes nothing about the technology that isn't in the .ext file itself. Part of this process is what causes it to change the scale from lambda to centimicrons. And yes, this behavior isn't documented. Some day I'm going to have to take a sabbatical to get the documentation up to date with the code. . . Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From clint.kelly at gmail.com Mon Jul 4 23:50:02 2005 From: clint.kelly at gmail.com (Clint Kelly) Date: Thu Oct 30 14:33:06 2008 Subject: [Magic-dev] Using magic with STM 90nm process??? Message-ID: <20eabb8805070419507896e514@mail.gmail.com> Hello magic users! I am going to use magic to produce a chip with the 90nm process from STMicroelectronics. http://cmp.imag.fr/products/ic/?p=STCMOS090 I have a couple of questions: - Does anybody have a magic tech file for this process? - Has anybody used magic to make a chip with this process? I would appreciate any response anybody can give me! -Clint From tim.edwards at multigig.com Tue Jul 5 09:33:38 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:06 2008 Subject: [Magic-dev] Using magic with STM 90nm process??? In-Reply-To: <20eabb8805070419507896e514@mail.gmail.com> References: <20eabb8805070419507896e514@mail.gmail.com> Message-ID: <42CAA852.7090905@opencircuitdesign.com> Dear Clint, > I am going to use magic to produce a chip with the 90nm process from > STMicroelectronics. > - Does anybody have a magic tech file for this process? > - Has anybody used magic to make a chip with this process? I have some experience with the TSMC 90nm process, and I can tell you that magic is not well-suited to the increasingly bizarre design rules at 130nm and below. You should not attempt to do any layout in 90nm on magic without some way to run DRC through, say, Calibre. At some point, I'm going to attempt to capture some of the more common contact-surround rules in magic's design rule checker. Other aspects of 90nm rules, like five or six "wide metal spacing" rules per metal layer, can now be captured with magic's DRC, but will slow the DRC down to a crawl. I have done some standard-cell layout for 90nm, but nothing has been fabricated from it yet. In short, designing for 90nm is NOT like designing for 0.5um, and should be done with a great deal of care and caution. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From philippe at alpha.ece.jhu.edu Tue Jul 5 16:02:37 2005 From: philippe at alpha.ece.jhu.edu (Philippe Pouliquen) Date: Thu Oct 30 14:33:06 2008 Subject: [Magic-dev] Using magic with STM 90nm process??? In-Reply-To: <20eabb8805070419507896e514@mail.gmail.com> References: <20eabb8805070419507896e514@mail.gmail.com> Message-ID: <20050705145607.M55990@alpha.ece.jhu.edu> Hi Clint, > I am going to use magic to produce a chip with the 90nm process from > STMicroelectronics. We just got the proprietary info for this process today. I will be creating a Magic techfile for it, but probably not for another month, because I have another chip to finish first. If you need a "professionally" created techfile, I suggest that you talk to Tim Edwards directly, as he may be willing to write the techfile for a nominal fee. (In any event, exchange of Magic techfiles for this process will require some proof that you have an NDA in place with STMicroelectronics, or a silicon broker such as CMP.) Philippe Pouliquen The Johns Hopkins University From graham.petley at vlsitechnology.org Tue Jul 5 15:44:41 2005 From: graham.petley at vlsitechnology.org (Graham Petley) Date: Thu Oct 30 14:33:06 2008 Subject: [Magic-dev] Using magic with STM 90nm process??? In-Reply-To: <20eabb8805070419507896e514@mail.gmail.com> Message-ID: <20050705214441.45430.qmail@web203.biz.mail.re2.yahoo.com> Hi Clint, I have some familiarity with this process and have created a generic 0.13um Magic tech file http://www.vlsitechnology.org/magic/etc/vsc013.tech27 Most of the info I have about the STM 90nm techno is secret, so can't be used to make a public Magic tech file. If you know of anything that is open, then I could help you. Best regards, Graham Petley --- Clint Kelly wrote: > Hello magic users! > > I am going to use magic to produce a chip with the 90nm process from > > STMicroelectronics. > > http://cmp.imag.fr/products/ic/?p=STCMOS090 > > I have a couple of questions: > > - Does anybody have a magic tech file for this process? > > - Has anybody used magic to make a chip with this process? > > I would appreciate any response anybody can give me! > > -Clint > > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev > Graham Petley ASIC Specialist and Consulting Engineer 96 Bridge Street, Mosta MST08, Malta Phone +356-21-413-699, Mobile +356-99-224-109 http://www.vlsitechnology.org From tim at multigig.com Wed Jul 6 11:00:28 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:06 2008 Subject: [Magic-dev] Using magic with STM 90nm process??? In-Reply-To: <20eabb8805070606037eb92fb7@mail.gmail.com> References: <20eabb8805070419507896e514@mail.gmail.com> <42CAA852.7090905@opencircuitdesign.com> <20eabb8805070606037eb92fb7@mail.gmail.com> Message-ID: <42CC0E2C.1000501@opencircuitdesign.com> Dear Clint, > Do you think it would be possible to change the design rules for a > 90nm process to make them slightly more conservative and therefore > make them easier for magic to check? Yes, absolutely. I started out this way with the TSMC 90nm tech file, but I ended up working on a project where I was tweaking the layout of a vendor-made standard cell, so to properly read in the vendor GDS, I needed to be on minimum grid with liberal design rules. Oddly, the vendor GDS was drawn on rules more liberal than the TSMC DRC document allows---I don't know how they get away with that. The TSMC documentation had a slew of "absolute" rules and another slew of "recommended" rules. I found, in general, that if I enforced the more conservative "recommended" ruleset, it was much easier to get magic's design rule checker to match. However, there are still complicated rules like "spacing A to B must be X except when A is closer than distance Y to layer C", etc., etc. I know of a way to capture most of these rules using a generic form of the method I implemented for checking wide-metal-spacing rules, but I haven't coded it yet. I also have come up with a method for detecting violations of spacing rules on catecorner N+/P+ implant layers and other auto-generated mask layers, which tends to be a problem with magic in that these sort of errors should not affect circuit behavior, but vendors will now reject GDS data that contains them---i.e., it becomes increasingly difficult to waive these drc violations, or at least increasingly cumbersome to fill out all the waiver forms. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim at multigig.com Wed Jul 6 11:15:58 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:07 2008 Subject: [Magic-dev] Using magic with STM 90nm process??? In-Reply-To: <42CB536A.7000305@austin.rr.com> References: <20eabb8805070419507896e514@mail.gmail.com> <42CAA852.7090905@opencircuitdesign.com> <42CB536A.7000305@austin.rr.com> Message-ID: <42CC11CE.1030501@opencircuitdesign.com> Dear Erwin, > We have > elected to use Mentor Graphics Calibre to check the design rules, since > we had a Calibre deck available which had been verified with QA cells > (quality assurance). I think it is a major project to code the 90nm > rules in Magic, fabricate suitable QA cells, and then proof the DRC > rules with the QA cells, and make sure the rules check identically to > the decks already available. To start, have a look at the bond pad > design rules... I have done exactly that, and yes, it is a royal pain. However, one can capture 90% of rules in the magic tech file without too much work, and the layout is still much easier in magic than with any other tool (at least, most people seem to think so), particularly if you can work on a lambda grid in magic instead of a minimum-dimension (e.g., 0.1 or 0.01 um) grid. I have managed to do several chips in the last couple of months by using Cadence to generate some of the "p-cells", like bipolar transistors, pads, varactors, copyright text, etc., and importing them into magic using the "gds readonly true" and "gds rescale false" commands that I coded recently. Using this method, the "view" of the subcell in magic is in magic's layers but the GDS of the subcell is copied directly from the vendor GDS into the final GDS file. That lets me do final chip assembly in magic (using TCL scripts, usually). I insist on using Calibre for final DRC but usually I can get magic's DRC to be near-perfect after numerous iterations. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From fox at researchsupport.com Mon Jul 11 16:23:37 2005 From: fox at researchsupport.com (Jon Fox) Date: Thu Oct 30 14:33:07 2008 Subject: [Magic-dev] Postscript plotting and layers Message-ID: <42D2C739.2080002@researchsupport.com> I want to make postscript output for an imagesetter again (10 micron resolution masks) from some stuff I made in Magic and was wondering if magic has a command that lets me hide particular layers/levels. I didn't see this in the docs at /vlsi.cornell.edu/magic/. In the past I've imported CIF generated elsewhere one layer at a time. I see that Tim's pplot has a feature like this as well. -- Jon --- Jon R. Fox Principal Scientist, Research Support Instruments, Inc. Visiting Researcher, Princeton University fox@researchsupport.com tel: 732-329-3700 x 103 fax: 732-329-9200 http://www.rsiprinceton.com/Members/jfox From tim at multigig.com Mon Jul 11 15:39:47 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:07 2008 Subject: [Magic-dev] Postscript plotting and layers In-Reply-To: <42D2C739.2080002@researchsupport.com> References: <42D2C739.2080002@researchsupport.com> Message-ID: <42D2E723.5030502@opencircuitdesign.com> Jon Fox wrote: > I want to make postscript output for an imagesetter again (10 micron > resolution masks) from some stuff I made in Magic and was wondering if > magic has a command that lets me hide particular layers/levels. I > didn't see this in the docs at /vlsi.cornell.edu/magic/. The list of layers to plot can be specified as the 4th argument to the plot command: "plot postscript ". If the 4th argument is omitted, all layers are plotted. I think that the negation operator "~" can be used to specify layers NOT to plot, but I haven't tested it to see if that's true. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From nagaraj11 at rediffmail.com Thu Jul 14 12:33:03 2005 From: nagaraj11 at rediffmail.com (RAJU) Date: Thu Oct 30 14:33:08 2008 Subject: [Magic-dev] Magic - Windows Installation Error!!! Message-ID: <20050714113303.15089.qmail@webmail7.rediffmail.com> ?Hi, I am trying to install Magic 7.2 on my system Windows 2000. I have downloaded Cygwin (file size approx 648MB) with complete modules from ftp://cygwin.dp.ua/pub/mirrors/cygwin/release After installing, when i type Xwin-multiwindow or Xwin_GL-multiwindow, it says command not found. Please help me How Can I get Magic working on my system. Thanks Raju -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050714/d99eeec0/attachment.html From nagaraj11 at rediffmail.com Thu Jul 14 12:38:11 2005 From: nagaraj11 at rediffmail.com (RAJU) Date: Thu Oct 30 14:33:09 2008 Subject: [Magic-dev] Magic - Windows Installation windows Message-ID: <20050714113811.17932.qmail@webmail9.rediffmail.com> Hi, I am trying to install Magic 7.2 on my system Windows 2000. I have downloaded Cygwin (file size approx 648MB) with complete modules from ftp://cygwin.dp.ua/pub/mirrors/cygwin/release After installing, when i type Xwin-multiwindow or Xwin_GL-multiwindow, it says command not found. Please help me How Can I get Magic working on my system. Thanks Raju -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050714/4c74b04a/attachment.html From tim at multigig.com Thu Jul 14 13:56:28 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:09 2008 Subject: [Magic-dev] Magic - Windows Installation Error!!! In-Reply-To: <20050714113303.15089.qmail@webmail7.rediffmail.com> References: <20050714113303.15089.qmail@webmail7.rediffmail.com> Message-ID: <42D6C36C.60101@opencircuitdesign.com> Dear Raju, > After installing, when i type Xwin-multiwindow or Xwin_GL-multiwindow, > it says command not found. I don't know if that's a typo in your email or not, but note that the command is "Xwin -multiwindow", with a space; i.e., the command is "Xwin", and "-multiwindow" is an option passed to it. "Xwin_GL" may be deprecated; I didn't see it in the last version of Cygwin I downloaded. The standard "Xwin" should be capable of handling OpenGL calls. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From codendev at vsnl.com Thu Aug 4 20:00:16 2005 From: codendev at vsnl.com (CODE) Date: Thu Oct 30 14:33:09 2008 Subject: [Magic-dev] C compiler default output... configure: error: C compiler cannot create executables Message-ID: Hi, Iam new to cygwin. However, I got cygwin & magic (magic_win_tcl) working. When I try to install patch of magic-7.2.70 it gives the following error. raju@systemc /usr/local/src/magic-7.2.70 $ ./configure --without-tcl checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking target system type... i686-pc-cygwin checking for gcc... gcc checking for C compiler default output... configure: error: C compiler cannot cr eate executables See `config.log' for more details. My setup details after installing cygwin is enclosed in a text file. Please help me how do I solve this problem, I dont know how to test the C compiler working. Thanks, raju -------------- next part -------------- raju@systemc /usr/local/src/magic-7.2.70 $ ./configure --without-tcl checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking target system type... i686-pc-cygwin checking for gcc... gcc checking for C compiler default output... configure: error: C compiler cannot cr eate executables See `config.log' for more details. ===================================================== $ cygcheck -c Cygwin Package Information Package Version Status _update-info-dir 00272-1 OK alternatives 1.3.20a-1 OK ash 20040127-1 OK aspell 0.50.3-1 OK aspell-de 0.50.2-1 OK autoconf 2.59-2 OK autoconf-devel 2.59-2 OK autoconf-stable 2.13-6 OK autoconf2.1 2.13-1 OK autoconf2.5 2.59-1 OK automake1.9 1.9.5-2 OK base-files 3.4-2 OK base-passwd 2.2-1 OK bash 2.05b-17 OK binutils 20050608-2 OK bzip2 1.0.2-6 OK cgoban 1.9.14-1 OK clear 1.0-1 OK clisp 2.33.1-1 OK coreutils 5.3.0-6 OK crypt 1.1-1 OK ctags 5.5-4 OK curl 7.11.1-1 OK cygrunsrv 1.10-1 OK cygutils 1.2.8-1 OK cygwin 1.5.18-1 OK cygwin-doc 1.4-2 OK cygwin-x-doc 1.0.4-1 OK ddd 3.3.9-1 OK dejagnu 20021217-2 OK diffutils 2.8.7-1 OK editrights 1.01-1 OK emacs 21.2-13 OK emacs-el 21.2-13 OK emacs-X11 21.2-13 OK expat 1.95.8-1 OK expect 20030128-1 OK file 4.12-1 OK fileutils 4.1-3 OK findutils 20041227-1 OK fontconfig 2.2.2-1 OK freeglut 2.2.0-1 OK freetype2 2.1.5-1 OK fvwm 2.4.7-3 OK gawk 3.1.4-3 OK gcc 3.4.4-1 OK gcc-ada 3.4.4-1 OK gcc-core 3.4.4-1 OK gcc-g++ 3.4.4-1 OK gcc-g77 3.4.4-1 OK gcc-gdc 3.4.4-1 OK gcc-gpc 3.3.3-3 OK gcc-java 3.4.4-1 OK gcc-mingw 20040810-1 OK gcc-mingw-ada 20050522-1 OK gcc-mingw-core 20050522-1 OK gcc-mingw-g++ 20050522-1 OK gcc-mingw-g77 20050522-1 OK gcc-mingw-gdc 20050522-1 OK gcc-mingw-gpc 20040810-1 OK gcc-mingw-java 20050522-1 OK gcc-mingw-objc 20050522-1 OK gcc-objc 3.4.4-1 OK gcc-testsuite 3.4.4-1 OK gd 2.0.33-1 OK gdb 20041228-3 OK gdbm 1.8.3-7 OK gettext 0.14.1-1 OK ghostscript 8.15-2 OK ghostscript-base 8.15-2 OK ghostscript-x11 8.15-2 OK glib 1.2.10-2 OK glib2 2.4.8-1 OK glib2-devel 2.4.8-1 OK gnuplot 4.0.0-1 OK grep 2.5.1a-2 OK groff 1.18.1-2 OK gv 3.5.8-2 OK gzip 1.3.5-1 OK lesstif 0.93.94-2 OK libbz2_1 1.0.2-6 OK libfontconfig-devel 2.2.2-1 OK libfontconfig1 2.2.2-1 OK libfreetype2-devel 2.1.5-1 OK libfreetype26 2.1.5-1 OK libgd-devel 2.0.33-1 OK libgd2 2.0.33-1 OK libltdl3 1.5.18-1 OK libtool 1.5b-2 OK libtool-devel 1.5.10-2 OK libtool-stable 1.4.3-3 OK libtool1.5 1.5.18-1 OK libXft 2.1.6-1 OK libXft-devel 2.1.6-1 OK libXft1 1.0.0-1 OK libXft2 2.1.6-1 OK m4 1.4.3-1 OK make 3.80-1 OK nedit 5.5-1 OK openbox 0.99.1-4 OK pcre 4.5-1 OK pcre-doc 4.5-1 OK sed 4.1.4-1 OK tar 1.13.25-7 OK tcltk 20030901-1 OK tcm 2.20-1 OK transfig 3.2.4-2 OK vim 6.3-1 OK WindowMaker 0.90.0-2 OK X-start-menu-icons 1.0.3-2 OK X-startup-scripts 1.0.10-4 OK x2x 1.30-2 OK Xaw3d 1.5D-5 OK xfig 3.2.4-6 OK xfig-lib 3.2.4-6 OK XFree86-lib-compat 4.3.0-2 OK xgraph 12.1-1 OK XmHTML 1.1.7-1 OK xmon 1.5.6-1 OK xorg-x11-base 6.8.2.0-1 OK xorg-x11-bin 6.8.2.0-1 OK xorg-x11-bin-dlls 6.8.2.0-1 OK xorg-x11-bin-lndir 6.8.2.0-1 OK xorg-x11-devel 6.8.2.0-2 OK xorg-x11-etc 6.8.2.0-1 OK xorg-x11-f100 6.8.1.0-3 OK xorg-x11-fcyr 6.8.1.0-2 OK xorg-x11-fenc 6.8.1.0-2 OK xorg-x11-fnts 6.8.1.0-3 OK xorg-x11-fscl 6.8.1.0-2 OK xorg-x11-fsrv 6.8.2.0-1 OK xorg-x11-libs-data 6.8.2.0-1 OK xorg-x11-man-pages 6.8.2.0-1 OK xorg-x11-man-pages-html 6.8.2.0-1 OK xorg-x11-nest 6.8.2.0-2 OK xorg-x11-vfb 6.8.2.0-2 OK xorg-x11-xwin 6.8.2.0-3 OK xorg-x11-xwin-gl 6.8.2.0-3 OK xpdf 3.00-2 OK xterm 202-1 OK xwinclip 1.2.0-1 OK xwinwm 0.0.5-1 OK ==================================================== $ cygcheck -s -v -r Cygwin Configuration Diagnostics Current System Time: Thu Aug 04 18:21:00 2005 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem c:\ORANT\BIN .\ c:\Xilinx\bin\nt c:\BITWARE\ Output from C:\cygwin\bin\id.exe (nontsec) UID: 1000(raju) GID: 513(None) 513(None) 547(Power Users) 545(Users) Output from C:\cygwin\bin\id.exe (ntsec) UID: 1000(raju) GID: 513(None) 513(None) 547(Power Users) 545(Users) SysDir: C:\WINNT\system32 WinDir: C:\WINNT USER = `raju' PWD = `/home/raju' HOME = `/home/raju' MAKE_MODE = `unix' HOMEPATH = `\Documents and Settings\raju' MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man: X11R6/man' APPDATA = `C:\Documents and Settings\raju\Application Data' HOSTNAME = `systemc' TERM = `cygwin' PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 9, GenuineIntel' WINDIR = `C:\WINNT' OLDPWD = `/etc/skel' USERDOMAIN = `SYSTEMC' OS = `Windows_NT' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' OS2LIBPATH = `C:\WINNT\system32\os2\dll;' !:: = `::\' TEMP = `/cygdrive/c/DOCUME~1/raju/LOCALS~1/Temp' COMMONPROGRAMFILES = `C:\Program Files\Common Files' USERNAME = `raju' PROCESSOR_LEVEL = `15' SYSTEMDRIVE = `C:' USERPROFILE = `C:\Documents and Settings\raju' PS1 = `\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = `\\SYSTEMC' PROCESSOR_ARCHITECTURE = `x86' LM_LICENSE_FILE = `D:\license.dat;C:\Modeltech_xe_starter\win32xoem\licens !C: = `C:\cygwin\bin' SHLVL = `1' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' HOMEDRIVE = `C:' PROMPT = `$P$G' COMSPEC = `C:\WINNT\system32\cmd.exe' TMP = `/cygdrive/c/DOCUME~1/raju/LOCALS~1/Temp' SYSTEMROOT = `C:\WINNT' PRINTER = `hp psc 1200 series' CVS_RSH = `/bin/ssh' PROCESSOR_REVISION = `0209' PKG_CONFIG_PATH = `/usr/X11R6/lib/pkgconfig' INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/ usr/autotool/stable/info:' PROGRAMFILES = `C:\Program Files' LMC_HOME = `C:\Xilinx\smartmodel\nt\installed_nt' NUMBER_OF_PROCESSORS = `1' XILINX = `C:\Xilinx' COMPUTERNAME = `SYSTEMC' _ = `/usr/bin/cygcheck' POSIXLY_CORRECT = `1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x00000022 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x00000022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `C:\cygwin' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `C:\cygwin/bin' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `C:\cygwin/lib' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options a: fd N/A N/A c: hd FAT32 9991Mb 75% CP UN d: hd FAT32 9991Mb 75% CP UN DATA e: hd FAT32 9991Mb 52% CP UN BACKUP f: cd N/A N/A . /cygdrive user binmode,cygdrive C:\cygwin / system binmode C:\cygwin/bin /usr/bin system binmode C:\cygwin/lib /usr/lib system binmode . /cygdrive system binmode,cygdrive Found: C:\cygwin\bin\awk.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cpp.exe Found: C:\cygwin\bin\find.exe Found: C:\cygwin\bin\gcc.exe Found: C:\cygwin\bin\gdb.exe Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\mv.exe Found: C:\cygwin\bin\rm.exe Found: C:\cygwin\bin\sed.exe Found: C:\cygwin\bin\sh.exe Found: C:\cygwin\bin\tar.exe 21k 2005/07/14 C:\WINNT\system32\cygintl.dll - os=4.0 img=1.0 sys=4.0 "cygintl.dll" v0.0 ts=2001/6/20 22:39 61k 2005/07/14 C:\WINNT\system32\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2003/12/4 8:33 63k 2005/07/14 C:\WINNT\system32\cygpcre.dll - os=4.0 img=1.0 sys=4.0 21k 2005/07/14 C:\WINNT\system32\cygintl.dll - os=4.0 img=1.0 sys=4.0 "cygintl.dll" v0.0 ts=2001/6/20 22:39 61k 2005/07/14 C:\WINNT\system32\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2003/12/4 8:33 63k 2005/07/14 C:\WINNT\system32\cygpcre.dll - os=4.0 img=1.0 sys=4.0 "cygpcre.dll" v0.0 ts=2003/4/11 14:01 22k 2005/07/14 C:\WINNT\system32\cygintl-1.dll - os=4.0 img=1.0 sys=4.0 "cygintl-1.dll" v0.0 ts=2001/12/13 14:58 991k 2005/07/14 C:\WINNT\system32\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0 "cygiconv-2.dll" v0.0 ts=2004/7/6 23:40 37k 2005/07/14 C:\WINNT\system32\cygintl-2.dll - os=4.0 img=1.0 sys=4.0 "cygintl-2.dll" v0.0 ts=2003/8/11 3:20 54k 2005/07/16 C:\WINNT\system32\cygintl-3.dll - os=4.0 img=1.0 sys=4.0 "cygintl-3.dll" v0.0 ts=2004/7/6 23:21 22k 2005/07/14 C:\WINNT\system32\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0 "cygpopt-0.dll" v0.0 ts=2002/6/9 11:15 62k 2005/07/14 C:\WINNT\system32\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcre-0.dll" v0.0 ts=2003/12/11 22:31 216k 2005/07/29 C:\WINNT\system32\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0 "cygncurses-8.dll" v0.0 ts=2004/10/10 13:55 21k 2005/07/14 C:\WINNT\SYSTEM\cygintl.dll - os=4.0 img=1.0 sys=4.0 "cygintl.dll" v0.0 ts=2001/6/20 22:39 991k 2005/07/14 C:\WINNT\SYSTEM\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0 "cygiconv-2.dll" v0.0 ts=2004/7/6 23:40 22k 2005/07/14 C:\WINNT\SYSTEM\cygintl-1.dll - os=4.0 img=1.0 sys=4.0 "cygintl-1.dll" v0.0 ts=2001/12/13 14:58 37k 2005/07/14 C:\WINNT\SYSTEM\cygintl-2.dll - os=4.0 img=1.0 sys=4.0 "cygintl-2.dll" v0.0 ts=2003/8/11 3:20 61k 2005/07/14 C:\WINNT\SYSTEM\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2003/12/4 8:33 54k 2005/07/16 C:\WINNT\SYSTEM\cygintl-3.dll - os=4.0 img=1.0 sys=4.0 "cygintl-3.dll" v0.0 ts=2004/7/6 23:21 22k 2005/07/14 C:\WINNT\SYSTEM\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0 "cygpopt-0.dll" v0.0 ts=2002/6/9 11:15 62k 2005/07/14 C:\WINNT\SYSTEM\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcre-0.dll" v0.0 ts=2003/12/11 22:31 63k 2005/07/14 C:\WINNT\SYSTEM\cygpcre.dll - os=4.0 img=1.0 sys=4.0 "cygpcre.dll" v0.0 ts=2003/4/11 14:01 7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0 "cygcrypt-0.dll" v0.0 ts=2003/10/19 13:27 617k 2004/03/22 C:\cygwin\bin\cygcurl-2.dll - os=4.0 img=1.0 sys=4.0 "cygcurl-2.dll" v0.0 ts=2004/3/22 21:22 174k 2004/10/14 C:\cygwin\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0 "cygexpat-0.dll" v0.0 ts=2004/10/14 14:04 146k 2004/12/21 C:\cygwin\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0 "cygmagic-1.dll" v0.0 ts=2004/12/21 20:04 135k 2004/09/02 C:\cygwin\bin\cygglib-1-2-0.dll - os=4.0 img=1.0 sys=4.0 "cygglib-1-2-0.dll" v0.0 ts=2004/9/2 23:51 11k 2004/09/02 C:\cygwin\bin\cyggmodule-1-2-0.dll - os=4.0 img=1.0 sys=4.0 "cyggmodule-1-2-0.dll" v0.0 ts=2004/9/2 23:53 10k 2004/09/02 C:\cygwin\bin\cyggthread-1-2-0.dll - os=4.0 img=1.0 sys=4.0 "cyggthread-1-2-0.dll" v0.0 ts=2004/9/2 23:53 55k 2004/09/14 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0 "cygbz2-1.dll" v0.0 ts=2004/9/14 9:46 129k 2004/03/11 C:\cygwin\bin\cygfontconfig-1.dll - os=4.0 img=1.0 sys=4.0 "cygfontconfig-1.dll" v0.0 ts=2004/3/11 5:42 361k 2003/10/25 C:\cygwin\bin\cygfreetype-6.dll - os=4.0 img=1.0 sys=4.0 "cygfreetype-6.dll" v0.0 ts=2003/10/22 9:48 222k 2005/01/13 C:\cygwin\bin\cyggd-2.dll - os=4.0 img=1.0 sys=4.0 "cyggd-2.dll" v0.0 ts=2005/1/13 21:26 41k 2005/06/01 C:\cygwin\bin\cygltdl-3.dll - os=4.0 img=1.0 sys=4.0 "cygltdl-3.dll" v0.0 ts=2005/6/1 11:04 1265k 2005/07/03 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=2005/7/3 6:00 Cygwin DLL version info: DLL version: 1.5.18 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 DLL malloc env: 28 API major: 0 API minor: 132 Shared data: 4 DLL identifier: cygwin1 Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Cygdrive flags: cygdrive flags Cygdrive prefix: cygdrive prefix Cygdrive default prefix: Build date: Sat Jul 2 20:30:04 EDT 2005 Shared id: cygwin1S4 140k 2004/08/06 C:\cygwin\usr\X11R6\bin\cygglut-3.dll - os=4.0 img=1.0 sys=4.0 "cygglut-3.dll" v0.0 ts=2004/8/6 20:13 28k 2004/03/31 C:\cygwin\usr\X11R6\bin\cygDtPrint-1.dll - os=4.0 img=1.0 sys= 4.0 "cygDtPrint-1.dll" v0.0 ts=2004/3/31 9:53 77k 2004/03/31 C:\cygwin\usr\X11R6\bin\cygMrm-2.dll - os=4.0 img=1.0 sys=4.0 "cygMrm-2.dll" v0.0 ts=2004/3/31 9:53 66k 2004/03/31 C:\cygwin\usr\X11R6\bin\cygUil-2.dll - os=4.0 img=1.0 sys=4.0 "cygUil-2.dll" v0.0 ts=2004/3/31 9:53 1294k 2004/03/31 C:\cygwin\usr\X11R6\bin\cygXm-2.dll - os=4.0 img=1.0 sys=4.0 "cygXm-2.dll" v0.0 ts=2004/3/31 9:50 56k 2004/03/11 C:\cygwin\usr\X11R6\bin\cygXft-1.dll - os=4.0 img=1.0 sys=4.0 "cygXft-1.dll" v0.0 ts=2003/11/18 7:12 63k 2004/03/23 C:\cygwin\usr\X11R6\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0 "cygXft-2.dll" v0.0 ts=2004/3/24 3:50 275k 2004/01/13 C:\cygwin\usr\X11R6\bin\cygXaw3d-7.dll - os=4.0 img=1.0 sys=4. 0 "cygXaw3d-7.dll" v0.0 ts=2004/1/14 3:47 282k 2003/10/28 C:\cygwin\usr\X11R6\bin\cygfreetype-9.dll - os=4.0 img=1.0 sys =4.0 "cygfreetype-9.dll" v0.0 ts=2003/10/18 12:14 459k 2004/02/10 C:\cygwin\usr\X11R6\bin\cygXmHTML-0.dll - os=4.0 img=1.0 sys=4 .0 "cygXmHTML-0.dll" v0.0 ts=2004/2/11 1:44 36k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygFS-6.dll - os=4.0 img=1.0 sys=4.0 "cygFS-6.dll" v0.0 ts=2005/2/23 20:04 358k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0 "cygGL-1.dll" v0.0 ts=2005/2/23 20:09 438k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygGLU-1.dll - os=4.0 img=1.0 sys=4.0 "cygGLU-1.dll" v0.0 ts=2005/2/23 20:11 75k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0 "cygICE-6.dll" v0.0 ts=2005/2/23 19:58 1413k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygOSMesa-4.dll - os=4.0 img=1.0 sys=4 .0 "cygOSMesa-4.dll" v0.0 ts=2005/2/23 20:09 30k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0 "cygSM-6.dll" v0.0 ts=2005/2/23 19:58 877k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0 "cygX11-6.dll" v0.0 ts=2005/2/23 19:58 8k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXRes-1.dll - os=4.0 img=1.0 sys=4.0 "cygXRes-1.dll" v0.0 ts=2005/2/23 20:13 27k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXTrap-6.dll - os=4.0 img=1.0 sys=4. 0 "cygXTrap-6.dll" v0.0 ts=2005/2/23 20:13 254k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXaw-6.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-6.dll" v0.0 ts=2005/2/23 20:01 356k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-7.dll" v0.0 ts=2005/2/23 20:02 363k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXaw-8.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-8.dll" v0.0 ts=2005/2/23 20:03 9k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXcomposite-1.dll - os=4.0 img=1.0 s ys=4.0 "cygXcomposite-1.dll" v0.0 ts=2005/2/23 20:14 30k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXcursor-1.dll - os=4.0 img=1.0 sys= 4.0 "cygXcursor-1.dll" v0.0 ts=2005/2/23 20:13 9k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXdamage-1.dll - os=4.0 img=1.0 sys= 4.0 "cygXdamage-1.dll" v0.0 ts=2005/2/23 20:14 7k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXevie-1.dll - os=4.0 img=1.0 sys=4. 0 "cygXevie-1.dll" v0.0 ts=2005/2/23 20:13 49k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0 "cygXext-6.dll" v0.0 ts=2005/2/23 19:58 16k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXfixes-3.dll - os=4.0 img=1.0 sys=4 .0 "cygXfixes-3.dll" v0.0 ts=2005/2/23 20:13 27k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXi-6.dll - os=4.0 img=1.0 sys=4.0 "cygXi-6.dll" v0.0 ts=2005/2/23 20:04 76k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0 "cygXmu-6.dll" v0.0 ts=2005/2/23 20:00 11k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0 "cygXmuu-1.dll" v0.0 ts=2005/2/23 20:00 26k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXp-6.dll - os=4.0 img=1.0 sys=4.0 "cygXp-6.dll" v0.0 ts=2005/2/23 20:01 52k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-4.dll" v0.0 ts=2005/2/23 20:00 12k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXrandr-2.dll - os=4.0 img=1.0 sys=4 .0 "cygXrandr-2.dll" v0.0 ts=2005/2/23 20:13 28k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXrender-1.dll - os=4.0 img=1.0 sys= 4.0 "cygXrender-1.dll" v0.0 ts=2005/2/23 20:12 282k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0 "cygXt-6.dll" v0.0 ts=2005/2/23 19:59 17k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXtst-6.dll - os=4.0 img=1.0 sys=4.0 "cygXtst-6.dll" v0.0 ts=2005/2/23 20:04 243k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygdps-1.dll - os=4.0 img=1.0 sys=4.0 "cygdps-1.dll" v0.0 ts=2005/2/23 20:12 26k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygdpstk-1.dll - os=4.0 img=1.0 sys=4. 0 "cygdpstk-1.dll" v0.0 ts=2005/2/23 20:12 21k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygfontenc-1.dll - os=4.0 img=1.0 sys= 4.0 "cygfontenc-1.dll" v0.0 ts=2005/2/23 20:15 9k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygoldX-6.dll - os=4.0 img=1.0 sys=4.0 "cygoldX-6.dll" v0.0 ts=2005/2/23 19:58 20k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygpsres-1.dll - os=4.0 img=1.0 sys=4. 0 "cygpsres-1.dll" v0.0 ts=2005/2/23 20:12 125k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygxkbfile-1.dll - os=4.0 img=1.0 sys= 4.0 "cygxkbfile-1.dll" v0.0 ts=2005/2/23 20:04 12k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygxkbui-1.dll - os=4.0 img=1.0 sys=4. 0 "cygxkbui-1.dll" v0.0 ts=2005/2/23 20:04 40k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygxrx-6.dll - os=4.0 img=1.0 sys=4.0 "cygxrx-6.dll" v0.0 ts=2005/2/23 20:23 25k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygxrxnest-6.dll - os=4.0 img=1.0 sys= 4.0 "cygxrxnest-6.dll" v0.0 ts=2005/2/23 20:23 No Cygwin services found. Cygwin Package Information Last downloaded files to: E:\magic-BACKUP-1-8-05\cygwin\ftp%3a%2f%2fftp-stud.fht -esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin Last downloaded files from: E:\magic-BACKUP-1-8-05\cygwin\ftp%3a%2f%2fftp-stud.f ht-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin Package Version _update-info-dir 00272-1 alternatives 1.3.20a-1 ash 20040127-1 aspell 0.50.3-1 aspell-de 0.50.2-1 autoconf 2.59-2 autoconf-devel 2.59-2 autoconf-stable 2.13-6 autoconf2.1 2.13-1 autoconf2.5 2.59-1 automake1.9 1.9.5-2 base-files 3.4-2 base-passwd 2.2-1 bash 2.05b-17 binutils 20050608-2 bzip2 1.0.2-6 cgoban 1.9.14-1 clear 1.0-1 clisp 2.33.1-1 coreutils 5.3.0-6 crypt 1.1-1 ctags 5.5-4 curl 7.11.1-1 cygrunsrv 1.10-1 cygutils 1.2.8-1 cygwin 1.5.18-1 cygwin-doc 1.4-2 cygwin-x-doc 1.0.4-1 ddd 3.3.9-1 dejagnu 20021217-2 diffutils 2.8.7-1 editrights 1.01-1 emacs 21.2-13 emacs-el 21.2-13 emacs-X11 21.2-13 expat 1.95.8-1 expect 20030128-1 file 4.12-1 fileutils 4.1-3 findutils 20041227-1 fontconfig 2.2.2-1 freeglut 2.2.0-1 freetype2 2.1.5-1 fvwm 2.4.7-3 gawk 3.1.4-3 gcc 3.4.4-1 gcc-ada 3.4.4-1 gcc-core 3.4.4-1 gcc-g++ 3.4.4-1 gcc-g77 3.4.4-1 gcc-gdc 3.4.4-1 gcc-gpc 3.3.3-3 gcc-java 3.4.4-1 gcc-mingw 20040810-1 gcc-mingw-ada 20050522-1 gcc-mingw-core 20050522-1 gcc-mingw-g++ 20050522-1 gcc-mingw-g77 20050522-1 gcc-mingw-gdc 20050522-1 gcc-mingw-gpc 20040810-1 gcc-mingw-java 20050522-1 gcc-mingw-objc 20050522-1 gcc-objc 3.4.4-1 gcc-testsuite 3.4.4-1 gd 2.0.33-1 gdb 20041228-3 gdbm 1.8.3-7 gettext 0.14.1-1 ghostscript 8.15-2 ghostscript-base 8.15-2 ghostscript-x11 8.15-2 glib 1.2.10-2 glib2 2.4.8-1 glib2-devel 2.4.8-1 gnuplot 4.0.0-1 grep 2.5.1a-2 groff 1.18.1-2 gv 3.5.8-2 gzip 1.3.5-1 lesstif 0.93.94-2 libbz2_1 1.0.2-6 libfontconfig-devel 2.2.2-1 libfontconfig1 2.2.2-1 libfreetype2-devel 2.1.5-1 libfreetype26 2.1.5-1 libgd-devel 2.0.33-1 libgd2 2.0.33-1 libltdl3 1.5.18-1 libtool 1.5b-2 libtool-devel 1.5.10-2 libtool-stable 1.4.3-3 libtool1.5 1.5.18-1 libXft 2.1.6-1 libXft-devel 2.1.6-1 libXft1 1.0.0-1 libXft2 2.1.6-1 m4 1.4.3-1 make 3.80-1 nedit 5.5-1 openbox 0.99.1-4 pcre 4.5-1 pcre-doc 4.5-1 sed 4.1.4-1 tar 1.13.25-7 tcltk 20030901-1 tcm 2.20-1 transfig 3.2.4-2 vim 6.3-1 WindowMaker 0.90.0-2 X-start-menu-icons 1.0.3-2 X-startup-scripts 1.0.10-4 x2x 1.30-2 Xaw3d 1.5D-5 xfig 3.2.4-6 xfig-lib 3.2.4-6 XFree86-lib-compat 4.3.0-2 xgraph 12.1-1 XmHTML 1.1.7-1 xmon 1.5.6-1 xorg-x11-base 6.8.2.0-1 xorg-x11-bin 6.8.2.0-1 xorg-x11-bin-dlls 6.8.2.0-1 xorg-x11-bin-lndir 6.8.2.0-1 xorg-x11-devel 6.8.2.0-2 xorg-x11-etc 6.8.2.0-1 xorg-x11-f100 6.8.1.0-3 xorg-x11-fcyr 6.8.1.0-2 xorg-x11-fenc 6.8.1.0-2 xorg-x11-fnts 6.8.1.0-3 xorg-x11-fscl 6.8.1.0-2 xorg-x11-fsrv 6.8.2.0-1 xorg-x11-libs-data 6.8.2.0-1 xorg-x11-man-pages 6.8.2.0-1 xorg-x11-man-pages-html 6.8.2.0-1 xorg-x11-nest 6.8.2.0-2 xorg-x11-vfb 6.8.2.0-2 xorg-x11-xwin 6.8.2.0-3 xorg-x11-xwin-gl 6.8.2.0-3 xpdf 3.00-2 xterm 202-1 xwinclip 1.2.0-1 xwinwm 0.0.5-1 Use -h to see help about each section From pgq1 at cornell.edu Fri Aug 5 10:08:46 2005 From: pgq1 at cornell.edu (Peter Quigley) Date: Thu Oct 30 14:33:10 2008 Subject: [Magic-dev] Spice model effects Message-ID: <5.2.1.1.2.20050805080249.01cacf10@pop.lns.cornell.edu> Hi, I am having difficulty understanding why two different spice models give radically different timing results for the exact same layout extraction. I extract my layout and then run a spice simulation with the T54G SPICE BSIM3 VERSION 3.1 PARAMETERS. I then take the same extraction and substitute an older (~ six years) spice model. This older model old and has far fewer parameters than the T54G model. The former model gives a factor of five faster circuit. The transistor dimensions appear to be set in the extraction. Does the model scale the layout? Is something fundamentally broken. We have a good deal of experience with the older models and have no reason to doubt the results that we got with them. Any advice would be greatly appreciated. Thank You. Peter G Quigley Wilson Laboratory Laboratory For Elementary Particle Physics Cornell University Ithaca, NY 14853 email: pgq1@cornell.edu Phone: 607-255-4882 Fax: 607-255-8062 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050805/5b1453c3/attachment.html From fang at csl.cornell.edu Sun Aug 7 22:43:11 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:10 2008 Subject: [Magic-dev] C compiler default output... configure: error: C compiler cannot create executables In-Reply-To: Message-ID: <20050807213743.B20791-100000@shannon.csl.cornell.edu> > raju@systemc /usr/local/src/magic-7.2.70 > $ ./configure --without-tcl > checking build system type... i686-pc-cygwin > checking host system type... i686-pc-cygwin > checking target system type... i686-pc-cygwin > checking for gcc... gcc > checking for C compiler default output... configure: error: C compiler > cannot cr > eate executables > See `config.log' for more details. Hi, Can you show us the excerpt of config.log that describes the failure? The only time I've seen this error message is when permissions were set incorrectly on gcc executables, either in .../bin or .../libexec. Also check the permissions of the directory where you are running the configure script -- you need write permissions, of course, to produce object files 'here'. > My setup details after installing cygwin is enclosed in a text file. > Please help me how do I solve this problem, I dont know how to test the C > compiler working. David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- *gag* work in progress From tim at multigig.com Sun Aug 7 22:39:51 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:10 2008 Subject: [Magic-dev] Spice model effects In-Reply-To: <5.2.1.1.2.20050805080249.01cacf10@pop.lns.cornell.edu> References: <5.2.1.1.2.20050805080249.01cacf10@pop.lns.cornell.edu> Message-ID: <42F6E217.1040103@opencircuitdesign.com> Dear Peter, > T54G SPICE BSIM3 VERSION 3.1 PARAMETERS. I then take the same > extraction and substitute an older (~ six years) spice model. This older > model old and has far fewer parameters than the T54G model. > The former model gives a factor of five faster circuit. The transistor > dimensions appear to be set in the extraction. Does the model scale > the layout? Is something fundamentally broken. > We have a good deal of experience with the older models and > have no reason to doubt the results that we got with them. Without seeing the spice decks, my gut feeling is that it's a scaling problem, possibly due to the format written vs. the format read by the simulator. Magic extracts to hspice or spice3 format. The hspice format uses a scale option that is not available in spice3. spice3 output should give all units in absolute numbers. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From fang at csl.cornell.edu Wed Aug 10 20:33:04 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:10 2008 Subject: [Magic-dev] C compiler default output... configure: error:Ccompiler cannot create executables (fwd) Message-ID: <20050810193219.J26181-100000@shannon.csl.cornell.edu> ---------- Forwarded message ---------- Date: Wed, 10 Aug 2005 18:57:55 +0530 From: CODE To: David Fang Subject: RE: [Magic-dev] C compiler default output... configure: error:Ccompiler cannot create executables Hi everyone, I got this problem fixed. Anyone who face this problem, please make sure you have W32api in place. thanks, raju -----Original Message----- From: David Fang [mailto:fang@csl.cornell.edu] Sent: Monday, August 08, 2005 7:13 AM To: CODE Cc: magic-dev@csl.cornell.edu Subject: Re: [Magic-dev] C compiler default output... configure: error:Ccompiler cannot create executables > raju@systemc /usr/local/src/magic-7.2.70 > $ ./configure --without-tcl > checking build system type... i686-pc-cygwin > checking host system type... i686-pc-cygwin > checking target system type... i686-pc-cygwin > checking for gcc... gcc > checking for C compiler default output... configure: error: C compiler > cannot cr > eate executables > See `config.log' for more details. Hi, Can you show us the excerpt of config.log that describes the failure? The only time I've seen this error message is when permissions were set incorrectly on gcc executables, either in .../bin or .../libexec. Also check the permissions of the directory where you are running the configure script -- you need write permissions, of course, to produce object files 'here'. > My setup details after installing cygwin is enclosed in a text file. > Please help me how do I solve this problem, I dont know how to test the C > compiler working. David Fang From fang at csl.cornell.edu Wed Aug 10 20:33:53 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:10 2008 Subject: [Magic-dev] Magic 7.2 & Magic 7.3: Couldn't open display; check DISPLAY variable (fwd) Message-ID: <20050810193339.N26181-200000@shannon.csl.cornell.edu> ---------- Forwarded message ---------- Date: Wed, 10 Aug 2005 18:57:57 +0530 From: CODE To: cygwin@cygwin.com Cc: fang@csl.cornell.edu, ebb9@byu.net Subject: Magic 7.2 & Magic 7.3: Couldn't open display; check DISPLAY variable Hi everyone, I just tried magic-7.2.70 & then magic-7.3.93. Enclosed is my installation set up details. Magic works just fine with "magic -w". However, I am more interested in getting 3D view of my layouts, so when I key in " magic -d OGL" following is the status: ----------------------------------------------------------------- Administrator@systemc ~ $ magic -d OGL Magic 7.3 revision 93 - Compiled on Wed Aug 10 18:10:20 IST 2005. Couldn't open display; check DISPLAY variable The graphics display couldn't be correctly initialized. Use '-d NULL' if you don't need graphics. ------------------------------------------------------------------- Please, anybody let me know how do I correct this & get 3D view of my layouts. thanks raju -------------- next part -------------- Administrator@systemc ~ $ magic -d OGL Magic 7.3 revision 93 - Compiled on Wed Aug 10 18:10:20 IST 2005. Couldn't open display; check DISPLAY variable The graphics display couldn't be correctly initialized. Use '-d NULL' if you don't need graphics. ================================================================== $ cygcheck -c Cygwin Package Information Package Version Status _update-info-dir 00272-1 OK a2ps 4.13-1 OK agetty 2.1-1 OK alternatives 1.3.20a-1 OK antiword 0.34-2 OK apache 1.3.33-1 OK apache2 2.0.54-1 OK apache2-devel 2.0.54-1 OK apache2-manual 2.0.54-1 OK apr 0.9.6-1 OK apr-util 0.9.6-1 OK ash 20040127-3 OK aspell 0.50.3-1 OK aspell-de 0.50.2-1 OK aspell-dev 0.50.3-1 OK aspell-doc 0.50.3-1 OK aspell-en 0.51.0-1 OK aspell-pl 0.50.2-1 OK astyle 1.15.3-3 OK atk 1.8.0-1 OK atk-devel 1.8.0-1 OK atk-doc 1.8.0-1 OK atk-runtime 1.8.0-1 OK audiofile 0.2.6-2 OK autoconf 2.59-2 OK autoconf-devel 2.59-2 OK autoconf-stable 2.13-6 OK autoconf2.1 2.13-1 OK autoconf2.5 2.59-1 OK automake 1.7.9-2 OK automake-devel 1.9.2-2 OK automake-stable 1.4p6-3 OK automake1.4 1.4p6-2 OK automake1.6 1.6.3-2 OK automake1.7 1.7.9-2 OK automake1.8 1.8.5-2 OK automake1.9 1.9.5-2 OK autossh 1.3-2 OK base-files 3.5-1 OK base-passwd 2.2-1 OK bash 3.0-11 OK bashdb 3.00_0.02-2 OK bashdb3 0.02-1 OK bc 1.06-2 OK binutils 20050610-1 OK bison 20030307-1 OK byacc 1.9-1 OK bzip2 1.0.3-1 OK c-client 2002e-3 OK c3270 3.2.20-1 OK cabextract 0.6-2 OK catgets 1.0-1 OK ccache 2.2-1 OK ccdoc 0.8.41-2 OK ccrypt 1.7-1 OK cgoban 1.9.14-1 OK check 0.9.1-1 OK chere 0.6-1 OK chkconfig 1.2.24h-1 OK clamav 0.86.1-1 Incomplete clear 1.0-1 OK clisp 2.34-1 OK cmake 2.0.6-1 OK cocom 0.995-1 OK compface 1.4-5 OK coreutils 5.3.0-9 OK cpio 2.6-3 OK cppunit 1.9.14-1 OK cramfs 1.1-1 OK cron 3.0.1-19 OK crypt 1.1-1 OK ctags 5.5-4 OK ctetris 0.30-1 OK curl 7.11.1-1 OK curl-devel 7.11.1-1 OK cvs 1.11.17-1 OK cvsutils 0.2.3-1 OK cygipc 2.03-2 OK cygrunsrv 1.10-1 OK cygutils 1.2.9-1 OK cygwin 1.5.18-1 OK cygwin-doc 1.4-2 OK cygwin-x-doc 1.0.4-1 OK cyrus-sasl 2.1.19-3 OK d 1.2.0-1 OK db 4.2.52-1 OK ddd 3.3.9-1 OK desktop-file-utils 0.10-1 OK diffstat 1.39-1 OK diffutils 2.8.7-1 OK distcc 2.18.3-1 OK docbook-xml42 4.2-3 OK docbook-xml43 4.3-1 OK docbook-xsl 1.69.0-1 OK doxygen 1.4.2_20050421-1 OK dpkg 1.10.4-2 OK e2fsimage 0.2.0-2 OK e2fsprogs 1.35-3 OK ec-fonts-mftraced 1.0.8-4 OK ed 0.2-1 OK editrights 1.01-1 OK ELFIO 1.0.2-1 OK emacs 21.2-13 OK email 2.3.4-1 OK enscript 1.6.3-3 OK epstool 3.08-1 OK esound 0.2.35-1 OK exif 0.6.9-1 OK exim 4.52-2 OK expat 1.95.8-1 OK fetchmail 6.2.5-2 OK figlet 2.2-1 OK file 4.12-1 OK findutils 20041227-1 OK flex 2.5.4a-3 OK fltk 1.1.4-2 OK fontconfig 2.2.2-1 OK fortune 1.99.1-1 OK freeglut 2.2.0-1 OK freetype2 2.1.5-1 OK fvwm 2.4.7-3 OK gawk 3.1.5-1 OK gcc 3.4.4-1 OK gcc-core 3.4.4-1 OK gcc-g++ 3.4.4-1 OK GConf2 2.8.1-1 OK gd 2.0.33-1 OK gdbm 1.8.3-7 OK gettext 0.14.1-1 OK gettext-devel 0.14.1-1 OK ghostscript 8.15-2 OK ghostscript-base 8.15-2 OK ghostscript-x11 8.15-2 OK glib 1.2.10-3 OK glib-devel 1.2.10-3 OK glib2 2.4.8-1 OK glib2-devel 2.4.8-1 OK glib2-doc 2.4.8-1 OK glib2-runtime 2.4.8-1 OK gmp 4.1.4-2 OK gnome-common 2.8.0-1 OK gnome-icon-theme 2.8.0-1 OK gnome-keyring 0.4.0-1 OK gnome-mime-data 2.4.1-1 OK gnome-vfs2 2.8.0-1 OK gnugo 3.6-1 OK gnupg 1.4.1-1 OK gnuplot 4.0.0-1 OK gperf 2.7.2-1 OK grace 5.1.18-1 OK GraphicsMagick 1.0.6-1 OK grep 2.5.1a-2 OK groff 1.18.1-2 OK gsl 1.6-1 OK gtk+ 1.2.10-2 OK gtk+-devel 1.2.10-2 OK gtk-doc 1.3-1 OK gtk2-x11 2.4.14-1 OK gtk2-x11-devel 2.4.14-1 OK gtk2-x11-doc 2.4.14-1 OK gtk2-x11-runtime 2.4.14-1 OK gtypist 2.7-2 OK guile 1.6.7-1 OK guile-devel 1.6.7-1 OK guile-doc 1.6.7-1 OK gv 3.5.8-2 OK gzip 1.3.5-1 OK help2man 1.33.1-1 OK hexedit 1.2.10-1 OK hicolor-icon-theme 0.5-1 OK ImageMagick 6.0.4-1 OK indent 2.2.9-1 OK inetutils 1.3.2-29 OK initscripts 0.9-1 OK intltool 0.33-1 OK ioperm 0.4-1 OK irc 20010101-3 OK jasper 1.701.0-1 OK jbigkit 1.5-3 OK jgraph 8.3-1 OK joe 3.3-2 OK jpeg 6b-11 OK keychain 2.5.3.1-1 OK lablgtk2 2.4.0-2 OK lapack 3.0-2 OK lcms 1.13-1 OK less 381-1 OK lesstif 0.93.96-2 OK lftp 2.6.10-2 OK libapr0 0.9.6-1 OK libaprutil0 0.9.6-1 OK libart_lgpl 2.3.16-1 OK libaspell15 0.50.3-1 OK libaudiofile-devel 0.2.6-2 OK libaudiofile0 0.2.6-2 OK libbonobo2 2.8.0-1 OK libbonobo2-devel 2.8.0-1 OK libbonobo2-doc 2.8.0-1 OK libbonobo20 2.8.0-1 OK libbonoboui2 2.8.0-1 OK libbz2_0 1.0.2-1 OK libbz2_1 1.0.3-1 OK libcharset1 1.9.2-1 OK libcroco 0.5.1-2 OK libcroco06 0.6.0-1 OK libdb2 2.7.7-4 OK libdb2-devel 2.7.7-4 OK libdb3.1 3.1.17-2 OK libdb3.1-devel 3.1.17-2 OK libdb4.1 4.1.25-1 OK libdb4.1-devel 4.1.25-1 OK libdb4.2 4.2.52-1 OK libdb4.2-devel 4.2.52-1 OK libdb4.3 4.3.28-1 OK libdb4.3-devel 4.3.28-1 OK libesound-devel 0.2.35-1 OK libesound0 0.2.35-1 OK libexif 0.6.9-1 OK libfontconfig-devel 2.2.2-1 OK libfontconfig1 2.2.2-1 OK libfpx 1.2.0.9-1 OK libfreetype2-devel 2.1.5-1 OK libfreetype26 2.1.5-1 OK libgc 6.4-1 OK libgcrypt 1.2.1-1 OK libgd-devel 2.0.33-1 OK libgd2 2.0.33-1 OK libgdbm 1.8.0-5 OK libgdbm-devel 1.8.3-7 OK libgdbm3 1.8.3-3 OK libgdbm4 1.8.3-7 OK libgeotiff 1.2.2-1 OK libgeotiff-devel 1.2.2-1 OK libgeotiff1 1.2.2-1 OK libgettextpo0 0.14.1-1 OK libglade2 2.4.0-1 OK libgnome2 2.8.0-1 OK libgnomecanvas2 2.8.0-1 OK libgnomeprint22 2.8.0.1-1 OK libgnomeprintui22 2.8.0-1 OK libgnomeui2 2.8.0-1 OK libgpg-error 1.1-1 OK libGraphicsMagick-devel 1.0.6-1 OK libGraphicsMagick0 1.0.6-1 OK libguile12 1.6.7-1 OK libguile12abi13 1.6.4-3 OK libguile16 1.7.2-1 OK libiconv 1.9.2-1 OK libiconv2 1.9.2-1 OK libIDL 0.8.3-2 OK libintl 0.10.38-3 OK libintl1 0.10.40-1 OK libintl2 0.12.1-3 OK libintl3 0.14.1-1 OK libjpeg62 6b-11 OK libjpeg6b 6b-8 OK libkpathsea3 2.0.2-15 OK libkpathsea4 3.0.0-3 OK libltdl3 1.5.18-1 OK libMagick-devel 6.0.4-1 OK libMagick6 6.0.4-1 OK libmcrypt 2.5.7-2 OK libmcrypt-devel 2.5.7-2 OK libmng 1.0.8-1 OK libncurses-devel 5.4-2 OK libncurses5 5.2-1 OK libncurses6 5.2-8 OK libncurses7 5.3-4 OK libncurses8 5.4-2 OK libneon24 0.24.7-1 OK libopenldap2 2.1.25-1 OK libopenldap2_2_7 2.2.26-1 OK libpcre 4.1-1 OK libpcre0 4.5-1 OK libpng 1.2.8-2 OK libpng10 1.0.18-2 OK libpng10-devel 1.0.18-2 OK libpng12 1.2.8-2 OK libpng12-devel 1.2.8-2 OK libpng2 1.0.12-1 OK libpopt0 1.6.4-4 OK libproj-devel 4.4.8-1 OK libproj0 4.4.8-1 OK libreadline4 4.1-2 OK libreadline5 4.3-5 OK libreadline6 5.0-4 OK libsasl2 2.1.19-3 OK libsasl2-devel 2.1.19-3 OK libsmi 0.4.2-1 OK libtiff-devel 3.7.3-1 OK libtiff3 3.6.0-2 OK libtiff4 3.6.0-5 OK libtiff5 3.7.3-1 OK libtool1.5 1.5.18-1 OK libungif 4.1.0-3 OK libwmf 0.2.8.3-1 OK libwnck 2.8.1-1 OK libxerces-c21 2.1.0-1 OK libxerces-c22 2.2.0-1 OK libxerces-c23 2.3.0-4 OK libxerces-c24 2.4.0-4 OK libxerces-c25 2.5.0-1 OK libXft 2.1.6-1 OK libXft-devel 2.1.6-1 OK libXft1 1.0.0-1 OK libXft2 2.1.6-1 OK libxml2 2.6.20-3 OK libxml2-devel 2.6.20-3 OK libxml2-doc 2.6.20-3 OK libxml2-python 2.6.20-3 OK libxslt 1.1.14-2 OK lighttpd 1.3.0-1 OK lilypond 2.4.6-1 OK lilypond-doc 2.4.6-1 OK links 0.99pre14-1 OK login 1.9-7 OK lynx 2.8.5-2 OK m4 1.4.3-1 OK make 3.80-1 OK man 1.5p-1 OK mathomatic 12.4.3-1 OK mc 4.6.1-2 OK mhash 0.9.2-1 OK mhash-devel 0.9.1-1 OK mined 2000.10-1 OK mingw-bzip2 1.0.3-1 OK mingw-libbz2_1 1.0.3-1 OK mingw-runtime 3.7-1 OK mingw-zlib 1.2.2-2 OK minires 1.00-1 OK minires-devel 1.00-1 OK mktemp 1.5-3 OK more 2.11o-1 OK mt 2.3.1-1 OK mtd 20050419-1 OK mutt 1.4.2.1i-1 OK naim 0.11.7.2-1 OK nano 1.2.2-1 OK nasm 0.98.39-1 OK ncftp 3.1.7-1 OK ncurses 5.4-2 OK ncurses-demo 5.4-2 OK nedit 5.5-1 OK neon 0.24.7-1 OK netcat 1.10-2 OK nfs-server 2.3-2 OK ocaml 3.08.1-1 OK octave 2.1.71-1 OK octave-forge 2005.06.13-1 OK octave-headers 2.1.71-1 OK openbox 0.99.1-4 OK opengl 1.1.0-7 OK openjade 1.3.3-1 OK openldap 2.2.26-1 OK openldap-devel 2.2.26-1 OK OpenSP 1.5.1-1 OK openssh 4.1p1-2 OK openssl 0.9.8-2 OK openssl-devel 0.9.8-2 OK openssl097 0.9.7g-1 OK ORBit2 2.12.0-1 OK ORBit2-devel 2.12.0-1 OK pango 1.6.0-2 OK pango-devel 1.6.0-2 OK pango-doc 1.6.0-2 OK pango-runtime 1.6.0-2 OK par 1.52-1 OK patch 2.5.8-8 OK patchutils 0.2.30-1 OK pcre 4.5-1 OK pcre-devel 4.5-1 OK pcre-doc 4.5-1 OK pdksh 5.2.14-3 OK perl 5.8.7-3 OK perl-libwin32 0.191-4 OK perl-Win32-GUI 1.0-2 OK perl_manpages 5.8.7-3 OK pine 4.58-1 OK pinfo 0.6.8-1 OK ping 1.0-1 OK pkgconfig 0.17.2-2 OK popt 1.6.4-4 OK postgresql 7.4.5-1 OK pr3270 3.2.20-1 OK procmail 3.22-10 OK procps 3.2.5-1 OK proftpd 1.2.10-1 OK proj 4.4.8-1 OK psmisc 21.5-1 OK psutils 1.17-1 OK python 2.4.1-1 OK rcs 5.7-3 OK readline 5.0-4 OK rebase 2.4.2-1 OK regex 4.4-4 OK robots 2.0-4 OK rpm 4.1-2 OK rpm-build 4.1-1 OK rpm-doc 4.1-1 OK rsync 2.6.3-1 OK ruby 1.8.2-2 OK rxvt 2.7.10-6 OK s3270 3.2.20-1 OK sed 4.1.4-1 OK setsid 0.0-3 OK sh-utils 2.0.15-5 OK shared-mime-info 0.15-1 OK sharutils 4.3.80-1 OK shutdown 1.7-1 OK splint 3.1.1-1 OK squid 2.4.STABLE7-1 OK ssmtp 2.60.9-3 OK startup-notification 0.8-1 OK stow 1.3.3-1 OK stunnel 4.04-3 OK subversion 1.2.0-1 OK subversion-devel 1.2.0-1 OK subversion-python 1.2.0-1 OK suite3270 3.2.20-1 OK sunrpc 4.0-3 OK SWI-Prolog 5.2.6-1 OK swig 1.3.24-1 OK sysvinit 2.84-4 OK t1lib 5.0.2-1 OK t1lib-x11 5.0.2-1 OK tar 1.13.25-7 OK tcl3270 3.2.20-1 OK tcltk 20030214-1 OK tcm 2.20-1 OK tcp_wrappers 7.6-1 OK tcsh 6.14.00-4 OK termcap 20050421-1 OK terminfo 5.4_20041009-1 OK tetex 3.0.0-3 OK tetex-base 3.0.0-3 OK tetex-bin 3.0.0-3 OK tetex-devel 3.0.0-3 OK tetex-doc 3.0.0-3 OK tetex-extra 3.0.0-3 OK tetex-tiny 3.0.0-3 OK tetex-x11 3.0.0-3 OK texinfo 4.8-1 OK transfig 3.2.4-2 OK vim 6.3-1 OK w32api 3.2-1 OK WindowMaker 0.90.0-2 OK X-start-menu-icons 1.0.3-2 OK X-startup-scripts 1.0.9-1 OK x2x 1.30-2 OK Xaw3d 1.5D-5 OK xfig 3.2.4-6 OK xfig-lib 3.2.4-6 OK XFree86-lib-compat 4.3.0-2 OK xgraph 12.1-1 OK XmHTML 1.1.7-1 OK xmon 1.5.6-1 OK xorg-x11-base 6.8.2.0-1 OK xorg-x11-bin 6.8.2.0-1 OK xorg-x11-bin-dlls 6.8.2.0-1 OK xorg-x11-bin-lndir 6.8.2.0-1 OK xorg-x11-devel 6.8.2.0-2 OK xorg-x11-etc 6.8.2.0-1 OK xorg-x11-f100 6.8.1.0-3 OK xorg-x11-fcyr 6.8.1.0-2 OK xorg-x11-fenc 6.8.1.0-2 OK xorg-x11-fnts 6.8.1.0-3 OK xorg-x11-fscl 6.8.1.0-2 OK xorg-x11-fsrv 6.8.2.0-1 OK xorg-x11-libs-data 6.8.2.0-1 OK xorg-x11-man-pages 6.8.2.0-1 OK xorg-x11-man-pages-html 6.8.2.0-1 OK xorg-x11-nest 6.8.2.0-2 OK xorg-x11-vfb 6.8.2.0-2 OK xorg-x11-xwin 6.8.2.0-4 OK xorg-x11-xwin-gl 6.8.2.0-4 OK xpdf 3.00-2 OK xterm 202-1 OK xwinclip 1.2.0-1 OK xwinwm 0.0.5-1 OK =============================================================== $ cygcheck -s -v -r Cygwin Configuration Diagnostics Current System Time: Wed Aug 10 18:22:09 2005 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem c:\ORANT\BIN c:\Modeltech_xe_starter\win32xoem c:\Modeltech_xe\win32xoem c:\BITWARE\ C:\cygwin\lib\lapack Output from C:\cygwin\bin\id.exe (nontsec) UID: 500(Administrator) GID: 513(None) 0(root) 513(None) 544(Administrators) 545(Users) Output from C:\cygwin\bin\id.exe (ntsec) UID: 500(Administrator) GID: 513(None) 0(root) 513(None) 544(Administrators) 545(Users) SysDir: C:\WINNT\system32 WinDir: C:\WINNT USER = `Administrator' PWD = `/home/Administrator' HOME = `/home/Administrator' MAKE_MODE = `unix' HOMEPATH = `\Documents and Settings\Administrator' MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/ X11R6/man' APPDATA = `C:\Documents and Settings\Administrator\Application Data' HOSTNAME = `systemc' TERM = `cygwin' PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 9, GenuineIntel' WINDIR = `C:\WINNT' TEXDOCVIEW_txt = `cygstart %s' TEXDOCVIEW_dvi = `cygstart %s' OLDPWD = `/usr/bin' USERDOMAIN = `SYSTEMC' OS = `Windows_NT' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' OS2LIBPATH = `C:\WINNT\system32\os2\dll;' !:: = `::\' TEMP = `/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp' COMMONPROGRAMFILES = `C:\Program Files\Common Files' USERNAME = `Administrator' TEXDOCVIEW_pdf = `cygstart %s' PROCESSOR_LEVEL = `15' SYSTEMDRIVE = `C:' TEXDOCVIEW_html = `cygstart %s' USERPROFILE = `C:\Documents and Settings\Administrator' PS1 = `\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = `\\SYSTEMC' PROCESSOR_ARCHITECTURE = `x86' LM_LICENSE_FILE = `D:\license.dat;C:\Modeltech_xe_starter\win32xoem\license.dat' !C: = `C:\cygwin\bin' SHLVL = `1' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' HOMEDRIVE = `C:' PROMPT = `$P$G' COMSPEC = `C:\WINNT\system32\cmd.exe' TMP = `/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp' SYSTEMROOT = `C:\WINNT' PRINTER = `hp psc 1200 series' CVS_RSH = `/bin/ssh' PROCESSOR_REVISION = `0209' PKG_CONFIG_PATH = `/usr/X11R6/lib/pkgconfig' TEXDOCVIEW_ps = `cygstart %s' INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/ usr/autotool/stable/info:' PROGRAMFILES = `C:\Program Files' TEXMF = `{/usr/share/lilypond/2.4.6,{!!/home/Administrator/.texmf/config,!!/home /Administrator/.texmf/var,/home/Administrator/texmf,!!/usr/local/share/texmf,!!/ var/lib/texmf,!!/usr/share/texmf}}' NUMBER_OF_PROCESSORS = `1' COMPUTERNAME = `SYSTEMC' _ = `/usr/bin/cygcheck' POSIXLY_CORRECT = `1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x00000022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `C:\cygwin' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `C:\cygwin/bin' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `C:\cygwin/lib' flags = 0x0000000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options a: fd N/A N/A c: hd FAT32 9991Mb 78% CP UN d: hd FAT32 9991Mb 69% CP UN DATA e: hd FAT32 9991Mb 62% CP UN BACKUP f: cd N/A N/A C:\cygwin / system binmode C:\cygwin/bin /usr/bin system binmode C:\cygwin/lib /usr/lib system binmode . /cygdrive system binmode,cygdrive Found: C:\cygwin\bin\awk.exe Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cp.exe Found: C:\cygwin\bin\cpp.exe Found: C:\cygwin\bin\find.exe Found: C:\cygwin\bin\gcc.exe Not Found: gdb Found: C:\cygwin\bin\grep.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\mv.exe Found: C:\cygwin\bin\rm.exe Found: C:\cygwin\bin\sed.exe Found: C:\cygwin\bin\sh.exe Found: C:\cygwin\bin\tar.exe 21k 2005/07/14 C:\WINNT\system32\cygintl.dll - os=4.0 img=1.0 sys=4.0 "cygintl.dll" v0.0 ts=2001/6/20 22:39 61k 2005/07/14 C:\WINNT\system32\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2003/12/4 8:33 63k 2005/07/14 C:\WINNT\system32\cygpcre.dll - os=4.0 img=1.0 sys=4.0 "cygpcre.dll" v0.0 ts=2003/4/11 14:01 22k 2005/07/14 C:\WINNT\system32\cygintl-1.dll - os=4.0 img=1.0 sys=4.0 "cygintl-1.dll" v0.0 ts=2001/12/13 14:58 991k 2005/07/14 C:\WINNT\system32\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0 "cygiconv-2.dll" v0.0 ts=2004/7/6 23:40 37k 2005/07/14 C:\WINNT\system32\cygintl-2.dll - os=4.0 img=1.0 sys=4.0 "cygintl-2.dll" v0.0 ts=2003/8/11 3:20 54k 2005/07/16 C:\WINNT\system32\cygintl-3.dll - os=4.0 img=1.0 sys=4.0 "cygintl-3.dll" v0.0 ts=2004/7/6 23:21 22k 2005/07/14 C:\WINNT\system32\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0 "cygpopt-0.dll" v0.0 ts=2002/6/9 11:15 62k 2005/07/14 C:\WINNT\system32\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcre-0.dll" v0.0 ts=2003/12/11 22:31 216k 2005/07/29 C:\WINNT\system32\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0 "cygncurses-8.dll" v0.0 ts=2004/10/10 13:55 40k 2005/02/23 C:\WINNT\system32\cygxrx-6.dll - os=4.0 img=1.0 sys=4.0 "cygxrx-6.dll" v0.0 ts=2005/2/23 20:23 358k 2005/02/23 C:\WINNT\system32\cygGL-1.dll - os=4.0 img=1.0 sys=4.0 "cygGL-1.dll" v0.0 ts=2005/2/23 20:09 877k 2005/02/23 C:\WINNT\system32\cygX11-6.dll - os=4.0 img=1.0 sys=4.0 "cygX11-6.dll" v0.0 ts=2005/2/23 19:58 49k 2005/02/23 C:\WINNT\system32\cygXext-6.dll - os=4.0 img=1.0 sys=4.0 "cygXext-6.dll" v0.0 ts=2005/2/23 19:58 36k 2005/02/23 C:\WINNT\system32\cygFS-6.dll - os=4.0 img=1.0 sys=4.0 "cygFS-6.dll" v0.0 ts=2005/2/23 20:04 438k 2005/02/23 C:\WINNT\system32\cygGLU-1.dll - os=4.0 img=1.0 sys=4.0 "cygGLU-1.dll" v0.0 ts=2005/2/23 20:11 140k 2004/08/06 C:\WINNT\system32\cygglut-3.dll - os=4.0 img=1.0 sys=4.0 "cygglut-3.dll" v0.0 ts=2004/8/6 20:13 26k 2005/02/23 C:\WINNT\system32\cygdpstk-1.dll - os=4.0 img=1.0 sys=4.0 "cygdpstk-1.dll" v0.0 ts=2005/2/23 20:12 28k 2004/10/22 C:\WINNT\system32\cygDtPrint-1.dll - os=4.0 img=1.0 sys=4.0 "cygDtPrint-1.dll" v0.0 ts=2004/10/22 12:07 21k 2005/02/23 C:\WINNT\system32\cygfontenc-1.dll - os=4.0 img=1.0 sys=4.0 "cygfontenc-1.dll" v0.0 ts=2005/2/23 20:15 75k 2005/02/23 C:\WINNT\system32\cygICE-6.dll - os=4.0 img=1.0 sys=4.0 "cygICE-6.dll" v0.0 ts=2005/2/23 19:58 77k 2004/10/22 C:\WINNT\system32\cygMrm-2.dll - os=4.0 img=1.0 sys=4.0 "cygMrm-2.dll" v0.0 ts=2004/10/22 12:07 9k 2005/02/23 C:\WINNT\system32\cygoldX-6.dll - os=4.0 img=1.0 sys=4.0 "cygoldX-6.dll" v0.0 ts=2005/2/23 19:58 1413k 2005/02/23 C:\WINNT\system32\cygOSMesa-4.dll - os=4.0 img=1.0 sys=4.0 "cygOSMesa-4.dll" v0.0 ts=2005/2/23 20:09 20k 2005/02/23 C:\WINNT\system32\cygpsres-1.dll - os=4.0 img=1.0 sys=4.0 "cygpsres-1.dll" v0.0 ts=2005/2/23 20:12 30k 2005/02/23 C:\WINNT\system32\cygSM-6.dll - os=4.0 img=1.0 sys=4.0 "cygSM-6.dll" v0.0 ts=2005/2/23 19:58 66k 2004/10/22 C:\WINNT\system32\cygUil-2.dll - os=4.0 img=1.0 sys=4.0 "cygUil-2.dll" v0.0 ts=2004/10/22 12:07 275k 2004/01/13 C:\WINNT\system32\cygXaw3d-7.dll - os=4.0 img=1.0 sys=4.0 "cygXaw3d-7.dll" v0.0 ts=2004/1/14 3:47 254k 2005/02/23 C:\WINNT\system32\cygXaw-6.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-6.dll" v0.0 ts=2005/2/23 20:01 356k 2005/02/23 C:\WINNT\system32\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-7.dll" v0.0 ts=2005/2/23 20:02 363k 2005/02/23 C:\WINNT\system32\cygXaw-8.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-8.dll" v0.0 ts=2005/2/23 20:03 9k 2005/02/23 C:\WINNT\system32\cygXcomposite-1.dll - os=4.0 img=1.0 sys=4.0 "cygXcomposite-1.dll" v0.0 ts=2005/2/23 20:14 30k 2005/02/23 C:\WINNT\system32\cygXcursor-1.dll - os=4.0 img=1.0 sys=4.0 "cygXcursor-1.dll" v0.0 ts=2005/2/23 20:13 9k 2005/02/23 C:\WINNT\system32\cygXdamage-1.dll - os=4.0 img=1.0 sys=4.0 "cygXdamage-1.dll" v0.0 ts=2005/2/23 20:14 7k 2005/02/23 C:\WINNT\system32\cygXevie-1.dll - os=4.0 img=1.0 sys=4.0 "cygXevie-1.dll" v0.0 ts=2005/2/23 20:13 16k 2005/02/23 C:\WINNT\system32\cygXfixes-3.dll - os=4.0 img=1.0 sys=4.0 "cygXfixes-3.dll" v0.0 ts=2005/2/23 20:13 56k 2004/03/11 C:\WINNT\system32\cygXft-1.dll - os=4.0 img=1.0 sys=4.0 "cygXft-1.dll" v0.0 ts=2003/11/18 7:12 63k 2004/03/23 C:\WINNT\system32\cygXft-2.dll - os=4.0 img=1.0 sys=4.0 "cygXft-2.dll" v0.0 ts=2004/3/24 3:50 27k 2005/02/23 C:\WINNT\system32\cygXi-6.dll - os=4.0 img=1.0 sys=4.0 "cygXi-6.dll" v0.0 ts=2005/2/23 20:04 125k 2005/02/23 C:\WINNT\system32\cygxkbfile-1.dll - os=4.0 img=1.0 sys=4.0 "cygxkbfile-1.dll" v0.0 ts=2005/2/23 20:04 12k 2005/02/23 C:\WINNT\system32\cygxkbui-1.dll - os=4.0 img=1.0 sys=4.0 "cygxkbui-1.dll" v0.0 ts=2005/2/23 20:04 1301k 2004/10/22 C:\WINNT\system32\cygXm-2.dll - os=4.0 img=1.0 sys=4.0 "cygXm-2.dll" v0.0 ts=2004/10/22 12:04 459k 2004/02/10 C:\WINNT\system32\cygXmHTML-0.dll - os=4.0 img=1.0 sys=4.0 "cygXmHTML-0.dll" v0.0 ts=2004/2/11 1:44 76k 2005/02/23 C:\WINNT\system32\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0 "cygXmu-6.dll" v0.0 ts=2005/2/23 20:00 11k 2005/02/23 C:\WINNT\system32\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0 "cygXmuu-1.dll" v0.0 ts=2005/2/23 20:00 26k 2005/02/23 C:\WINNT\system32\cygXp-6.dll - os=4.0 img=1.0 sys=4.0 "cygXp-6.dll" v0.0 ts=2005/2/23 20:01 52k 2005/02/23 C:\WINNT\system32\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-4.dll" v0.0 ts=2005/2/23 20:00 12k 2005/02/23 C:\WINNT\system32\cygXrandr-2.dll - os=4.0 img=1.0 sys=4.0 "cygXrandr-2.dll" v0.0 ts=2005/2/23 20:13 28k 2005/02/23 C:\WINNT\system32\cygXrender-1.dll - os=4.0 img=1.0 sys=4.0 "cygXrender-1.dll" v0.0 ts=2005/2/23 20:12 8k 2005/02/23 C:\WINNT\system32\cygXRes-1.dll - os=4.0 img=1.0 sys=4.0 "cygXRes-1.dll" v0.0 ts=2005/2/23 20:13 25k 2005/02/23 C:\WINNT\system32\cygxrxnest-6.dll - os=4.0 img=1.0 sys=4.0 "cygxrxnest-6.dll" v0.0 ts=2005/2/23 20:23 282k 2005/02/23 C:\WINNT\system32\cygXt-6.dll - os=4.0 img=1.0 sys=4.0 "cygXt-6.dll" v0.0 ts=2005/2/23 19:59 27k 2005/02/23 C:\WINNT\system32\cygXTrap-6.dll - os=4.0 img=1.0 sys=4.0 "cygXTrap-6.dll" v0.0 ts=2005/2/23 20:13 17k 2005/02/23 C:\WINNT\system32\cygXtst-6.dll - os=4.0 img=1.0 sys=4.0 "cygXtst-6.dll" v0.0 ts=2005/2/23 20:04 243k 2005/02/23 C:\WINNT\system32\cygdps-1.dll - os=4.0 img=1.0 sys=4.0 "cygdps-1.dll" v0.0 ts=2005/2/23 20:12 196k 2001/06/03 C:\WINNT\system32\cygreadline4.2.dll - os=4.0 img=1.0 sys=4.0 "cygreadline4.2.dll" v0.0 ts=2001/6/3 9:19 148k 2003/08/10 C:\WINNT\system32\cygreadline5.dll - os=4.0 img=1.0 sys=4.0 "cygreadline5.dll" v0.0 ts=2003/8/11 4:46 108k 2001/06/28 C:\WINNT\system32\cygreadline4.dll - os=4.0 img=1.0 sys=4.0 "cygreadline4.dll" v0.0 ts=2001/1/7 10:04 144k 2005/07/29 C:\WINNT\system32\cygreadline6.dll - os=4.0 img=1.0 sys=4.0 "cygreadline6.dll" v0.0 ts=2005/7/29 9:27 226k 2001/04/25 C:\WINNT\system32\cygncurses5.dll - os=4.0 img=1.0 sys=4.0 "cygncurses5.dll" v0.0 ts=2001/4/25 10:47 21k 2005/07/14 C:\WINNT\SYSTEM\cygintl.dll - os=4.0 img=1.0 sys=4.0 "cygintl.dll" v0.0 ts=2001/6/20 22:39 991k 2005/07/14 C:\WINNT\SYSTEM\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0 "cygiconv-2.dll" v0.0 ts=2004/7/6 23:40 22k 2005/07/14 C:\WINNT\SYSTEM\cygintl-1.dll - os=4.0 img=1.0 sys=4.0 "cygintl-1.dll" v0.0 ts=2001/12/13 14:58 37k 2005/07/14 C:\WINNT\SYSTEM\cygintl-2.dll - os=4.0 img=1.0 sys=4.0 "cygintl-2.dll" v0.0 ts=2003/8/11 3:20 61k 2005/07/14 C:\WINNT\SYSTEM\cygz.dll - os=4.0 img=1.0 sys=4.0 "cygz.dll" v0.0 ts=2003/12/4 8:33 54k 2005/07/16 C:\WINNT\SYSTEM\cygintl-3.dll - os=4.0 img=1.0 sys=4.0 "cygintl-3.dll" v0.0 ts=2004/7/6 23:21 22k 2005/07/14 C:\WINNT\SYSTEM\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0 "cygpopt-0.dll" v0.0 ts=2002/6/9 11:15 62k 2005/07/14 C:\WINNT\SYSTEM\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0 "cygpcre-0.dll" v0.0 ts=2003/12/11 22:31 63k 2005/07/14 C:\WINNT\SYSTEM\cygpcre.dll - os=4.0 img=1.0 sys=4.0 "cygpcre.dll" v0.0 ts=2003/4/11 14:01 617k 2004/03/22 C:\cygwin\bin\cygcurl-2.dll - os=4.0 img=1.0 sys=4.0 "cygcurl-2.dll" v0.0 ts=2004/3/22 21:22 7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0 "cygcrypt-0.dll" v0.0 ts=2003/10/19 13:27 22k 2004/02/10 C:\cygwin\bin\cygcygipc-2.dll - os=4.0 img=1.0 sys=4.0 "cygcygipc-2.dll" v0.0 ts=2004/2/10 8:18 174k 2004/10/14 C:\cygwin\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0 "cygexpat-0.dll" v0.0 ts=2004/10/14 14:04 146k 2004/12/21 C:\cygwin\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0 "cygmagic-1.dll" v0.0 ts=2004/12/21 20:04 129k 2004/03/11 C:\cygwin\bin\cygfontconfig-1.dll - os=4.0 img=1.0 sys=4.0 "cygfontconfig-1.dll" v0.0 ts=2004/3/11 5:42 361k 2003/10/25 C:\cygwin\bin\cygfreetype-6.dll - os=4.0 img=1.0 sys=4.0 "cygfreetype-6.dll" v0.0 ts=2003/10/22 9:48 41k 2005/06/01 C:\cygwin\bin\cygltdl-3.dll - os=4.0 img=1.0 sys=4.0 "cygltdl-3.dll" v0.0 ts=2005/6/1 11:04 42k 2005/05/04 C:\cygwin\bin\cyglber-2-2-7.dll - os=4.0 img=1.0 sys=4.0 "cyglber-2-2-7.dll" v0.0 ts=2005/5/4 16:24 179k 2005/05/04 C:\cygwin\bin\cygldap-2-2-7.dll - os=4.0 img=1.0 sys=4.0 "cygldap-2-2-7.dll" v0.0 ts=2005/5/4 16:33 191k 2005/05/04 C:\cygwin\bin\cygldap_r-2-2-7.dll - os=4.0 img=1.0 sys=4.0 "cygldap_r-2-2-7.dll" v0.0 ts=2005/5/4 16:33 304k 2004/10/11 C:\cygwin\bin\cygORBit-2-0.dll - os=4.0 img=1.0 sys=4.0 "cygORBit-2-0.dll" v0.0 ts=2004/10/12 4:48 39k 2004/10/11 C:\cygwin\bin\cygORBit-imodule-2-0.dll - os=4.0 img=1.0 sys=4. 0 "cygORBit-imodule-2-0.dll" v0.0 ts=2004/10/12 4:58 18k 2004/10/11 C:\cygwin\bin\cygORBitCosNaming-2-0.dll - os=4.0 img=1.0 sys=4 .0 "cygORBitCosNaming-2-0.dll" v0.0 ts=2004/10/12 4:57 311k 2005/06/22 C:\cygwin\bin\cyghttpd2core.dll - os=4.0 img=1.0 sys=4.0 "cyghttpd2core.dll" v0.0 ts=2005/6/22 22:58 123k 2004/09/29 C:\cygwin\bin\cygatk-1.0-0.dll - os=4.0 img=1.0 sys=4.0 "cygatk-1.0-0.dll" v0.0 ts=2004/9/30 4:46 260k 2005/06/25 C:\cygwin\bin\cygclamav-1.dll - os=4.0 img=1.0 sys=4.0 "cygclamav-1.dll" v0.0 ts=2005/6/25 13:03 529k 2004/06/27 C:\cygwin\bin\cygcppunit-1-9-14.dll - os=4.0 img=1.0 sys=4.0 "cygcppunit-1-9-14.dll" v0.0 ts=2004/6/27 6:59 654k 2003/11/04 C:\cygwin\bin\cygfltknox-0.dll - os=4.0 img=1.0 sys=4.0 "cygfltknox-0.dll" v0.0 ts=2003/11/5 3:27 65k 2003/11/04 C:\cygwin\bin\cygfltknox_forms-0.dll - os=4.0 img=1.0 sys=4.0 "cygfltknox_forms-0.dll" v0.0 ts=2003/11/5 3:27 81k 2003/11/04 C:\cygwin\bin\cygfltknox_gl-0.dll - os=4.0 img=1.0 sys=4.0 "cygfltknox_gl-0.dll" v0.0 ts=2003/11/5 3:28 108k 2003/11/04 C:\cygwin\bin\cygfltknox_images-0.dll - os=4.0 img=1.0 sys=4.0 "cygfltknox_images-0.dll" v0.0 ts=2003/11/5 3:28 135k 2005/03/16 C:\cygwin\bin\cygglib-1-2-0.dll - os=4.0 img=1.0 sys=4.0 "cygglib-1-2-0.dll" v0.0 ts=2005/3/16 7:46 12k 2005/03/16 C:\cygwin\bin\cyggmodule-1-2-0.dll - os=4.0 img=1.0 sys=4.0 "cyggmodule-1-2-0.dll" v0.0 ts=2005/3/16 7:48 10k 2005/03/16 C:\cygwin\bin\cyggthread-1-2-0.dll - os=4.0 img=1.0 sys=4.0 "cyggthread-1-2-0.dll" v0.0 ts=2005/3/16 7:48 564k 2004/12/30 C:\cygwin\bin\cygglib-2.0-0.dll - os=4.0 img=1.0 sys=4.0 "cygglib-2.0-0.dll" v0.0 ts=2004/12/30 19:47 11k 2004/12/30 C:\cygwin\bin\cyggmodule-2.0-0.dll - os=4.0 img=1.0 sys=4.0 "cyggmodule-2.0-0.dll" v0.0 ts=2004/12/30 19:51 252k 2004/12/30 C:\cygwin\bin\cyggobject-2.0-0.dll - os=4.0 img=1.0 sys=4.0 "cyggobject-2.0-0.dll" v0.0 ts=2004/12/30 19:50 15k 2004/12/30 C:\cygwin\bin\cyggthread-2.0-0.dll - os=4.0 img=1.0 sys=4.0 "cyggthread-2.0-0.dll" v0.0 ts=2004/12/30 19:51 158k 2004/10/16 C:\cygwin\bin\cyggmp-3.dll - os=4.0 img=1.0 sys=4.0 "cyggmp-3.dll" v0.0 ts=2004/10/16 13:10 288k 2004/10/16 C:\cygwin\bin\cyggmpxx-3.dll - os=4.0 img=1.0 sys=4.0 "cyggmpxx-3.dll" v0.0 ts=2004/10/16 13:10 71k 2004/10/16 C:\cygwin\bin\cygmp-3.dll - os=4.0 img=1.0 sys=4.0 "cygmp-3.dll" v0.0 ts=2004/10/16 13:10 95k 2004/10/16 C:\cygwin\bin\cygmpfr-0.dll - os=4.0 img=1.0 sys=4.0 "cygmpfr-0.dll" v0.0 ts=2004/10/16 13:17 32k 2004/09/29 C:\cygwin\bin\cyggnome-keyring-0.dll - os=4.0 img=1.0 sys=4.0 "cyggnome-keyring-0.dll" v0.0 ts=2004/9/29 11:57 403k 2004/10/27 C:\cygwin\bin\cyggnomevfs-2-0.dll - os=4.0 img=1.0 sys=4.0 "cyggnomevfs-2-0.dll" v0.0 ts=2004/10/28 2:59 1412k 2005/03/12 C:\cygwin\bin\cyggsl-0.dll - os=4.0 img=1.0 sys=4.0 "cyggsl-0.dll" v0.0 ts=2005/3/13 2:56 184k 2005/03/12 C:\cygwin\bin\cyggslcblas-0.dll - os=4.0 img=1.0 sys=4.0 "cyggslcblas-0.dll" v0.0 ts=2005/3/13 2:32 195k 2004/09/02 C:\cygwin\bin\cyggdk-1-2-0.dll - os=4.0 img=1.0 sys=4.0 "cyggdk-1-2-0.dll" v0.0 ts=2004/9/3 0:01 1293k 2004/09/02 C:\cygwin\bin\cyggtk-1-2-0.dll - os=4.0 img=1.0 sys=4.0 "cyggtk-1-2-0.dll" v0.0 ts=2004/9/3 0:14 394k 2004/12/31 C:\cygwin\bin\cyggdk-x11-2.0-0.dll - os=4.0 img=1.0 sys=4.0 "cyggdk-x11-2.0-0.dll" v0.0 ts=2004/12/31 2:29 79k 2004/12/31 C:\cygwin\bin\cyggdk_pixbuf-2.0-0.dll - os=4.0 img=1.0 sys=4.0 "cyggdk_pixbuf-2.0-0.dll" v0.0 ts=2004/12/31 2:06 56k 2004/12/31 C:\cygwin\bin\cyggdk_pixbuf_xlib-2.0-0.dll - os=4.0 img=1.0 sy s=4.0 "cyggdk_pixbuf_xlib-2.0-0.dll" v0.0 ts=2004/12/31 4:15 2708k 2004/12/31 C:\cygwin\bin\cyggtk-x11-2.0-0.dll - os=4.0 img=1.0 sys=4.0 "cyggtk-x11-2.0-0.dll" v0.0 ts=2004/12/31 3:25 12k 2003/02/17 C:\cygwin\bin\cygioperm-0.dll - os=4.0 img=1.0 sys=4.0 "cygioperm-0.dll" v0.0 ts=2003/2/18 1:28 241k 2004/08/06 C:\cygwin\bin\cygjasper-1-701-1.dll - os=4.0 img=1.0 sys=4.0 "cygjasper-1-701-1.dll" v0.0 ts=2004/8/6 20:47 48k 2003/08/10 C:\cygwin\bin\cygjbig1.dll - os=4.0 img=1.0 sys=4.0 "cygjbig1.dll" v0.0 ts=2003/8/11 5:28 156k 2004/06/04 C:\cygwin\bin\cyglcms-1.dll - os=4.0 img=1.0 sys=4.0 "cyglcms-1.dll" v0.0 ts=2004/6/4 19:30 93k 2005/02/17 C:\cygwin\bin\cygapr-0-0.dll - os=4.0 img=1.0 sys=4.0 "cygapr-0-0.dll" v0.0 ts=2005/2/18 3:22 68k 2005/02/17 C:\cygwin\bin\cygaprutil-0-0.dll - os=4.0 img=1.0 sys=4.0 "cygaprutil-0-0.dll" v0.0 ts=2005/2/18 3:26 77k 2004/06/04 C:\cygwin\bin\cygart_lgpl_2-2.dll - os=4.0 img=1.0 sys=4.0 "cygart_lgpl_2-2.dll" v0.0 ts=2004/6/4 15:50 802k 2003/09/15 C:\cygwin\bin\cygaspell-15.dll - os=4.0 img=1.0 sys=4.0 "cygaspell-15.dll" v0.0 ts=2003/9/15 18:02 145k 2004/09/02 C:\cygwin\bin\cygaudiofile-0.dll - os=4.0 img=1.0 sys=4.0 "cygaudiofile-0.dll" v0.0 ts=2004/9/2 9:08 336k 2004/10/27 C:\cygwin\bin\cygbonobo-2-0.dll - os=4.0 img=1.0 sys=4.0 "cygbonobo-2-0.dll" v0.0 ts=2004/10/27 13:13 72k 2004/10/27 C:\cygwin\bin\cygbonobo-activation-4.dll - os=4.0 img=1.0 sys= 4.0 "cygbonobo-activation-4.dll" v0.0 ts=2004/10/27 4:49 425k 2004/10/29 C:\cygwin\bin\cygbonoboui-2-0.dll - os=4.0 img=1.0 sys=4.0 "cygbonoboui-2-0.dll" v0.0 ts=2004/10/29 4:42 54k 2002/01/27 C:\cygwin\bin\cygbz21.0.dll - os=4.0 img=1.0 sys=4.0 "cygbz21.0.dll" v0.0 ts=2002/1/27 6:37 56k 2005/07/09 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0 "cygbz2-1.dll" v0.0 ts=2005/7/9 10:39 18k 2004/07/06 C:\cygwin\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0 "cygcharset-1.dll" v0.0 ts=2004/7/6 23:39 260k 2004/10/26 C:\cygwin\bin\cygcroco-0.6-3.dll - os=4.0 img=1.0 sys=4.0 "cygcroco-0.6-3.dll" v0.0 ts=2004/10/27 3:39 326k 2002/06/26 C:\cygwin\bin\cygdb2.dll - os=4.0 img=1.0 sys=4.0 "cygdb2.dll" v0.0 ts=2002/6/26 23:18 380k 2002/07/24 C:\cygwin\bin\cygdb-3.1.dll - os=4.0 img=1.0 sys=4.0 "cygdb-3.1.dll" v0.0 ts=2002/7/24 21:54 "cygpangoft2-1.0-0.dll" v0.0 ts=2005/1/9 3:06 33k 2005/01/08 C:\cygwin\bin\cygpangowin32-1.0-0.dll - os=4.0 img=1.0 sys=4.0 "cygpangowin32-1.0-0.dll" v0.0 ts=2005/1/9 3:09 37k 2005/01/08 C:\cygwin\bin\cygpangox-1.0-0.dll - os=4.0 img=1.0 sys=4.0 "cygpangox-1.0-0.dll" v0.0 ts=2005/1/9 3:05 17k 2005/01/08 C:\cygwin\bin\cygpangoxft-1.0-0.dll - os=4.0 img=1.0 sys=4.0 "cygpangoxft-1.0-0.dll" v0.0 ts=2005/1/9 3:08 1248k 2005/07/28 C:\cygwin\bin\cygperl5_8.dll - os=4.0 img=1.0 sys=4.0 "cygperl5_8.dll" v0.0 ts=2005/7/28 14:53 685k 2005/01/18 C:\cygwin\bin\cygruby18.dll - os=4.0 img=1.0 sys=4.0 "cygruby18.dll" v0.0 ts=2005/1/19 2:51 28k 2004/11/15 C:\cygwin\bin\cygstartup-notification-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygstartup-notification-1-0.dll" v0.0 ts=2004/11/15 9:29 134k 2005/06/10 C:\cygwin\bin\cygsvn_client-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_client-1-0.dll" v0.0 ts=2005/6/11 2:55 27k 2005/06/10 C:\cygwin\bin\cygsvn_delta-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_delta-1-0.dll" v0.0 ts=2005/6/11 2:51 22k 2005/06/10 C:\cygwin\bin\cygsvn_diff-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_diff-1-0.dll" v0.0 ts=2005/6/11 2:53 15k 2005/06/10 C:\cygwin\bin\cygsvn_fs-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_fs-1-0.dll" v0.0 ts=2005/6/11 2:52 127k 2005/06/10 C:\cygwin\bin\cygsvn_fs_base-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_fs_base-1-0.dll" v0.0 ts=2005/6/11 2:52 88k 2005/06/10 C:\cygwin\bin\cygsvn_fs_fs-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_fs_fs-1-0.dll" v0.0 ts=2005/6/11 2:51 9k 2005/06/10 C:\cygwin\bin\cygsvn_ra-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_ra-1-0.dll" v0.0 ts=2005/6/11 2:54 85k 2005/06/10 C:\cygwin\bin\cygsvn_ra_dav-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_ra_dav-1-0.dll" v0.0 ts=2005/6/11 2:53 19k 2005/06/10 C:\cygwin\bin\cygsvn_ra_local-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_ra_local-1-0.dll" v0.0 ts=2005/6/11 2:53 55k 2005/06/10 C:\cygwin\bin\cygsvn_ra_svn-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_ra_svn-1-0.dll" v0.0 ts=2005/6/11 2:52 98k 2005/06/10 C:\cygwin\bin\cygsvn_repos-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_repos-1-0.dll" v0.0 ts=2005/6/11 2:53 130k 2005/06/10 C:\cygwin\bin\cygsvn_subr-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_subr-1-0.dll" v0.0 ts=2005/6/11 2:40 146k 2005/06/10 C:\cygwin\bin\cygsvn_wc-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_wc-1-0.dll" v0.0 ts=2005/6/11 2:54 25k 2005/06/10 C:\cygwin\bin\cygsvn_swig_py-1-0.dll - os=4.0 img=1.0 sys=4.0 "cygsvn_swig_py-1-0.dll" v0.0 ts=2005/6/11 2:56 230k 2004/10/04 C:\cygwin\bin\cygt1-5.dll - os=4.0 img=1.0 sys=4.0 "cygt1-5.dll" v0.0 ts=2004/10/5 3:14 18k 2004/10/04 C:\cygwin\bin\cygt1x-5.dll - os=4.0 img=1.0 sys=4.0 "cygt1x-5.dll" v0.0 ts=2004/10/5 3:14 1265k 2005/07/03 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0 ts=2005/7/3 6:00 Cygwin DLL version info: DLL version: 1.5.18 DLL epoch: 19 DLL bad signal mask: 19005 DLL old termios: 5 DLL malloc env: 28 API major: 0 API minor: 132 Shared data: 4 DLL identifier: cygwin1 Mount registry: 2 Cygnus registry name: Cygnus Solutions Cygwin registry name: Cygwin Program options name: Program Options Cygwin mount registry name: mounts v2 Cygdrive flags: cygdrive flags Cygdrive prefix: cygdrive prefix Cygdrive default prefix: Build date: Sat Jul 2 20:30:04 EDT 2005 Shared id: cygwin1S4 56k 2004/03/11 C:\cygwin\usr\X11R6\bin\cygXft-1.dll - os=4.0 img=1.0 sys=4.0 "cygXft-1.dll" v0.0 ts=2003/11/18 7:12 63k 2004/03/23 C:\cygwin\usr\X11R6\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0 "cygXft-2.dll" v0.0 ts=2004/3/24 3:50 275k 2004/01/13 C:\cygwin\usr\X11R6\bin\cygXaw3d-7.dll - os=4.0 img=1.0 sys=4. 0 "cygXaw3d-7.dll" v0.0 ts=2004/1/14 3:47 282k 2003/10/28 C:\cygwin\usr\X11R6\bin\cygfreetype-9.dll - os=4.0 img=1.0 sys =4.0 "cygfreetype-9.dll" v0.0 ts=2003/10/18 12:14 459k 2004/02/10 C:\cygwin\usr\X11R6\bin\cygXmHTML-0.dll - os=4.0 img=1.0 sys=4 .0 "cygXmHTML-0.dll" v0.0 ts=2004/2/11 1:44 36k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygFS-6.dll - os=4.0 img=1.0 sys=4.0 "cygFS-6.dll" v0.0 ts=2005/2/23 20:04 358k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0 "cygGL-1.dll" v0.0 ts=2005/2/23 20:09 438k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygGLU-1.dll - os=4.0 img=1.0 sys=4.0 "cygGLU-1.dll" v0.0 ts=2005/2/23 20:11 75k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0 "cygICE-6.dll" v0.0 ts=2005/2/23 19:58 1413k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygOSMesa-4.dll - os=4.0 img=1.0 sys=4 .0 "cygOSMesa-4.dll" v0.0 ts=2005/2/23 20:09 30k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0 "cygSM-6.dll" v0.0 ts=2005/2/23 19:58 877k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0 "cygX11-6.dll" v0.0 ts=2005/2/23 19:58 8k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXRes-1.dll - os=4.0 img=1.0 sys=4.0 "cygXRes-1.dll" v0.0 ts=2005/2/23 20:13 27k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXTrap-6.dll - os=4.0 img=1.0 sys=4. 0 "cygXTrap-6.dll" v0.0 ts=2005/2/23 20:13 254k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXaw-6.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-6.dll" v0.0 ts=2005/2/23 20:01 356k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-7.dll" v0.0 ts=2005/2/23 20:02 363k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXaw-8.dll - os=4.0 img=1.0 sys=4.0 "cygXaw-8.dll" v0.0 ts=2005/2/23 20:03 9k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXcomposite-1.dll - os=4.0 img=1.0 s ys=4.0 "cygXcomposite-1.dll" v0.0 ts=2005/2/23 20:14 30k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXcursor-1.dll - os=4.0 img=1.0 sys= 4.0 "cygXcursor-1.dll" v0.0 ts=2005/2/23 20:13 9k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXdamage-1.dll - os=4.0 img=1.0 sys= 4.0 "cygXdamage-1.dll" v0.0 ts=2005/2/23 20:14 7k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXevie-1.dll - os=4.0 img=1.0 sys=4. 0 "cygXevie-1.dll" v0.0 ts=2005/2/23 20:13 49k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0 "cygXext-6.dll" v0.0 ts=2005/2/23 19:58 16k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXfixes-3.dll - os=4.0 img=1.0 sys=4 .0 "cygXfixes-3.dll" v0.0 ts=2005/2/23 20:13 27k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXi-6.dll - os=4.0 img=1.0 sys=4.0 "cygXi-6.dll" v0.0 ts=2005/2/23 20:04 76k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0 "cygXmu-6.dll" v0.0 ts=2005/2/23 20:00 11k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0 "cygXmuu-1.dll" v0.0 ts=2005/2/23 20:00 26k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXp-6.dll - os=4.0 img=1.0 sys=4.0 "cygXp-6.dll" v0.0 ts=2005/2/23 20:01 52k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0 "cygXpm-4.dll" v0.0 ts=2005/2/23 20:00 12k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXrandr-2.dll - os=4.0 img=1.0 sys=4 .0 "cygXrandr-2.dll" v0.0 ts=2005/2/23 20:13 28k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXrender-1.dll - os=4.0 img=1.0 sys= 4.0 "cygXrender-1.dll" v0.0 ts=2005/2/23 20:12 282k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0 "cygXt-6.dll" v0.0 ts=2005/2/23 19:59 17k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygXtst-6.dll - os=4.0 img=1.0 sys=4.0 "cygXtst-6.dll" v0.0 ts=2005/2/23 20:04 243k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygdps-1.dll - os=4.0 img=1.0 sys=4.0 "cygdps-1.dll" v0.0 ts=2005/2/23 20:12 26k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygdpstk-1.dll - os=4.0 img=1.0 sys=4. 0 "cygdpstk-1.dll" v0.0 ts=2005/2/23 20:12 21k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygfontenc-1.dll - os=4.0 img=1.0 sys= 4.0 "cygfontenc-1.dll" v0.0 ts=2005/2/23 20:15 9k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygoldX-6.dll - os=4.0 img=1.0 sys=4.0 "cygoldX-6.dll" v0.0 ts=2005/2/23 19:58 20k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygpsres-1.dll - os=4.0 img=1.0 sys=4. 0 "cygpsres-1.dll" v0.0 ts=2005/2/23 20:12 125k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygxkbfile-1.dll - os=4.0 img=1.0 sys= 4.0 "cygxkbfile-1.dll" v0.0 ts=2005/2/23 20:04 12k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygxkbui-1.dll - os=4.0 img=1.0 sys=4. 0 "cygxkbui-1.dll" v0.0 ts=2005/2/23 20:04 40k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygxrx-6.dll - os=4.0 img=1.0 sys=4.0 "cygxrx-6.dll" v0.0 ts=2005/2/23 20:23 25k 2005/02/23 C:\cygwin\usr\X11R6\bin\cygxrxnest-6.dll - os=4.0 img=1.0 sys= 4.0 "cygxrxnest-6.dll" v0.0 ts=2005/2/23 20:23 28k 2004/10/22 C:\cygwin\usr\X11R6\bin\cygDtPrint-1.dll - os=4.0 img=1.0 sys= 4.0 "cygDtPrint-1.dll" v0.0 ts=2004/10/22 12:07 77k 2004/10/22 C:\cygwin\usr\X11R6\bin\cygMrm-2.dll - os=4.0 img=1.0 sys=4.0 "cygMrm-2.dll" v0.0 ts=2004/10/22 12:07 66k 2004/10/22 C:\cygwin\usr\X11R6\bin\cygUil-2.dll - os=4.0 img=1.0 sys=4.0 "cygUil-2.dll" v0.0 ts=2004/10/22 12:07 1301k 2004/10/22 C:\cygwin\usr\X11R6\bin\cygXm-2.dll - os=4.0 img=1.0 sys=4.0 "cygXm-2.dll" v0.0 ts=2004/10/22 12:04 140k 2004/08/06 C:\cygwin\usr\X11R6\bin\cygglut-3.dll - os=4.0 img=1.0 sys=4.0 "cygglut-3.dll" v0.0 ts=2004/8/6 20:13 603k 2005/07/15 C:\cygwin\lib\lapack\cygblas.dll - os=4.0 img=1.0 sys=4.0 "cygblas.dll" v0.0 ts=2005/7/14 17:34 5367k 2005/07/15 C:\cygwin\lib\lapack\cyglapack.dll - os=4.0 img=1.0 sys=4.0 "cyglapack.dll" v0.0 ts=2005/7/14 17:34 No Cygwin services found. Cygwin Package Information Last downloaded files to: D:\magic-5July\cygwin\ Last downloaded files from: D:\magic-5July\cygwin\ Package Version _update-info-dir 00272-1 a2ps 4.13-1 agetty 2.1-1 alternatives 1.3.20a-1 antiword 0.34-2 apache 1.3.33-1 apache2 2.0.54-1 apache2-devel 2.0.54-1 apache2-manual 2.0.54-1 apr 0.9.6-1 apr-util 0.9.6-1 ash 20040127-3 aspell 0.50.3-1 aspell-de 0.50.2-1 aspell-dev 0.50.3-1 aspell-doc 0.50.3-1 aspell-en 0.51.0-1 aspell-pl 0.50.2-1 astyle 1.15.3-3 atk 1.8.0-1 atk-devel 1.8.0-1 atk-doc 1.8.0-1 atk-runtime 1.8.0-1 audiofile 0.2.6-2 autoconf 2.59-2 autoconf-devel 2.59-2 autoconf-stable 2.13-6 autoconf2.1 2.13-1 autoconf2.5 2.59-1 automake 1.7.9-2 automake-devel 1.9.2-2 automake-stable 1.4p6-3 automake1.4 1.4p6-2 automake1.6 1.6.3-2 automake1.7 1.7.9-2 automake1.8 1.8.5-2 automake1.9 1.9.5-2 autossh 1.3-2 base-files 3.5-1 base-passwd 2.2-1 bash 3.0-11 bashdb 3.00_0.02-2 bashdb3 0.02-1 bc 1.06-2 binutils 20050610-1 bison 20030307-1 byacc 1.9-1 bzip2 1.0.3-1 c-client 2002e-3 c3270 3.2.20-1 cabextract 0.6-2 catgets 1.0-1 ccache 2.2-1 ccdoc 0.8.41-2 ccrypt 1.7-1 cgoban 1.9.14-1 check 0.9.1-1 chere 0.6-1 chkconfig 1.2.24h-1 clamav 0.86.1-1 clear 1.0-1 clisp 2.34-1 cmake 2.0.6-1 cocom 0.995-1 compface 1.4-5 coreutils 5.3.0-9 cpio 2.6-3 cppunit 1.9.14-1 cramfs 1.1-1 cron 3.0.1-19 crypt 1.1-1 ctags 5.5-4 ctetris 0.30-1 curl 7.11.1-1 curl-devel 7.11.1-1 cvs 1.11.17-1 cvsutils 0.2.3-1 cygipc 2.03-2 cygrunsrv 1.10-1 cygutils 1.2.9-1 cygwin 1.5.18-1 cygwin-doc 1.4-2 cygwin-x-doc 1.0.4-1 cyrus-sasl 2.1.19-3 d 1.2.0-1 db 4.2.52-1 ddd 3.3.9-1 desktop-file-utils 0.10-1 diffstat 1.39-1 diffutils 2.8.7-1 distcc 2.18.3-1 docbook-xml42 4.2-3 docbook-xml43 4.3-1 docbook-xsl 1.69.0-1 doxygen 1.4.2_20050421-1 dpkg 1.10.4-2 e2fsimage 0.2.0-2 e2fsprogs 1.35-3 ec-fonts-mftraced 1.0.8-4 ed 0.2-1 editrights 1.01-1 ELFIO 1.0.2-1 emacs 21.2-13 email 2.3.4-1 enscript 1.6.3-3 epstool 3.08-1 esound 0.2.35-1 exif 0.6.9-1 exim 4.52-2 expat 1.95.8-1 fetchmail 6.2.5-2 figlet 2.2-1 file 4.12-1 findutils 20041227-1 flex 2.5.4a-3 fltk 1.1.4-2 fontconfig 2.2.2-1 fortune 1.99.1-1 freeglut 2.2.0-1 freetype2 2.1.5-1 fvwm 2.4.7-3 gawk 3.1.5-1 gcc 3.4.4-1 gcc-core 3.4.4-1 gcc-g++ 3.4.4-1 GConf2 2.8.1-1 gd 2.0.33-1 gdbm 1.8.3-7 gettext 0.14.1-1 gettext-devel 0.14.1-1 ghostscript 8.15-2 ghostscript-base 8.15-2 ghostscript-x11 8.15-2 glib 1.2.10-3 glib-devel 1.2.10-3 glib2 2.4.8-1 glib2-devel 2.4.8-1 glib2-doc 2.4.8-1 glib2-runtime 2.4.8-1 gmp 4.1.4-2 gnome-common 2.8.0-1 gnome-icon-theme 2.8.0-1 gnome-keyring 0.4.0-1 gnome-mime-data 2.4.1-1 gnome-vfs2 2.8.0-1 gnugo 3.6-1 gnupg 1.4.1-1 gnuplot 4.0.0-1 gperf 2.7.2-1 grace 5.1.18-1 GraphicsMagick 1.0.6-1 grep 2.5.1a-2 groff 1.18.1-2 gsl 1.6-1 gtk+ 1.2.10-2 gtk+-devel 1.2.10-2 gtk-doc 1.3-1 gtk2-x11 2.4.14-1 gtk2-x11-devel 2.4.14-1 gtk2-x11-doc 2.4.14-1 gtk2-x11-runtime 2.4.14-1 gtypist 2.7-2 guile 1.6.7-1 guile-devel 1.6.7-1 guile-doc 1.6.7-1 gv 3.5.8-2 gzip 1.3.5-1 help2man 1.33.1-1 hexedit 1.2.10-1 hicolor-icon-theme 0.5-1 ImageMagick 6.0.4-1 indent 2.2.9-1 inetutils 1.3.2-29 initscripts 0.9-1 intltool 0.33-1 ioperm 0.4-1 irc 20010101-3 jasper 1.701.0-1 jbigkit 1.5-3 jgraph 8.3-1 joe 3.3-2 jpeg 6b-11 keychain 2.5.3.1-1 lablgtk2 2.4.0-2 lapack 3.0-2 lcms 1.13-1 less 381-1 lesstif 0.93.96-2 lftp 2.6.10-2 libapr0 0.9.6-1 libaprutil0 0.9.6-1 libart_lgpl 2.3.16-1 libaspell15 0.50.3-1 libaudiofile-devel 0.2.6-2 libaudiofile0 0.2.6-2 libbonobo2 2.8.0-1 libbonobo2-devel 2.8.0-1 libbonobo2-doc 2.8.0-1 libbonobo20 2.8.0-1 libbonoboui2 2.8.0-1 libbz2_0 1.0.2-1 libbz2_1 1.0.3-1 libcharset1 1.9.2-1 libcroco 0.5.1-2 libcroco06 0.6.0-1 libdb2 2.7.7-4 libdb2-devel 2.7.7-4 libdb3.1 3.1.17-2 libdb3.1-devel 3.1.17-2 libdb4.1 4.1.25-1 libdb4.1-devel 4.1.25-1 libdb4.2 4.2.52-1 libdb4.2-devel 4.2.52-1 libdb4.3 4.3.28-1 libdb4.3-devel 4.3.28-1 libesound-devel 0.2.35-1 libesound0 0.2.35-1 libexif 0.6.9-1 libfontconfig-devel 2.2.2-1 libfontconfig1 2.2.2-1 libfpx 1.2.0.9-1 libfreetype2-devel 2.1.5-1 libfreetype26 2.1.5-1 libgc 6.4-1 libgcrypt 1.2.1-1 libgd-devel 2.0.33-1 libgd2 2.0.33-1 libgdbm 1.8.0-5 libgdbm-devel 1.8.3-7 libgdbm3 1.8.3-3 libgdbm4 1.8.3-7 libgeotiff 1.2.2-1 libgeotiff-devel 1.2.2-1 libgeotiff1 1.2.2-1 libgettextpo0 0.14.1-1 libglade2 2.4.0-1 libgnome2 2.8.0-1 libgnomecanvas2 2.8.0-1 libgnomeprint22 2.8.0.1-1 libgnomeprintui22 2.8.0-1 libgnomeui2 2.8.0-1 libgpg-error 1.1-1 libGraphicsMagick-devel 1.0.6-1 libGraphicsMagick0 1.0.6-1 libguile12 1.6.7-1 libguile12abi13 1.6.4-3 libguile16 1.7.2-1 libiconv 1.9.2-1 libiconv2 1.9.2-1 libIDL 0.8.3-2 libintl 0.10.38-3 libintl1 0.10.40-1 libintl2 0.12.1-3 libintl3 0.14.1-1 libjpeg62 6b-11 libjpeg6b 6b-8 libkpathsea3 2.0.2-15 libkpathsea4 3.0.0-3 libltdl3 1.5.18-1 libMagick-devel 6.0.4-1 libMagick6 6.0.4-1 libmcrypt 2.5.7-2 libmcrypt-devel 2.5.7-2 libmng 1.0.8-1 libncurses-devel 5.4-2 libncurses5 5.2-1 libncurses6 5.2-8 libncurses7 5.3-4 libncurses8 5.4-2 libneon24 0.24.7-1 libopenldap2 2.1.25-1 libopenldap2_2_7 2.2.26-1 libpcre 4.1-1 libpcre0 4.5-1 libpng 1.2.8-2 libpng10 1.0.18-2 libpng10-devel 1.0.18-2 libpng12 1.2.8-2 libpng12-devel 1.2.8-2 libpng2 1.0.12-1 libpopt0 1.6.4-4 libproj-devel 4.4.8-1 libproj0 4.4.8-1 libreadline4 4.1-2 libreadline5 4.3-5 libreadline6 5.0-4 libsasl2 2.1.19-3 libsasl2-devel 2.1.19-3 libsmi 0.4.2-1 libtiff-devel 3.7.3-1 libtiff3 3.6.0-2 libtiff4 3.6.0-5 libtiff5 3.7.3-1 libtool1.5 1.5.18-1 libungif 4.1.0-3 libwmf 0.2.8.3-1 libwnck 2.8.1-1 libxerces-c21 2.1.0-1 libxerces-c22 2.2.0-1 libxerces-c23 2.3.0-4 libxerces-c24 2.4.0-4 libxerces-c25 2.5.0-1 libXft 2.1.6-1 libXft-devel 2.1.6-1 libXft1 1.0.0-1 libXft2 2.1.6-1 libxml2 2.6.20-3 libxml2-devel 2.6.20-3 libxml2-doc 2.6.20-3 libxml2-python 2.6.20-3 libxslt 1.1.14-2 lighttpd 1.3.0-1 lilypond 2.4.6-1 lilypond-doc 2.4.6-1 links 0.99pre14-1 login 1.9-7 lynx 2.8.5-2 m4 1.4.3-1 make 3.80-1 man 1.5p-1 mathomatic 12.4.3-1 mc 4.6.1-2 mhash 0.9.2-1 mhash-devel 0.9.1-1 mined 2000.10-1 mingw-bzip2 1.0.3-1 mingw-libbz2_1 1.0.3-1 mingw-runtime 3.7-1 mingw-zlib 1.2.2-2 minires 1.00-1 minires-devel 1.00-1 mktemp 1.5-3 more 2.11o-1 mt 2.3.1-1 mtd 20050419-1 mutt 1.4.2.1i-1 naim 0.11.7.2-1 nano 1.2.2-1 nasm 0.98.39-1 ncftp 3.1.7-1 ncurses 5.4-2 ncurses-demo 5.4-2 nedit 5.5-1 neon 0.24.7-1 netcat 1.10-2 nfs-server 2.3-2 ocaml 3.08.1-1 octave 2.1.71-1 octave-forge 2005.06.13-1 octave-headers 2.1.71-1 openbox 0.99.1-4 opengl 1.1.0-7 openjade 1.3.3-1 openldap 2.2.26-1 openldap-devel 2.2.26-1 OpenSP 1.5.1-1 openssh 4.1p1-2 openssl 0.9.8-2 openssl-devel 0.9.8-2 openssl097 0.9.7g-1 ORBit2 2.12.0-1 ORBit2-devel 2.12.0-1 pango 1.6.0-2 pango-devel 1.6.0-2 pango-doc 1.6.0-2 pango-runtime 1.6.0-2 par 1.52-1 patch 2.5.8-8 patchutils 0.2.30-1 pcre 4.5-1 pcre-devel 4.5-1 pcre-doc 4.5-1 pdksh 5.2.14-3 perl 5.8.7-3 perl-libwin32 0.191-4 perl-Win32-GUI 1.0-2 perl_manpages 5.8.7-3 pine 4.58-1 pinfo 0.6.8-1 ping 1.0-1 pkgconfig 0.17.2-2 popt 1.6.4-4 postgresql 7.4.5-1 pr3270 3.2.20-1 procmail 3.22-10 procps 3.2.5-1 proftpd 1.2.10-1 proj 4.4.8-1 psmisc 21.5-1 psutils 1.17-1 python 2.4.1-1 rcs 5.7-3 readline 5.0-4 rebase 2.4.2-1 regex 4.4-4 robots 2.0-4 rpm 4.1-2 rpm-build 4.1-1 rpm-doc 4.1-1 rsync 2.6.3-1 ruby 1.8.2-2 rxvt 2.7.10-6 s3270 3.2.20-1 sed 4.1.4-1 setsid 0.0-3 sh-utils 2.0.15-5 shared-mime-info 0.15-1 sharutils 4.3.80-1 shutdown 1.7-1 splint 3.1.1-1 squid 2.4.STABLE7-1 ssmtp 2.60.9-3 startup-notification 0.8-1 stow 1.3.3-1 stunnel 4.04-3 subversion 1.2.0-1 subversion-devel 1.2.0-1 subversion-python 1.2.0-1 suite3270 3.2.20-1 sunrpc 4.0-3 SWI-Prolog 5.2.6-1 swig 1.3.24-1 sysvinit 2.84-4 t1lib 5.0.2-1 t1lib-x11 5.0.2-1 tar 1.13.25-7 tcl3270 3.2.20-1 tcltk 20030214-1 tcm 2.20-1 tcp_wrappers 7.6-1 tcsh 6.14.00-4 termcap 20050421-1 terminfo 5.4_20041009-1 tetex 3.0.0-3 tetex-base 3.0.0-3 tetex-bin 3.0.0-3 tetex-devel 3.0.0-3 tetex-doc 3.0.0-3 tetex-extra 3.0.0-3 tetex-tiny 3.0.0-3 tetex-x11 3.0.0-3 texinfo 4.8-1 transfig 3.2.4-2 vim 6.3-1 w32api 3.2-1 WindowMaker 0.90.0-2 X-start-menu-icons 1.0.3-2 X-startup-scripts 1.0.9-1 x2x 1.30-2 Xaw3d 1.5D-5 xfig 3.2.4-6 xfig-lib 3.2.4-6 XFree86-lib-compat 4.3.0-2 xgraph 12.1-1 XmHTML 1.1.7-1 xmon 1.5.6-1 xorg-x11-base 6.8.2.0-1 xorg-x11-bin 6.8.2.0-1 xorg-x11-bin-dlls 6.8.2.0-1 xorg-x11-bin-lndir 6.8.2.0-1 xorg-x11-devel 6.8.2.0-2 xorg-x11-etc 6.8.2.0-1 xorg-x11-f100 6.8.1.0-3 xorg-x11-fcyr 6.8.1.0-2 xorg-x11-fenc 6.8.1.0-2 xorg-x11-fnts 6.8.1.0-3 xorg-x11-fscl 6.8.1.0-2 xorg-x11-fsrv 6.8.2.0-1 xorg-x11-libs-data 6.8.2.0-1 xorg-x11-man-pages 6.8.2.0-1 xorg-x11-man-pages-html 6.8.2.0-1 xorg-x11-nest 6.8.2.0-2 xorg-x11-vfb 6.8.2.0-2 xorg-x11-xwin 6.8.2.0-4 xorg-x11-xwin-gl 6.8.2.0-4 xpdf 3.00-2 xterm 202-1 xwinclip 1.2.0-1 xwinwm 0.0.5-1 Use -h to see help about each section ======================================================================== From fang at csl.cornell.edu Thu Aug 11 14:58:06 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:11 2008 Subject: [Magic-dev] OS X patch updated for magic-7.1 Message-ID: <20050811134630.W27478-100000@shannon.csl.cornell.edu> Hi folks, I've posted updated instructions and patch for building magic-7.1 on Mac OS X 10.3+ at http://www.csl.cornell.edu/~fang/sw/magic-7.1-osx.html Summary of patch: (old) Fixed (old) Conditional support for Darwin-ism / mach-ism (old) __APPLE__ conditional for endianness (new) #include standard headers to silence implicit built-in function warnings (just for cleaning sake) (new) Fixed magic/proto.magic to work with cpp. None of these changes should break compiles on other platforms, in fact, many of these changes may also be needed for other platforms, especially with newer versions of gcc. Note: none of these revisions have made it back into cvs yet. Is there any word of an upcoming release for 7.1.x? A stable, end-of-life release of 7.1 would be nice... David Fang From tim at multigig.com Thu Aug 11 13:17:07 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:11 2008 Subject: [Magic-dev] Magic 7.2 & Magic 7.3: Couldn't open display; check DISPLAY variable (fwd) In-Reply-To: <20050810193339.N26181-200000@shannon.csl.cornell.edu> References: <20050810193339.N26181-200000@shannon.csl.cornell.edu> Message-ID: <42FBA433.3060804@opencircuitdesign.com> Dear David, > Magic works just fine with "magic -w". However, I am more interested in > getting 3D view of my layouts, so when I key in " magic -d OGL" following is > the status: > > Magic 7.3 revision 93 - Compiled on Wed Aug 10 18:10:20 IST 2005. > Couldn't open display; check DISPLAY variable > The graphics display couldn't be correctly initialized. > Use '-d NULL' if you don't need graphics. > Cygwin Package Information > Package Version > opengl 1.1.0-7 > xorg-x11-xwin-gl 6.8.2.0-4 From the above package information, it looks like you have the relevant packages for OpenGL. If you didn't, magic probably would not have made it as far as it did. Here are the possibilities: 1) check DISPLAY variable, as it says. The script /usr/local/bin/magic in the Cygwin version should set DISPLAY to ":0". In the tkcon console of magic ("magic -d OGL -w"), you can query the variable using the Tcl command "echo $env(DISPLAY)". It may be that the script does not set the environment variable correctly for some command-line options, such as having no "-w" in the command line. You can always try "export DISPLAY=:0" in the Cygwin terminal before running magic. 2) If Xwin_GL is available, it should be run instead of Xwin. I'm not sure of the current status of Xwin_GL, whether it exists or if it just installs a variant of the Xwin server that handles OpenGL calls. I expect any problem with the OpenGL version has a trivial solution, provided that we understand the problem properly. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From raju_ga153 at rediffmail.com Tue Aug 30 06:13:18 2005 From: raju_ga153 at rediffmail.com (Appala raju) Date: Thu Oct 30 14:33:12 2008 Subject: [Magic-dev] I am unable to install Magic Message-ID: <20050830051318.22207.qmail@webmail26.rediffmail.com> Dear sir, I am Raju.G.A,I am doing M.Tech in VLSI.I have downloaded magic software from your site and tried to install in my system.But I am unable to install it(I have followed steps what ever given in READ_ME). My os is SUSE LINUX. Pls let me know how to install it.Thanking you. Raju.G.A -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050830/87077122/attachment.html From sondeen at ISI.EDU Thu Sep 1 15:02:28 2005 From: sondeen at ISI.EDU (Jeff Sondeen) Date: Thu Oct 30 14:33:12 2008 Subject: [Magic-dev] magic install issue with redhat Fedore core 3 linux 64bit Message-ID: <17175.27748.935475.61181@vapor.isi.edu> Hi, here's 2 install notes for the 'tcl' variant of magic 7.3 on the 64bit version of redhat Fedore core 3 linux: 1) i had to tell the ./configure script where to find the 'tclConfig.sh' script, else when configure looked inside '/usr/lib' and didn't find tclConfig.sh, it declines to install the 'tcl' variant. ./configure --prefix=/home/sondeen/linux/magic --with-tcl=/usr/lib64 --with-tk=/usr/lib64 2) since the Fedora core install seems to set the Tcl built-in variable 'auto_path' having '/usr/lib' before '/usr/lib64' (and on 64bit Fedora, there's nothing in '/usr/lib' for tcl, only in '/usr/lib64'), i had to put a crude fix: set i [ lsearch $auto_path /usr/lib ] set j [ lsearch $auto_path /usr/lib64 ] puts stderr "old auto_path: $auto_path" puts stderr "i: $i j: $j" if {$i >= 0 && $j >= 0 && $i < $j} { set auto_path [lreplace $auto_path $i $i /usr/lib64 ] set auto_path [lreplace $auto_path $j $j /usr/lib ] } puts stderr "new auto_path: $auto_path" (your mileage may vary, i'm sure there are better fixes) into: /home/sondeen/linux/magic/lib/magic/tcl/tkcon.tcl: just after the start lines: #!/bin/sh # \ exec ${MAGIC_WISH:=wish} "$0" ${1+"$@"} else on magic startup, it says: error in slave eval: couldn't load file "/usr/lib/tk8.4/../libtk8.4.so": /usr/lib/tk8.4/../libtk8.4.so: cannot open shared object file: No such file or directory /jeff From puneet_m at students.iiit.net Thu Sep 15 06:23:46 2005 From: puneet_m at students.iiit.net (Puneet) Date: Thu Oct 30 14:33:12 2008 Subject: [Magic-dev] :specialopen command Message-ID: The specialopen netlist command is not displaying the netlist menu. Instead it gives the following error - :specialopen netlist Usage: specialopen [leftx bottomy rightx topy] type [args] Valid window types are: color layout What could be the problem?? Puneet -- From vamsi.krishnak at gmail.com Fri Sep 16 22:43:59 2005 From: vamsi.krishnak at gmail.com (vamsi krishna) Date: Thu Oct 30 14:33:13 2008 Subject: [Magic-dev] :specialopen command In-Reply-To: References: Message-ID: <3faf05680509160913315bada2@mail.gmail.com> AFAIR its netlist-menu not netlist , look at tut6 under /docs On 9/15/05, Puneet wrote: > > > The specialopen netlist command is not displaying the netlist menu. > Instead it gives the following error - > > :specialopen netlist > Usage: specialopen [leftx bottomy rightx topy] type [args] > Valid window types are: > color > layout > > What could be the problem?? > > Puneet > -- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > magic-dev mailing list > magic-dev@vlsi.cornell.edu > http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050916/6ac2cf71/attachment.html From tim at multigig.com Fri Sep 16 10:50:22 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:13 2008 Subject: [Magic-dev] :specialopen command In-Reply-To: References: Message-ID: <432AF7CE.2040504@opencircuitdesign.com> Puneet wrote: > The specialopen netlist command is not displaying the netlist menu. > Instead it gives the following error - > > :specialopen netlist > Usage: specialopen [leftx bottomy rightx topy] type [args] > Valid window types are: > color > layout > > What could be the problem?? What version of magic are you using? utils/main.c (in magic version 7.3.100) has: #ifdef ROUTE_MODULE /* Initialize the netlist menu */ NMinit(); #endif so if the route module is not compiled in, the netlist window will be unavailable. Since I spent some time making sure that the netlist menu is not dependent on other packages like the router, it may suffice just to remove the #ifdef statements around NMinit() and recompile. If this doesn't work, then you will have to recompile with the route modules. If you do remove the #ifdef statements and recompile, and everything works normally, please let me know and I will remove the statements from the distribution. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From spaceborne_calin at yahoo.com Wed Sep 21 23:59:39 2005 From: spaceborne_calin at yahoo.com (Spaceborne Calin) Date: Thu Oct 30 14:33:13 2008 Subject: [Magic-dev] Compiling error for magic7.3.102 Message-ID: <20050921205939.64932.qmail@web53908.mail.yahoo.com> Hello I try to compile magic on my slackware box I configure magic with the following command: ./configure --prefix=/usr/local/magic --enable-calma --enable-cif --enable-plot --with-tcl The error is: --- compiling database/DBcellsrch.o DBcellsrch.c: In function `dbTileScaleFunc': DBcellsrch.c:1512: error: `CIFPaintTable' undeclared (first use in this function) DBcellsrch.c:1512: error: (Each undeclared identifier is reported only once DBcellsrch.c:1512: error: for each function it appears in.) If i add -DCIF_MODULE to CFLAGS magic compiles ok. However, when i run it, i receive the following error: loading history file ... 1 events added error in slave eval: couldn't load file "/usr/local/magic/lib/magic/tcl/tclmagic.so": /usr/local/magic/lib/magic/tcl/tclmagic.so: undefined symbol: CIFSolidBits Main console display active (Tcl8.4.6 / Tk8.4.6) (tcl) 2 % If i configure with: ./configure --prefix=/usr/local/magic --enable-calma --enable-plot --with-tcl when i try to run it (with magic -w) it says: loading history file ... 1 events added error in slave eval: couldn't load file "/usr/local/magic/lib/magic/tcl/tclmagic.so": /usr/local/magic/lib/magic/tcl/tclmagic.so: undefined symbol: CalmaContactArrays Main console display active (Tcl8.4.6 / Tk8.4.6) (tcl) 2 % If i configure with: ./configure --prefix=/usr/local/magic --enable-plot --with-tcl it compiles and runs (almost - but other hot stuff will be sent later) correctly. Bye Calin P.S. gcc is 3.3.4 Yahoo! Mail - Votre e-mail personnel et gratuit qui vous suit partout ! Cr?ez votre Yahoo! Mail sur http://mail.yahoo.fr From tim at multigig.com Thu Sep 22 22:26:28 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:13 2008 Subject: [Magic-dev] Compiling error for magic7.3.102 In-Reply-To: <20050921205939.64932.qmail@web53908.mail.yahoo.com> References: <20050921205939.64932.qmail@web53908.mail.yahoo.com> Message-ID: <433383F4.4080404@opencircuitdesign.com> Dear Calin, > Hello > > I try to compile magic on my slackware box > I configure magic with the following command: > ./configure --prefix=/usr/local/magic --enable-calma --enable-cif > --enable-plot --with-tcl > > The error is: > ... I have never used "--enable-calma" or any of the other "--enable" compile options. Normally they're included, and you would use "--disable" to remove the packages. Clearly the makefile process doesn't set the -D... flags when you use "--enable". Thanks for the bug report; should be easy to fix. But note that by doing "./configure" you get (or at least, you are supposed to get) the same behavior as the line you typed above. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From puneetrocks at gmail.com Fri Sep 30 04:55:24 2005 From: puneetrocks at gmail.com (Puneet Maheshwari) Date: Thu Oct 30 14:33:14 2008 Subject: [Magic-dev] Netlist Information Message-ID: <588212940509291525524064f3@mail.gmail.com> Is the node in the ext file same as the net?? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20050930/a4f3d7fc/attachment.html From puneetrocks at gmail.com Sat Oct 1 14:52:02 2005 From: puneetrocks at gmail.com (Puneet Maheshwari) Date: Thu Oct 30 14:33:16 2008 Subject: [Magic-dev] Regarding Extract Message-ID: <588212940510010122v79d0008cg1a3f9f908ad55199@mail.gmail.com> When we do the extract command, devices get extracted. Also we get the layout netlist from it. Can anyone tell me how this netlist is computed?? Do they find the enclosures of polygons for computing the netlist. Thanx Puneet -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20051001/d214a722/attachment.html From mcnzhao at yahoo.com Wed Oct 5 17:52:29 2005 From: mcnzhao at yahoo.com (Minchen Zhao) Date: Thu Oct 30 14:33:16 2008 Subject: [Magic-dev] Magic on RedHat Enterprise Linux 64 EMT Message-ID: <4344673D.4010101@yahoo.com> HI, does Magic work on 64 bit Redhat Enterprise Linux such as EM64 bits? thanks, Minchen From clint.kelly at gmail.com Sun Oct 9 20:38:18 2005 From: clint.kelly at gmail.com (Clint Kelly) Date: Thu Oct 30 14:33:16 2008 Subject: [Magic-dev] errGnd! ???? Message-ID: <20eabb880510091638n6e203a9j8859dc7f6eace1e6@mail.gmail.com> Hi! Does anybody know what it means when I run ext2spice and I get a bunch of nodes in my spice file called "errGnd!"??? -Clint From tim at multigig.com Mon Oct 10 08:35:58 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:16 2008 Subject: [Magic-dev] errGnd! ???? In-Reply-To: <20eabb880510091638n6e203a9j8859dc7f6eace1e6@mail.gmail.com> References: <20eabb880510091638n6e203a9j8859dc7f6eace1e6@mail.gmail.com> Message-ID: <434A7C4E.9000202@opencircuitdesign.com> Dear Clint, > Hi! Does anybody know what it means when I run ext2spice and I get a > bunch of nodes in my spice file called "errGnd!"??? ext2spice prints this any time it finds a device for which it cannot determine the substrate node. The tech file entry for a device can either specify a default node name to use if there is no substrate node specified, or it can omit this, in which case ext2spice will generate "errGnd!". You are more likely to get "errGnd!" nodes if you don't explicitly draw n- and p- wells (this is also the reason for having drawn p-wells in an n-well process technology). Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From mcnzhao at yahoo.com Mon Oct 10 18:04:02 2005 From: mcnzhao at yahoo.com (Minchen Zhao) Date: Thu Oct 30 14:33:16 2008 Subject: [Magic-dev] magic init problem Message-ID: <20051011000402.38623.qmail@web81910.mail.mud.yahoo.com> Upon installation of magic 7.3 on RedHat 7.3 OS. % magic loading history file ... 0 events added error in slave eval: syntax error in expression "$do_wrapper == true" Main console display active (Tcl8.3.3 / Tk8.3.3) (minchen) 1 % is it something wrong or missing from installation >From Magic tutorial: magic tut1 should see layout, however I see the same error as above. thanks, Minchen From tim.edwards at multigig.com Tue Oct 11 20:12:23 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:16 2008 Subject: [Magic-dev] magic init problem In-Reply-To: <20051011000402.38623.qmail@web81910.mail.mud.yahoo.com> References: <20051011000402.38623.qmail@web81910.mail.mud.yahoo.com> Message-ID: <434C7107.4080204@multigig.com> Dear Minchen, > error in slave eval: > syntax error in expression "$do_wrapper == true" > Main console display active (Tcl8.3.3 / Tk8.3.3) Apparently Tcl 8.3 allows one to use "true" and "false" unquoted if setting a variable but not if testing it, which I assume was a bug, not a feature, and was clearly corrected in version 8.4. There is only one occurrence of the error, and the correction is to change line 179 of tcltk/magic.tcl.in from if {$do_wrapper == true} { to just if {$do_wrapper} { and do "make install" again. I will correct this in the distribution and repost it. Thanks for reporting the problem. ---Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From clint.kelly at gmail.com Wed Oct 19 13:57:12 2005 From: clint.kelly at gmail.com (Clint Kelly) Date: Thu Oct 30 14:33:16 2008 Subject: [Magic-dev] ext2spice area and perim problems Message-ID: <20eabb880510190957g1e4b1d02ib14ab4423896be6c@mail.gmail.com> Hello. I am having a problem with ext2spice in magic 7.3. Using both the command-line ext2spice and the built-in tcl command ":exttospice", I always get area and perimeter as zero for source and drain for all transistors in my spice file. I have tried this with layout from two different technology files and it happens with both of them. I tried using the magic 7.1 version of ext2spice and this does not happen. Does anybody know what the problem might be? Any help is greatly appreciated! -Clint From wan at ecf.utoronto.ca Wed Oct 19 00:13:15 2005 From: wan at ecf.utoronto.ca (Wan Eric) Date: Thu Oct 30 14:33:17 2008 Subject: [Magic-dev] Magic used on Windows, please help Message-ID: Hi, I am a student at the University of Toronto. I'm now taking a course that uses Magic 6.5. Because I have a physical disability, I am not able to use a computer at school. I have my own computer at home with special adaptive equipment, and so I'm making an attempt to set up Magic here. The problem is that I have windows xp, and Magic is not compatible with winxp. I can't find any instructions on how to set it up on Windows. Can you please give me some guidance? I'd appreciate very much your help. Thanks, Eric From tim.edwards at multigig.com Thu Oct 27 11:16:21 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:17 2008 Subject: [Magic-dev] ext2spice area and perim problems In-Reply-To: <20eabb880510190957g1e4b1d02ib14ab4423896be6c@mail.gmail.com> References: <20eabb880510190957g1e4b1d02ib14ab4423896be6c@mail.gmail.com> Message-ID: <43610B65.7060007@multigig.com> Dear Clint, > Hello. I am having a problem with ext2spice in magic 7.3. Using both > the command-line ext2spice and the built-in tcl command ":exttospice", > I always get area and perimeter as zero for source and drain for all > transistors in my spice file. I have tried this with layout from two > different technology files and it happens with both of them. > > I tried using the magic 7.1 version of ext2spice and this does not > happen. Does anybody know what the problem might be? Any help is > greatly appreciated! First try ext2spice with some obvious known circuit, like tut11a.mag, with a known good techfile like scmos.tech. I just did this; I get an assortment of transistors with zero and non-zero S/D areas and perimeters. Because magic calculates area and perimeter per node, nodes that are shared between multiple transistor sources and drains have a calculated *total* area and perimeter. When writing SPICE, magic writes out this total value for the first transistor encountered, and all remaining connected transistors have their area and perimeter set to zero. Using "ext2spice -d" will distribute the area and perimeter equally between all transistors connected to the same node. If you really have ALL S/D area and perimeter values set to zero, then there is some fundamental error, probably with the technology file. To debug it I would need enough information to recreate the problem; that is, the technology file you're using (or just the name of it if it is a standard one), a sample layout that produces the problem, and a verbatim list of command-line commands and options used. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim.edwards at multigig.com Sun Oct 30 10:14:23 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:17 2008 Subject: [Magic-dev] Re: Web Site Comments In-Reply-To: <43642FEE.60000@austin.rr.com> References: <43642FEE.60000@austin.rr.com> Message-ID: <43650D7F.4030100@multigig.com> Erwin J. Prinz wrote: > * Can you announce on the mailing list that the old web site is out of > date? I stumbled by accident on the 7.3.108 version at > opencircuitdesign.com whereas the old web site http://bach.ece.jhu.edu > contains only the 7.3.106 version. Okay, here's the announcement: I've been getting increasingly concerned about the fact that bach.ece.jhu.edu is an old (by computer standards) SGI Indigo^2 running IRIX, with practically no remaining hardware or software support services. It sits in the corner of the lab of my former advisor Gert Cauwenberghs at Johns Hopkins, while Gert himself is actually on leave and at UCSD this year. Meanwhile, the domain opencircuitdesign.com, which I registered myself, has moved up from being my personal home computer on a Comcast cable line to a machine in the MultiGiG server closet with a dedicated IP address. As long as I keep up the registration and the redirection service, opencircuitdesign.com can exist anywhere in the world, indefinitely. So I am moving all my stuff there. Consequently, the following addresses are now preferred: Magic http://opencircuitdesign.com/magic/ (Version 7.3) IRSIM http://opencircuitdesign.com/irsim/ Netgen http://opencircuitdesign.com/netgen/ XCircuit http://opencircuitdesign.com/xcircuit/ PCB http://opencircuitdesign.com/pcb/ (Version 3.0) The link to "pcb" is a new branch for an alpha version of the code which is otherwise found on pcb.sourceforge.net, maintained by harry eaton at APL. It is my intention to give all this back over to harry to have a single code base once again, but it has not been high on my agenda lately. The link to "magic" is for my development version 7.3. Version 7.1 is still listed as "distribution". However, Rajit Manohar has indicated that he would like to shift to version 7.3 as the distribution version. So hopefully that will happen sometime soon. ---Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim.edwards at multigig.com Sun Oct 30 16:37:56 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:18 2008 Subject: [Magic-dev] Re: [Xcircuit-dev] Re: Web Site Comments In-Reply-To: <200510301400.52499.bob.paddock@gmail.com> References: <43642FEE.60000@austin.rr.com> <43650D7F.4030100@multigig.com> <200510301400.52499.bob.paddock@gmail.com> Message-ID: <43656764.3090203@multigig.com> Bob Paddock wrote: >> The link to "pcb" is a new branch for an alpha version of the code >> which is otherwise found on pcb.sourceforge.net, maintained by harry >> eaton at APL. > > PCB from cvs already runs on the Alpha?: Sorry, I meant "alpha" as in "alpha", "beta", "distribution". The Tcl/Tk-based version of PCB has so far only been compiled on Linux systems, although that does include 64-bit Opteron running 64-bit Fedore Core 2. The Tcl/Tk version has not been exhaustively tested on anything, although it has been used by MultiGiG to create quite a few printed circuit boards. Thus the "alpha" designation. ---Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From miquel.soler.mir at gmail.com Mon Oct 31 14:31:39 2005 From: miquel.soler.mir at gmail.com (Miquel Soler i Mir) Date: Thu Oct 30 14:33:19 2008 Subject: [Magic-dev] Problems in magiz Message-ID: <24575fcf0510310531y7fc7ec0u5dab92d6ca01a2f2@mail.gmail.com> Hello, my name is Miquel Soler i Mir and I'm studen of electronic enginyering in UPC in Catalonia (Barcelona) I would like to us magiz, but a have some problems with the installation. when i make "make config" the shell aswer me: miki@MikiMonster:~/magic-7.1.7$ make config Makefile:17: defs.mak: El fitxer o directori no existeix No "defs.mak" file found. Run make config to make one. Welcome to Magic's configuration program. This is Version 7.1. Unknown user: cad. make: *** [config] Error 1 I'm not good in Linux. Thanks for you help. -- Miquel Soler i Mir From spaceborne_calin at yahoo.com Wed Nov 2 15:24:19 2005 From: spaceborne_calin at yahoo.com (Spaceborne Calin) Date: Thu Oct 30 14:33:19 2008 Subject: [Magic-dev] Re: Web Site Comments In-Reply-To: <43650D7F.4030100@multigig.com> Message-ID: <20051102142419.81949.qmail@web53902.mail.yahoo.com> --- "R. Timothy Edwards" a ?crit : > > The link to "magic" is for my development version 7.3. Version 7.1 > is > still listed as "distribution". However, Rajit Manohar has indicated > that he would like to shift to version 7.3 as the distribution > version. > So hopefully that will happen sometime soon. > > ---Tim Are there any plans to "port" the technology files to Magic 7.3 ? Or do the old technology files still work with magic 7.3 because i understood that there are some differences between mmagic pre 7.3 technlogy files and magic 7.3 technology files. Thank you Calin ___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger T?l?chargez cette version sur http://fr.messenger.yahoo.com From tim.edwards at multigig.com Wed Nov 2 09:28:39 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:19 2008 Subject: [Magic-dev] Re: Web Site Comments In-Reply-To: <20051102142419.81949.qmail@web53902.mail.yahoo.com> References: <20051102142419.81949.qmail@web53902.mail.yahoo.com> Message-ID: <4368F747.408@multigig.com> Dear Calin, > Are there any plans to "port" the technology files to Magic 7.3 ? > Or do the old technology files still work with magic 7.3 because i > understood that there are some differences between mmagic pre 7.3 > technology files and magic 7.3 technology files. There are enhancements to the technology file format in 7.3, but the original technology files work fine. The only real behavioral difference is that contacts do not stack unless this is explicitly spelled out in the tech file. In the original tech27 format, some people relied on the ability to draw, for example, a m345 contact on top of a m123 contact to create a m12345 structure. Apparently, this actually worked, although I have difficulty understanding how it can work without completely screwing up the database. At any rate, my recommendation is to insert the keyword "stackable" at the end of the "contact" section of the techfile, and stop using the stacked contact types (e.g., "m123c"---just draw "m3c" on top of "m2c"). There is a program I wrote called "convert" that makes some attempt to convert format-27 technology files into format-30 files, mainly by removing the stacked contact types (this makes the technology file quite a bit smaller). It works on everything except the "cifinput" section, which will probably need to be hand-edited if you want to import CIF/GDS files. The source code and some comments on the program are at http://opencircuitdesign.com/magic/; click on the "Technology Files" button, and go to the section titled "The New Technology Files". I have now taped out 6 or 7 major chip designs using magic-7.3, in five different technologies (AMI .35, TSMC .18 and .09, Jazz .18, and Peregrine 0.25). All of them (so far) have worked (I wouldn't say "flawlessly", but this is experimental stuff). What we in the magic-dev community really need to do is to push to get this stuff back up on download sites for MOSIS and, hopefully, other fab facilities as well. It is less a matter of porting technology files than of writing scripts and documentation to put together an environment equivalent to a Cadence toolkit. It has been suggested to me by several people, including Rajit, that it would be extremely helpful to have tools to convert from Cadence to magic. ---Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From svenn at bjerkem.de Tue Nov 8 00:05:44 2005 From: svenn at bjerkem.de (Svenn Are Bjerkem) Date: Thu Oct 30 14:33:19 2008 Subject: [Magic-dev] Now that Tim has formalized the development home for some EDA tools ... Message-ID: <20051108000544.64735f46.svenn@bjerkem.de> ... I hope it will also be possible to centralize the mailinglists for these programs, and also start getting some serious work on getting them debian clean. I found that xcircuit was orphaned and picked up by John Rigg lately as I was trying to get a more up-to-date source compiled at home. I also found that there is no version of magic, netgen or irsim available for debian. PCB is heavily developed by some of the gEDA guys over at http://geda.seul.org and they seem to be focusing on gtk. (They have discovered that Tim has a fork based on Tcl/Tk) I think we should take a discussion on how to proceed coordination as I guess that Tim has an idea where he wants to go with the tools. There is also the license topic. I haven't checked all licenses and I hope they would fit the criterias that Debian set. Bringing the TimTools to Debian also has a downside: I expect the cry for support to increase and thus the packaging and maintaining of the Debian packages should not be something that Tim would have to bother about. I will take the jobs that nobody else wants. Now, I hope as many as possible who more or less actively use the TimTools step up and say something about what hardware and operating system they use and if a Debian initiative make any sense in your opinion. If you don't want to publish to the mailinglists, send me an email and I will post a short summary to the lists. -- Kind regards, Svenn From iltseng at seed.net.tw Thu Nov 10 23:39:10 2005 From: iltseng at seed.net.tw (I-Lun Tseng (SeedNet)) Date: Thu Oct 30 14:33:19 2008 Subject: [Magic-dev] Re: Now that Tim has formalized the development home for some EDA tools ... Message-ID: <000201c5e5fc$354b8c30$0401010a@TOMDESKTOP> I have recently installed Debian 3.1 and tried to complie and install Magic on it. I must say that it was very frustrating. I downloaded all of the Magic versions that I can get on the web. However, none of them can be compiled on Debian. I was even forced to use older version of gcc (2.9.x) instead of 3.3.x. Fortunately, I installed Red Hat Linux 9 then and the compliation passed finally. Take a look at this mailing list. Quit a large portion of questions is about compilation and installation. Some of them have not been answered (and maybe resolved) yet. I really think that the Magic team should make more efforts on this issue. For the long term development, I would suggest getting more people involved in this project; even the people who do not have a PhD from Ivy League or other famous universities. Build a better forum, such as using phpBB, instead of this stone age mailing list. Organize people who specialize in specific topics. Each group has developers and modulators working on that topic. Just like any other successful open-source projects. From mpe at writeme.com Fri Nov 11 14:04:28 2005 From: mpe at writeme.com (Marcus Escobosa) Date: Thu Oct 30 14:33:19 2008 Subject: [Magic-dev] widespacing drc rule Message-ID: <20051111220428.60562.qmail@web81306.mail.mud.yahoo.com> I have been looking for documentation on the widespacing drc check I found in the scmos8 tech file, but can't find any. Where should I be looking? Thanks Marcus Escobsosa From fang at csl.cornell.edu Sat Nov 12 23:29:43 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:19 2008 Subject: [Magic-dev] Re: Now that Tim has formalized the development home for some EDA tools ... In-Reply-To: <000201c5e5fc$354b8c30$0401010a@TOMDESKTOP> Message-ID: <20051112231059.H45482-100000@shannon.csl.cornell.edu> > I have recently installed Debian 3.1 and tried to complie and install Magic > on it. I must say that it was very frustrating. I downloaded all of the > Magic versions that I can get on the web. However, none of them can be > compiled on Debian. I was even forced to use older version of gcc (2.9.x) > instead of 3.3.x. Fortunately, I installed Red Hat Linux 9 then and the > compliation passed finally. Hi, If 7.1 was one of the versions you tried, the released distribution on the web is rather outdated, unfortunately. For a better chance at 7.1, you'll have to checkout the latest revision in CVS, instructions posted on the web site. However, that alone may not compile on anything newer than gcc-2.9x. I've posted a patch months ago to make it compilable on Mac OS X with gcc-3.3 and 4.0, most of which are platform-independent fixes to the source, and may be of help to you. That patch (with comments and instructions) can be found at: http://www.csl.cornell.edu/~fang/sw/magic-7.1-osx.html Hopefully, one of the maintainers will get around to checking this in one day and releasing an updated 7.1. *ahem* :) If that still produces problems, post a build log, and we may be able to help further. For more recent versions of Magic, Tim's should be able to provide some answers. > Take a look at this mailing list. Quit a large portion of questions is about > compilation and installation. Some of them have not been answered (and maybe > resolved) yet. I really think that the Magic team should make more efforts > on this issue. > > For the long term development, I would suggest getting more people involved > in this project; even the people who do not have a PhD from Ivy League or > other famous universities. Build a better forum, such as using phpBB, > instead of this stone age mailing list. Organize people who specialize in > specific topics. Each group has developers and modulators working on that > topic. Just like any other successful open-source projects. Stone age? Yeah, it DOES feel old... doesn't it? David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- (2400 baud? Netscape 3.0?? lynx??? No problem!) From tim.edwards at multigig.com Sat Nov 12 20:56:18 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:20 2008 Subject: [Magic-dev] Re: Debian compile and install In-Reply-To: <000201c5e5fc$354b8c30$0401010a@TOMDESKTOP> References: <000201c5e5fc$354b8c30$0401010a@TOMDESKTOP> Message-ID: <4376C772.5050405@multigig.com> Dear I-Lun Tseng, > I have recently installed Debian 3.1 and tried to complie and install > Magic on it. I must say that it was very frustrating. I downloaded all > of the Magic versions that I can get on the web. However, none of them > can be compiled on Debian. I was even forced to use older version of gcc > (2.9.x) instead of 3.3.x. Fortunately, I installed Red Hat Linux 9 then > and the compliation passed finally. Are you sure you've tried magic version 7.3 from the opencircuitdesign website (http;//opencircuitdesign.com)? This should have no difficulty compiling under Debian if you follow the instructions on the website. > Take a look at this mailing list. Quite a large portion of questions is > about compilation and installation. Some of them have not been answered > (and maybe resolved) yet. I really think that the Magic team should make > more efforts on this issue. This is because the developers (mostly me, but it applies to others as well) spend our time writing source code, inventing algorithms, not to mention doing layout and submitting chip designs to foundries. I try to leave it to others to generate, distribute, and maintain packages, such as for Debian or RedHat. Partly this is because I have a limited number of systems myself (one Fedora Core 2 laptop and one Fedora Core 3 desktop 64-bit Opteron system). If I keep up a Debian package, then 1) it will take time away from development, and 2) someone will come along and complain that I don't have a Slackware package, or Solaris binaries, etc. Fortunately, there are people out there willing to do this. > For the long term development, I would suggest getting more people > involved in this project; even the people who do not have a PhD from Ivy > League or other famous universities. Build a better forum, such as using > phpBB, instead of this stone age mailing list. Organize people who > specialize in specific topics. Each group has developers and modulators > working on that topic. Just like any other successful open-source projects. Sounds great to me! I'll even set up an account on opencircuitdesign.com for anybody who wants to help. For now, though, I have a chip to tape out on Monday, so I'm booked until Tuesday. After that, I'll get back on the mailing lists and see if I can start putting together some support for a coherent project. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From rajit at csl.cornell.edu Sun Nov 13 00:16:35 2005 From: rajit at csl.cornell.edu (Rajit Manohar) Date: Thu Oct 30 14:33:20 2008 Subject: [Magic-dev] widespacing drc rule In-Reply-To: <20051111220428.60562.qmail@web81306.mail.mud.yahoo.com> References: <20051111220428.60562.qmail@web81306.mail.mud.yahoo.com> Message-ID: Hi, There's some information about this rule posted by Tim on the mailing list earlier this year. http://vlsi.cornell.edu/pipermail/magic-dev/2005/000077.html Regards, -Rajit From rajit at csl.cornell.edu Sun Nov 13 13:43:59 2005 From: rajit at csl.cornell.edu (Rajit Manohar) Date: Thu Oct 30 14:33:20 2008 Subject: [Magic-dev] Re: Debian compile and install In-Reply-To: <4376C772.5050405@multigig.com> References: <000201c5e5fc$354b8c30$0401010a@TOMDESKTOP> <4376C772.5050405@multigig.com> Message-ID: <48f31751f0fc6e61a44558e25ebbc274@csl.cornell.edu> Dear I-Lun Tseng, I just wanted to echo what Tim said. There are many many platforms, and the issue of porting is pretty low priority for the people listed as developers (although Tim is doing most of the work :-) ). This is part of the reason the mailing list is called "magic-dev", rather than something like magic-users. This is also why the traffic is incredibly low, and it is only a mailing list. A parallel mailing list "magic-users" that deals with compilation/installation/porting issues would be extremely helpful, along with forums/etc. If Tim wants to host it that's great, otherwise I can easily set this up if there are volunteers willing to respond to questions/maintain packages/etc. (In fact I already have phpBB installed on the machine that hosts the mailing list.) Regards, -Rajit From svenn at bjerkem.de Tue Nov 15 00:26:46 2005 From: svenn at bjerkem.de (Svenn Are Bjerkem) Date: Thu Oct 30 14:33:20 2008 Subject: [Magic-dev] Re: Debian compile and install In-Reply-To: <4376C772.5050405@multigig.com> References: <000201c5e5fc$354b8c30$0401010a@TOMDESKTOP> <4376C772.5050405@multigig.com> Message-ID: <20051115002646.2c2ff9e7.svenn@bjerkem.de> On Sat, 12 Nov 2005 20:56:18 -0800 "R. Timothy Edwards" wrote: > > Are you sure you've tried magic version 7.3 from the opencircuitdesign > website (http;//opencircuitdesign.com)? This should have no difficulty > compiling under Debian if you follow the instructions on the website. I can confirm that magic-7.3.108 compiles on Debian sid (unstable). I assume you are allowed to install packages on your system (otherwise talk to your administrator about it. I am looking at way to bypass itchy admins ...) You need to have the packages tcl8.4, tcl8.4-dev, tk8.4, tk8.4-dev installed. Download and unpack magic, enter the magic directory and run the command ./configure --prefix=/opt/foss/magic-7.3.108 --with-tcl=/usr/lib/tcl8.4 --wi th-tk=/usr/lib/tk8.4 It is also nice to have the package blt installed. The --prefix above tell where to install the software. Feel free to put it anywhere you like. > > > Take a look at this mailing list. Quite a large portion of questions is > > about compilation and installation. Some of them have not been answered > > (and maybe resolved) yet. I really think that the Magic team should make > > more efforts on this issue. > > This is because the developers (mostly me, but it applies to others as > well) spend our time writing source code, inventing algorithms, not to > mention doing layout and submitting chip designs to foundries. > I try to leave it to others to generate, distribute, and maintain > packages, such as for Debian or RedHat. Partly this is because I have > a limited number of systems myself (one Fedora Core 2 laptop and one > Fedora Core 3 desktop 64-bit Opteron system). If I keep up a Debian > package, then 1) it will take time away from development, and 2) someone > will come along and complain that I don't have a Slackware package, or > Solaris binaries, etc. Fortunately, there are people out there willing > to do this. We got to start somewhere and collect important issues for each distribution in order to see if something needs to be done in the source tree. I don't know other distributions but Debian, and here it is possible to have the package system patch the sourcecode before compiling it in order to "massage" the package to fit the Debian binary tree. Most of these things can be solved with the autoconf system, but I find autoconf quite a hassle to learn. -- Svenn From tim.edwards at multigig.com Mon Nov 21 12:30:35 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:20 2008 Subject: [Magic-dev] Re: "extresist" fixed in 7.3 In-Reply-To: <20051121030443.35660.qmail@web31114.mail.mud.yahoo.com> References: <20051121030443.35660.qmail@web31114.mail.mud.yahoo.com> Message-ID: <43822E6B.7040905@multigig.com> Dear Vijaya, > I will be grateful if I can get the information that > the version 7.3 bug has been fixed. Okay, I found that the problem was with extresist's handling of the contact structures that were introduced in 7.3 to allow stacked contacts. I have fixed the error in 7.3.109 and tested on your example layout, and I am now getting what appears to be a correct cell_new.res.ext. Thank you for sending the example layout, and please let me know if you have any further problems. It is still true that "extresist" does not understand the "device" types (e.g., "device mosfet" or "device bjt") also introduced with version 7.3, but this will not be a problem with the technology file you are using. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From david at excavacionsbermudez.com Tue Nov 22 17:29:09 2005 From: david at excavacionsbermudez.com (=?iso-8859-1?Q?David_Berm=FAdez?=) Date: Thu Oct 30 14:33:21 2008 Subject: [Magic-dev] hi Message-ID: <20051122162740.0140F3BB4E@vrx03.nomiland.com> Hi! I'm David from Barcelona (Spain). I'm a electronical student, and I want to install magic in my Fedora Core 4. I have a problem in the instalation. I can't execute the order: setenv CAD-HOME ~/cad-try/, because setenv is not in the bash. How I can install the sofware? Maybe magic can't run in Fedora distribution?? Thanks and excuse me for my english, Regards, David -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20051122/efb60acb/attachment.html From fang at csl.cornell.edu Tue Nov 22 23:17:19 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:21 2008 Subject: [Magic-dev] help compiling (was: hi) In-Reply-To: <20051122162740.0140F3BB4E@vrx03.nomiland.com> Message-ID: <20051122231127.G64311-100000@shannon.csl.cornell.edu> > I have a problem in the instalation. I can't execute the order: setenv > CAD-HOME ~/cad-try/, because setenv is not in the bash. Hi, In bash, use 'export' to set environment variables. Then let us know how the rest of the installation goes. (Please include the magic version number in your report as well.) ('configure', then 'make', then 'make install') > How I can install the sofware? Maybe magic can't run in Fedora > distribution?? It *should* work on any linux variant. Please use a more descriptive subject in the header, your message almost got filtered as spam. Best, David Fang From tim.edwards at multigig.com Tue Nov 22 20:31:43 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:21 2008 Subject: [Magic-dev] hi In-Reply-To: <20051122162740.0140F3BB4E@vrx03.nomiland.com> References: <20051122162740.0140F3BB4E@vrx03.nomiland.com> Message-ID: <4383F0AF.4080701@multigig.com> Dear David, > I have a problem in the instalation. I can't execute the order: setenv > CAD-HOME ~/cad-try/, because setenv is not in the bash. > > How I can install the software? Maybe magic can't run in Fedora > distribution?? 1) Compile/Install magic-7.3 from opencircuitdesign.com. Follow the instructions, and don't set CAD_HOME, which is obsolete. Magic-7.3 is developed on a Fedora 3 distribution. (or) 2) If you must compile/install with "make config", CAD_HOME, etc., then the proper invocation in bash would be: export CAD_HOME=~/cad-try/ Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim.edwards at multigig.com Thu Nov 24 10:14:36 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:21 2008 Subject: [Magic-dev] Re: Magic MAXPLANES In-Reply-To: <20051124105023.48517.qmail@web52011.mail.yahoo.com> References: <20051124105023.48517.qmail@web52011.mail.yahoo.com> Message-ID: <4386030C.30108@multigig.com> Dear Malvin, > 1. MAXPLANES was set to 32 to illustrate the boundary > of the problem (when MAXPLANES = 64, the same problem > arises). When MAXPLANES = 31, everything works as it > should be, but you would be limited to 31 minus the 6 > built-in planes = 25 planes. That's bad because of > the number of planes and layers our layouts require > these days. You've uncovered a major error in magic. At some point I changed MAXPLANES from 32 to 64. However, definitions like: #define PlaneNumToMaskBit(p) (1 << (p)) #define PlaneMaskHasPlane(m, p) (((m) & PlaneNumToMaskBit(p)) != 0) usually have a target type defined as integer, which is normally 32 bits. So while MAXPLANES may be set to 64, plane definitions are limited to 32 or strange things will start happening. Crashing is not likely, just that any routine that maps planes into a bit mask will ignore any plane above number 31. This matches the description you provide about how magic behaves when 32 or more planes are defined in the technology file. There is no quick fix. The simplest fix is to create a typedef for, e.g., "PlaneMaskType", that would be a 4-byte integer if MAXPLANES is 32 or less, or an 8-byte integer if MAXPLANES is 64 or less. Then every typecast for variables used as plane mask must be changed from "int" to "PlaneMaskType". This works assuming that 64 planes is enough. In general it should be true that a technology file never needs more than 64 planes. However, there are cases, like mapping an unknown GDS file into magic with one type per plane, where one may very easily overreach 64 defined planes. In this case, the plane mask has to be defined like "TileTypeBitMask", with an array of integers, and any logical operation on the bitmask has to be replaced with a macro. Or, we get rid of all instances of using bitmasks as planes and replace the plane array with something else, like a hash table (which is the approach that MicroMagic took. I will probably go ahead an implement the "simple solution", because at least Magic will be consistent between the defined value of MAXPLANES and the number of planes that are correctly handled. Later, I'll probably work on the hash table thing as part of the next development version. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From lauromam at yahoo.com.br Thu Nov 24 18:56:19 2005 From: lauromam at yahoo.com.br (Lauro Magno de Aquino Macedo) Date: Thu Oct 30 14:33:22 2008 Subject: [Magic-dev] problem with instalation of magic Message-ID: <20051124215619.3037.qmail@web53707.mail.yahoo.com> I had problem with the installation of magic in Suse. I changed the distribution for Debian Ubuntu (kernel 2.6.12-9-386) and occurred the following problem when I use make after using ./configure . configure: "Notice: Use 'make' to compile and 'make install' to install" root@lauro:/home/lauro/magic# make --- errors and warnings logged in file make.log --- making header file database/database.h root@lauro:/home/lauro/magic# Somebody could help me ? Thanks. Lauro lauromam@yahoo.com.br __________________________________________________ Fa?a liga??es para outros computadores com o novo Yahoo! Messenger http://br.beta.messenger.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20051124/62695890/attachment.html From tim.edwards at multigig.com Fri Nov 25 10:46:13 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:23 2008 Subject: [Magic-dev] Re: Magic MAXPLANES In-Reply-To: <20051125095656.19351.qmail@web52015.mail.yahoo.com> References: <20051125095656.19351.qmail@web52015.mail.yahoo.com> Message-ID: <43875BF5.5040308@multigig.com> Dear Malvin, > I am overjoyed... thanks for your help! The MAXPLANE > limitation was one of my greatest headache - because > very often, I had to re-assign layers to other > planes... which was very dangerous. Presumably you will be even more overjoyed to know that I have an actual fix for the error in version 7.3.112, which I just posted to the opencircuitdesign.com website. As mentioned in the last email, this is the "simple solution" that allows correct behavior for up to 64 planes, making it consistent with the definition of MAXPLANES. I don't know if I caught all the places where plane masks are defined, but I assume any omissions will be found and corrected within a couple of revisions. Please let me know if you find any remaining problems with magic's behavior handling a large number of defined planes. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim.edwards at multigig.com Wed Nov 30 10:18:50 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:23 2008 Subject: [Magic-dev] Re: Magic MAXPLANES In-Reply-To: <20051130030332.89556.qmail@web52006.mail.yahoo.com> References: <20051130030332.89556.qmail@web52006.mail.yahoo.com> Message-ID: <438DED0A.3030000@multigig.com> Dear Malvin, > 1. Sorry for taking so long, I had some problems > compiling on Linux with my options. I manage to > install in Cygwin without-tcl (as a testcase). But in > Linux RH7.3, I had to compile with-tcl before it is > able to run properly, otherwise running magic > without-tcl will yield the following message (not sure > if I messed up somewhere): > > X Error of failed request: BadValue (integer > parameter out of range for operation) > Major opcode of failed request: 53 (X_CreatePixmap) > Value in failed request: 0x7 > Serial number of failed request: 1991 > Current serial number in output stream: 2618 > > The last working version I tried without this problem > was rev7.3.74. This is less critical, so I will look at it sometime later when I get the chance. Most likely this is my error, not yours, although sometimes the error can actually be the X server. XCreatePixmap errors, however, usually arise from a timing problem, in which the call is made before the target window is mapped. Which means it could be difficult to duplicate the error. > 2. Also, installing rev7.3.112 in RH7.3, gave: > CIFsee.c: In function `cifSeeFunc': > CIFsee.c:78: parse error before `char' > CIFsee.c:88: `text' undeclared (first use in this > function) > CIFsee.c:88: (Each undeclared identifier is reported > only once > CIFsee.c:88: for each function it appears in.) Type declaration inside a code block. . . a C++ syntax that my compiler accepts without question, but others balk at. > 3. I've found 1 declaration at line 304 > database/DBconnect.c and changed the datatype to > PlaneMask instead of unsigned integer; Upon > recompilation, I was still unable to select/pick paint > under cursor. Were you able to recreate the problem > with the scmos9m_planes.tech testcase? I traced > through the routines using the dlong PlaneMask you > redefined and cannot find any more abnormalities. I corrected this missing instance, and using your testcase, managed to track down the problem with selections, which was that the definition (in database/database.h): #define PlaneNumToMaskBit(p) (1 << (p)) had to be changed to: #define PlaneNumToMaskBit(p) ((PlaneMask)1 << (p)) Otherwise, the compiler assumes type 32-bit integer for the "1" and typecasts (p) DOWN to 32-bits to match it, rather than vice versa. Compilers never cease to amaze me in their occasional complete lapse of intelligence. The fixes are in 7.3.113, which appears to run correctly on your testcase (assuming a Tcl/Tk-enabled compilation). Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim at multigig.com Wed Nov 30 14:01:48 2005 From: tim at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:23 2008 Subject: [Magic-dev] subcell CIF/GDS interactions Message-ID: <438E214C.40205@opencircuitdesign.com> I have just posted magic-7.3.114. This revision fixes an error that has been a longtime problem in magic, and is actually a rather trivial fix. This means that although I have applied the fix to 7.3, someone (else, preferably) should generate a patch against version 7.1. Previously, arrayed subcells that were too narrow and closely spaced would generate a warning about possible bad CIF/GDS interaction between non-neighboring cells with the potential to write bad CIF/GDS output. This was particularly bad in that the resulting layers can't be seen with the "cif see" command (although you can see them with the "cif *array" command, except that the command option isn't widely advertised). Usually this does not result in an actual output error, so I have been used to ignoring the warning message. However, every now and then I get real erroneous output. Tracking one of these instances down, I realized that it happens when any cif layer in the tech file has a "grow" distance larger than the cell width in the direction of the arrayed instances. Interactions are then found between the 1st and 3rd cells in the array (or 4th, or more). Magic optimizes the search for inter- array interactions by finding interactions between the first two cells and copying them enough times to cover the array. This assumes that the interactions are only between the first two cells of the array. If interaction paint has been generated relative to, say, the 3rd cell in the array, this gets copied off the end of the array. The solution is actually quite simple: reduce the size of the array to at most 2x2 before computing interactions, and then restore the original size of the array at the end. The function cifHierArrayFunc() in cif/CIFhier.c is otherwise unchanged from magic version 7.1 and can simply replace the original. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim@opencircuitdesign.com | | Open Circuit Design, Inc. | web: http://opencircuitdesign.com | | 22815 Timber Creek Lane | phone: (301) 528-9364 | | Clarksburg, MD 20871-4001 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim.edwards at multigig.com Thu Dec 1 13:10:45 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:23 2008 Subject: [Magic-dev] Re: A magic bug In-Reply-To: <20051201134150.DLK37370@isrmail.isr.umd.edu> References: <20051201134150.DLK37370@isrmail.isr.umd.edu> Message-ID: <438F66D5.4020809@multigig.com> Eric Liu Wong wrote: > I think I found a bug in magic about highlighting connections. My magic system is quite recent. Please open the > attachment and see the readme file for detailed information on my system, techfile and the way to reproduce the > problem. In or around line 701 of database/DBcontact.c, change: if (TTMaskEqual(rMask, DBResidueMask(ctype))) to if (TTMaskIntersect(rMask, DBResidueMask(ctype))) I think my original assumption was that overlapping contacts would be replaced by a stacking type, but when the contacts are in separate subcells, the contacts can overlap without generating a stacking type. So, TTMaskEqual() was producing a mask of non-connecting types that included a lot of types that really connect to the contact. I didn't investigate why magic hangs and starts gobbling memory; the connectivity search routine is known to be very tricky and is very hard to debug. When the above fix seemed to fix the problem, I stopped investigating it further. If you find any other problems, let me know. I have posted the fix as part of magic-7.3.115. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From clint.kelly at gmail.com Fri Dec 2 17:34:05 2005 From: clint.kelly at gmail.com (Clint Kelly) Date: Thu Oct 30 14:33:23 2008 Subject: [Magic-dev] ext2spice documentation Message-ID: <20eabb880512021434r73ba87ecwc7d2fcaa2ab5e7aa@mail.gmail.com> Hi. I was wondering if there is any documentation on how ext2spice works. Specifically, I am curious how ext2spice uses the information in extract files to figure out what the area and perim values are for fets. Is there a document that describes this? The only thing I could find in the magic distribution was ext2spice.c... :) -Clint From tim.edwards at multigig.com Fri Dec 2 17:26:15 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:23 2008 Subject: [Magic-dev] ext2spice documentation In-Reply-To: <20eabb880512021434r73ba87ecwc7d2fcaa2ab5e7aa@mail.gmail.com> References: <20eabb880512021434r73ba87ecwc7d2fcaa2ab5e7aa@mail.gmail.com> Message-ID: <4390F437.5050806@multigig.com> Dear Clint, > Hi. I was wondering if there is any documentation on how ext2spice > works. Specifically, I am curious how ext2spice uses the information > in extract files to figure out what the area and perim values are for > fets. Is there a document that describes this? The only thing I > could find in the magic distribution was ext2spice.c... :) Try the following: 1. doc/ext2spice.1 (man page, in the distribution) 2. Magic tutorial #8 (http://opencircuitdesign.com/magic "Documentation") 3. Magic maintainer's manual #2, on the "extract" section (same location as above) 4. http://opencircuitdesign.com/magic/ go to "Documentation" then "Magic Command Reference" then click on "extract" and "ext2spice" for the online HTML documentation. The source code is always the ultimate documentation, but note that most of the real work done by "ext2spice" is actually in the "extflat" directory. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From donovanlee at gctsemi.com Sat Dec 3 17:27:23 2005 From: donovanlee at gctsemi.com (Donovan Lee) Date: Thu Oct 30 14:33:23 2008 Subject: [Magic-dev] some problem in linux system Message-ID: Hi.. I am donovan, circuit designer. I have used magic ver. 7.3.111 in radhat linux system. Recently, I have encountered some problem.. 1. when I use addpath command, do I always add path in absolutely path? (like /home/data/magic/layout1) . As you knows, in unix system, we can use relative path(like ../layout1) 2. when I enter 'calma write' command, after commanding, the magic program went always down (something like lock-down). So, whenever that case, I use ctrl-z in terminal where I start magic, and kill the processs. Anyone who know that case? Thank you in advance. Regards Donovan Ps. Sorry for my poor English ^^ -----Original Message----- From: magic-dev-bounces@csl.cornell.edu [mailto:magic-dev-bounces@csl.cornell.edu] On Behalf Of R. Timothy Edwards Sent: Saturday, December 03, 2005 10:26 AM To: Clint Kelly Cc: magic-dev@csl.cornell.edu Subject: Re: [Magic-dev] ext2spice documentation Dear Clint, > Hi. I was wondering if there is any documentation on how ext2spice > works. Specifically, I am curious how ext2spice uses the information > in extract files to figure out what the area and perim values are for > fets. Is there a document that describes this? The only thing I > could find in the magic distribution was ext2spice.c... :) Try the following: 1. doc/ext2spice.1 (man page, in the distribution) 2. Magic tutorial #8 (http://opencircuitdesign.com/magic "Documentation") 3. Magic maintainer's manual #2, on the "extract" section (same location as above) 4. http://opencircuitdesign.com/magic/ go to "Documentation" then "Magic Command Reference" then click on "extract" and "ext2spice" for the online HTML documentation. The source code is always the ultimate documentation, but note that most of the real work done by "ext2spice" is actually in the "extflat" directory. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ _______________________________________________ magic-dev mailing list magic-dev@vlsi.cornell.edu http://vlsi.csl.cornell.edu/mailman/listinfo/magic-dev From tim.edwards at multigig.com Sat Dec 3 17:44:50 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:23 2008 Subject: [Magic-dev] Re: some problem in linux system In-Reply-To: References: Message-ID: <43924A12.2020504@multigig.com> Dear Donovan, > Hi.. I am donovan, circuit designer. > I have used magic ver. 7.3.111 in radhat linux system. > Recently, I have encountered some problem.. > > 1. when I use addpath command, do I always add path in absolutely path? > (like /home/data/magic/layout1) . > As you knows, in unix system, we can use relative path(like ../layout1) Yes, all paths are interpreted as relative to the current working directory. So all the examples above work as expected. > 2. when I enter 'calma write' command, after commanding, the magic > program went always down (something like lock-down). > So, whenever that case, I use ctrl-z in terminal where I start magic, > and kill the processs. Anyone who know that case? What actually happened depends on a number of things. Usually, it indicates a bug in the code that causes an infinite loop during a search of the tile plane database. Generally speaking, these problems are difficult to debug. I can usually track down the problem, but I need an example layout that exhibits the problem, the technology file used, and the set of commands that produced the hang state. > Ps. Sorry for my poor English No problem. Open source software is for everyone, not just English speakers. I don't know why everyone apologizes to me; I should be the one apologizing for providing documentation only in English. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From tim.edwards at multigig.com Tue Dec 6 10:53:20 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:24 2008 Subject: [Magic-dev] Re: Problem with Installation of Magic 7.3 In-Reply-To: <1133894007.4395d977d455b@imapwww.epfl.ch> References: <1133816345.4394aa196c5c4@imapwww.epfl.ch> <43951012.4040706@multigig.com> <1133857407.43954a7f15a08@imapwww.epfl.ch> <4395B678.2000000@multigig.com> <1133894007.4395d977d455b@imapwww.epfl.ch> Message-ID: <4395DE20.7010004@multigig.com> Dear Uroschanit, > After I tried to install Magic 7.3 to my Ubuntu Linux, I've found some problems > during the installtion. After I created a directory "/usr/local/src" and then > copied the tar file into this directory and extracted it, I ran the command > "./configure" without any option, it gave the following message: > configure: error: M4 is required I do believe that those who create linux distributions deliberately want to cause trouble for us software developers! Hopefully you can find the package for "m4" in the ubuntu linux install and setup, because it is necessary. I am CC'ing this email to magic-dev, because if there are distributions whose setups are beginning to not include m4, this is bound to show up again and again. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From iltseng at seed.net.tw Wed Dec 7 13:37:54 2005 From: iltseng at seed.net.tw (iltseng@seed.net.tw) Date: Thu Oct 30 14:33:24 2008 Subject: [Magic-dev] compile & install Magic 7.3.115 on Solaris 10 Message-ID: <27927730.15971133933874713.JavaMail.root@wm11.seed.net.tw> Dear Magic users/developers, I was trying to compile and install Magic 7.3.115 on Solaris 10. Since I do not have the root password of the machine, I can only install Magic in my local directories. Therefore, I used the --prefix option for the configure command, followed by typing "make" and then "make install". However, I got some error messages during "make install". Please see the messages below: $ pwd /home/username/Magic_7.3.115/magic $ ./configure --prefix=/home/username/Magic_7.3.115/magic /* Everything seemed fine. */ $ make /* Everything seemed fine. */ $ make install --- installing to /home/username/Magic_7.3.115/magic make[2]: *** No rule to make target `../graphics/libgraphics.o', needed by `tclmagic.so'. Stop. $ cd bin $ ./magic ./magic: MAGIC_WISH=/usr/local/bin/wish: is not an identifier Can anyone shed me some light? Thanks in advance, I-Lun From tim.edwards at multigig.com Wed Dec 7 14:17:21 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:24 2008 Subject: [Magic-dev] compile & install Magic 7.3.115 on Solaris 10 In-Reply-To: <27927730.15971133933874713.JavaMail.root@wm11.seed.net.tw> References: <27927730.15971133933874713.JavaMail.root@wm11.seed.net.tw> Message-ID: <43975F71.6070907@multigig.com> Dear I-Lun, Looks like we have two separate problems here. > I was trying to compile and install Magic 7.3.115 on Solaris 10. Since I do not have the root password of the machine, I can only install Magic in my local directories. Therefore, I used the --prefix option for the configure command, followed by typing "make" and then "make install". However, I got some error messages during "make install". Please see the messages below: > > $ pwd > /home/username/Magic_7.3.115/magic > > $ ./configure --prefix=/home/username/Magic_7.3.115/magic > /* Everything seemed fine. */ > > $ make > /* Everything seemed fine. */ > > $ make install > --- installing to /home/username/Magic_7.3.115/magic > make[2]: *** No rule to make target `../graphics/libgraphics.o', needed by `tclmagic.so'. Stop. The actual error should show up in the "make.log" file. Please send me the make.log file or email me the relevant lines showing what the error was. > $ cd bin > > $ ./magic > ./magic: MAGIC_WISH=/usr/local/bin/wish: is not an identifier I've had problems before with the Solaris version of "sh", and this looks like one of those cases. Apart from the fact that magic never finished compiling all the code in the graphics subdirectory, probably the scripts /usr/local/bin/magic is not going to work until some changes are made for compatibility with Solaris. The error is almost certainly either line 15 or line 16 of /usr/local/bin/magic: DNULL= export MAGIC_WISH=/usr/local/bin/wish My best guess is that the syntax of the "export" command is only correct for "bash" (Linux doesn't have the original "sh", only the newer "bash"). Try changing the line to: MAGIC_WISH=/usr/local/bin/wish export MAGIC_WISH If this works for you, please let me know so I can change the distribution. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From iltseng at seed.net.tw Thu Dec 8 09:59:33 2005 From: iltseng at seed.net.tw (I-Lun Tseng) Date: Thu Oct 30 14:33:26 2008 Subject: [Magic-dev] compile & install Magic 7.3.115 on Solaris 10 References: <27927730.15971133933874713.JavaMail.root@wm11.seed.net.tw> <43975F71.6070907@multigig.com> Message-ID: <004a01c5fb8a$463eb320$0401010a@TOMDESKTOP> Dear Tim, Many thanks for your reply. First, I have attached make.log file in this mail. Second, modifying the "export" command to what you have said does solve the second problem. Best regards, I-Lun ----- Original Message ----- From: "R. Timothy Edwards" To: Cc: Sent: Thursday, December 08, 2005 8:17 AM Subject: Re: [Magic-dev] compile & install Magic 7.3.115 on Solaris 10 > Dear I-Lun, > > Looks like we have two separate problems here. > >> I was trying to compile and install Magic 7.3.115 on Solaris 10. Since I >> do not have the root password of the machine, I can only install Magic in >> my local directories. Therefore, I used the --prefix option for the >> configure command, followed by typing "make" and then "make install". >> However, I got some error messages during "make install". Please see the >> messages below: >> >> $ pwd >> /home/username/Magic_7.3.115/magic >> >> $ ./configure --prefix=/home/username/Magic_7.3.115/magic >> /* Everything seemed fine. */ >> >> $ make >> /* Everything seemed fine. */ >> >> $ make install >> --- installing to /home/username/Magic_7.3.115/magic >> make[2]: *** No rule to make target `../graphics/libgraphics.o', needed >> by `tclmagic.so'. Stop. > > The actual error should show up in the "make.log" file. Please send me > the make.log file or > email me the relevant lines showing what the error was. > >> $ cd bin >> >> $ ./magic >> ./magic: MAGIC_WISH=/usr/local/bin/wish: is not an identifier > > I've had problems before with the Solaris version of "sh", and this > looks like one of those cases. Apart from the fact that magic never > finished compiling all the code in the graphics subdirectory, probably > the scripts /usr/local/bin/magic is not going to work until some changes > are made for compatibility with Solaris. The error is almost certainly > either line 15 or line 16 of /usr/local/bin/magic: > > DNULL= > export MAGIC_WISH=/usr/local/bin/wish > > My best guess is that the syntax of the "export" command is only correct > for "bash" (Linux doesn't have the original "sh", only the newer "bash"). > Try changing the line to: > > MAGIC_WISH=/usr/local/bin/wish > export MAGIC_WISH > > If this works for you, please let me know so I can change the > distribution. > > Regards, > Tim > > +--------------------------------+-------------------------------------+ > | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | > | MultiGiG, Inc. | web: http://www.multigig.com | > | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | > | Scotts Valley, CA 95066 | cell: (240) 401-0616 | > +--------------------------------+-------------------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: make.log Type: application/octet-stream Size: 340715 bytes Desc: not available Url : http://vlsi.csl.cornell.edu/pipermail/magic-dev/attachments/20051208/8bbe88fd/make.obj From iltseng at seed.net.tw Thu Dec 8 19:50:33 2005 From: iltseng at seed.net.tw (I-Lun Tseng) Date: Thu Oct 30 14:33:26 2008 Subject: [Magic-dev] problems with Magic Tutorial #8: ext2sim, extresis Message-ID: <003001c5fbdc$d59adc40$0401010a@TOMDESKTOP> Dear Magic users/developers, I am having some problems while going through Magic Tutorial #8. In section 4.2.1 - Tutorial Introduction on page 6, I typed the following commands according to the tutorial: %:load tut8r %:extract Extracting tut8r into tut8r.ext: %:ext2sim tut8r Auto-loading EXTTOSIM module exttosim finished. %:extresis tolerance 10 %:extresis Cannot open file (UNNAMED).sim (At this time, I use a box to cover the whole layout in the layout window.) %:extresis Cannot open file tut8r.nodes The tutorial says that "tut8r.sim", "tut8r.nodes", and "tut8r.al" will be produced after the "ext2sim" command. However, I saw that only "tut8r.sim" was generated. Does anyone have similar problems? Thanks in advance, I-Lun Tseng From tim.edwards at multigig.com Thu Dec 8 10:31:21 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:26 2008 Subject: [Magic-dev] problems with Magic Tutorial #8: ext2sim, extresis In-Reply-To: <003001c5fbdc$d59adc40$0401010a@TOMDESKTOP> References: <003001c5fbdc$d59adc40$0401010a@TOMDESKTOP> Message-ID: <43987BF9.2000007@multigig.com> Dear I-Lun, > %:extresis > Cannot open file (UNNAMED).sim This appears to be a subtle bug in magic version 7.3---the "load" command does not transfer the box to the new layout, so until you click on the window somewhere, magic references a lot of commands to the cell that previously contained the box (which in this case is cell "(UNNAMED)"). I will fix this in the distribution. > (At this time, I use a box to cover the whole layout in the layout window.) Just a single mouse click will fix the problem, as it transfers the box to the new layout. > %:extresis > Cannot open file tut8r.nodes > > > The tutorial says that "tut8r.sim", "tut8r.nodes", and "tut8r.al" will > be produced after the "ext2sim" command. However, I saw that only > "tut8r.sim" was generated. Does anyone have similar problems? This is a magic-7.3 behavior that has not been corrected in the tutorial. Magic-7.3 does *not* create the extra files (.nodes, etc.) by default, so prior to doing "ext2sim", you need to do the following two commands: ext2sim alias on ext2sim labels on I apologize for not getting around to updating the tutorials. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From micktooher at yahoo.com Sat Dec 10 15:09:07 2005 From: micktooher at yahoo.com (mick tooher) Date: Thu Oct 30 14:33:26 2008 Subject: [Magic-dev] Crash during "save layout" Message-ID: <20051210230907.87914.qmail@web54109.mail.yahoo.com> Hi Tim, I've just tried moving from the magic-7.3.116 version from magic-7.3.99 version. I read in a gds file and clicked "save layout--> write" menu command and magic crached with the following message *** glibc detected *** double free or corruption (!prev): 0x08428e30 *** I retried with "save layout--> autowrite" menu command and it also crashed. I reverted to the magic-7.3.99 version and tried again and everything worked fine. I'm using Mandriva 2005 with gcc-3.4.3-7mdk and glibc-2.3.4-8mdk. Cheers, Mick __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From tim.edwards at multigig.com Mon Dec 12 20:13:43 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:26 2008 Subject: [Magic-dev] Crash during "save layout" In-Reply-To: <439E4344.7040806@austin.rr.com> References: <20051210230907.87914.qmail@web54109.mail.yahoo.com> <439E4344.7040806@austin.rr.com> Message-ID: <439E4A77.5000104@multigig.com> Erwin J. Prinz wrote: > I see the same issue on magic 7.3.116, on a fully upgraded Fedora Core > 4, with gcc-4.0.2-8.fc4, and glibc-2.3.5-10.3. I have, following the > instructions in the magic 7.2 page, used gdb and will separately mail > the output to Tim to not clutter the mailing list. Sorry, I should have CC'd my original reply. I posted a bad version of the source where I ran an experiment and reverted all lines back to the original except for one that I missed. Of course, that line happened to be the critical one that gets executed every time you run the "write" command. . . The offending line is line 1384 for commands/CmdTZ.c: freeMagic(prompt); Remove it and recompile, and everything will run smoothly. Really, you guys are much too on top of things. I had the bad code posted for less than a day before I overwrote it with the corrected version, and some of you already downloaded and compiled it. . . obviously I have to be more careful what I post. Fortunately all the disclaimers are in place. Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+ From ejprinz at austin.rr.com Mon Dec 12 21:43:00 2005 From: ejprinz at austin.rr.com (Erwin J. Prinz) Date: Thu Oct 30 14:33:26 2008 Subject: [Magic-dev] Crash during "save layout" In-Reply-To: <20051210230907.87914.qmail@web54109.mail.yahoo.com> References: <20051210230907.87914.qmail@web54109.mail.yahoo.com> Message-ID: <439E4344.7040806@austin.rr.com> Mick & Tim: I see the same issue on magic 7.3.116, on a fully upgraded Fedora Core 4, with gcc-4.0.2-8.fc4, and glibc-2.3.5-10.3. I have, following the instructions in the magic 7.2 page, used gdb and will separately mail the output to Tim to not clutter the mailing list. Best regards, Erwin From graham.petley at vlsitechnology.org Wed Dec 14 04:56:51 2005 From: graham.petley at vlsitechnology.org (Graham Petley) Date: Thu Oct 30 14:33:26 2008 Subject: [Magic-dev] Extracted capacitance values in Magic 7.2 and 7.3 Message-ID: <20051214125652.75447.qmail@web209.biz.mail.re2.yahoo.com> Hi, I'm upgrading from magic 7.2.70 to 7.3.117. I've noticed differences in the values of extracted capacitors using exttospice in the two programs, as shown below: C6 a vdd 0.023f *0.025 C0 a vss 0.031f *0.034 C19 a vss 0.029f *0.027 C2 a b 0.177f *0.192 C9 n1 a 0.225f *0.273 C12 a z 0.020f *0.020 The values after the * are 7.2 and before are 7.3. I've seen from the revision log that many changes have occured with the extract. Would this explain the discrepancies, or should the extracted cap values be unchanged? I think that in 7.2 the extract didn't take account of any layer over or undersizing as defined in the cifoutput section. If so the 7.2 values above are wrong by a small amount. I don't know whether 7.3 extract fixes this. If the extracted caps should be the same, I'll create some test circuits to try to find the origin of the discrepancies. Best regards, Graham Petley From john.barry at tyndall.ie Wed Dec 14 18:18:26 2005 From: john.barry at tyndall.ie (John Barry) Date: Thu Oct 30 14:33:26 2008 Subject: [Magic-dev] ext2spice & subcircuits working? Message-ID: <43A061F2.9030507@tyndall.ie> Hi, I am using Magic 7.3.74 and I am experimenting with extract/ext2spice with "subcircuits on". Here is what I find In the spice output of a cell containing a just 3 subcells (both root and subcells have port definitions) 1) I see no subcircuit calls to subcells. However when I remove port definition of root cell the subcircuit calls appear. 2) I see internodal caps from one of subcells duplicated in the root cell spice output John D Barry -- _____________________________________ John D Barry, Design Technology Evaluation Group, Tyndall National Institute, Lee Maltings, Prospect Row, Cork, Ireland. tel: +353-21-4904240 fax: +353-21-4904058 Web: www.tyndall.ie/industry/DTE.html _____________________________________ From fang at csl.cornell.edu Wed Dec 14 15:03:54 2005 From: fang at csl.cornell.edu (David Fang) Date: Thu Oct 30 14:33:27 2008 Subject: [Magic-dev] magic-7.1 CVS snapshot [branch] Message-ID: <20051214145114.F67962-100000@maxwell.csl.cornell.edu> Magic-users, I've posted a snapshot of a much cleaned-up magic-7.1 at: http://www.csl.cornell.edu/~fang/sw/magic-7.1-osx.html There are no modifications that change the behavior of the code relative to CVS HEAD, just major clean-ups to make it happier and quieter with newer and stricter compilers. (What good is 'stable' legacy code that doesn't survive the times?) If you've used 7.1 before (or attempted), please give this pre-release a shot and report problems to magic-hackers. After this series of clean-up, I'd like to *attempt* to bring the configuration system under autoconf control, to maximize survivability and portability. Anyone who's run "make config" knows exactly what I'm talking about. David Fang Computer Systems Laboratory Electrical & Computer Engineering Cornell University http://www.csl.cornell.edu/~fang/ -- (2400 baud? Netscape 3.0?? lynx??? No problem!) From iltseng at seed.net.tw Fri Dec 16 12:16:06 2005 From: iltseng at seed.net.tw (I-Lun Tseng) Date: Thu Oct 30 14:33:27 2008 Subject: [Magic-dev] Magic Tutorial #11 Message-ID: <001001c601e6$acd3def0$0401010a@TOMDESKTOP> Dear Magic users, While I was going through Magic Tutorial #11, I was stuck on page 2. This is because that I could not find where the program "presim" was. Also, the Magic command ":rsim" could not be found. Does anybody know why this happens? Thanks in advance, I-Lun Tseng From tim.edwards at multigig.com Fri Dec 16 09:15:21 2005 From: tim.edwards at multigig.com (R. Timothy Edwards) Date: Thu Oct 30 14:33:27 2008 Subject: [Magic-dev] Magic Tutorial #11 In-Reply-To: <001001c601e6$acd3def0$0401010a@TOMDESKTOP> References: <001001c601e6$acd3def0$0401010a@TOMDESKTOP> Message-ID: <43A2F629.5040807@multigig.com> Dear I-Lun, > Dear Magic users, > > While I was going through Magic Tutorial #11, I was stuck on page 2. > This is because that I could not find where the program "presim" was. > Also, the Magic command ":rsim" could not be found. Does anybody know > why this happens? Because these commands correspond to magic-7.1 or earlier, or the non-Tcl version of magic 7.3, but not the Tcl-based magic version 7.3. Magic version 7.3 has a different interface to IRSIM, although similar. If you have IRSIM compiled and installed, then the command "irsim" in magic will start the IRSIM simulator. Both magic and IRSIM then run under the same interpreter, and commands for both can be entered on the magic command line. For details, see http://opencircuitdesign.com/irsim/ Regards, Tim +--------------------------------+-------------------------------------+ | Dr. R. Timothy Edwards (Tim) | email: tim.edwards@multigig.com | | MultiGiG, Inc. | web: http://www.multigig.com | | 100 Enterprise Way, Suite A-3 | phone: (831) 621-3283 | | Scotts Valley, CA 95066 | cell: (240) 401-0616 | +--------------------------------+-------------------------------------+