Re: Exportability of EDA industry from North America?

From: Chuck Harris (cf-NO-SPAM-harris_at_erols.com)
Date: 01/13/05


Date: Thu, 13 Jan 2005 11:57:45 -0500

Hi Stuart,

Stuart Brorson wrote:
> In sci.electronics.cad Chuck Harris <cf-NO-SPAM-harris@erols.com> wrote:

> : The gEDA system is a very nice idea... It is truly a shame that it
> : is packaged with insufficient thought to portability.
>
> I'm sorry to hear that you have problems installing gEDA. It seems to
> work for many other people. I am one of the active developers.
> Accordingly, I am always interested in specific bug reports so I can
> then fix problems, and robustify the application. Therefore, can you
> please be more specific? I'd be happy to fix whatever I can if I had
> some hard information.
>
> Particularly relevant info:
>
> * Linux distro & revision level
> * Installation flavor (i.e. RedHat comes in "personal", "workstation",
> "server", and so on. SuSE comes in "personal" and "professional").

RedHat 9, Workstation, upgraded to the latest fixes on FreshRPM's apt-get
repository.
>
> : It wants the
> : system libraries it uses to be stuffed in non standard places inorder for
> : it to find them. It doesn't recognize that Redhat, and some of the
> : other distributions use differing names for some of the normal system
> : libraries. (GTK+ 2 comes to mind)

Redhat 9 calls GTK+ 2.0 GTK2, but your configuration scripts are looking for
GTK+-2.0 So they don't find GTK2, and back down to GTK+ 1.2

Your scripts on the latest version of gSchem cannot find the dynamic links
for libstroke, or libgdg* , even though they are in /usr/local/lib (with
all the other libraries it did find):

$ ls /usr/local/lib/libst*

         /usr/local/lib/libstroke.a /usr/local/lib/libstroke.so.0
         /usr/local/lib/libstroke.la /usr/local/lib/libstroke.so.0.0.5
         /usr/local/lib/libstroke.so

$ ls /usr/local/lib/libgdg*
         /usr/local/lib/libgdgeda.a /usr/local/lib/libgdgeda.so.6
         /usr/local/lib/libgdgeda.la /usr/local/lib/libgdgeda.so.6.0.0
         /usr/local/lib/libgdgeda.so

$ ldd `which gschem`

         libstroke.so.0 => not found
         libgeda.so.22 => /home/chuck/gEDA/geda-install/lib/libgeda.so.22 (0x40033000)
         libguile.so.12 => /usr/lib/libguile.so.12 (0x4006f000)
         libguile-ltdl.so.1 => /usr/lib/libguile-ltdl.so.1 (0x400fc000)
         libcrypt.so.1 => /lib/libcrypt.so.1 (0x40103000)
         libgdgeda.so.6 => not found
         libpng12.so.0 => /usr/lib/libpng12.so.0 (0x40131000)
         libm.so.6 => /lib/tls/libm.so.6 (0x40154000)
         libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x40176000)
         libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x4019b000)
         libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x402e3000)
         libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x4031b000)
         libdl.so.2 => /lib/libdl.so.2 (0x4031f000)
         libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x40323000)
         libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4032b000)
         libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40339000)
         libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40418000)
         libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40421000)
         libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
         libgdgeda.so.6 => /usr/local/lib/libgdgeda.so.6 (0x40439000)
         libz.so.1 => /usr/lib/libz.so.1 (0x4046b000)
         libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x40479000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

>
> If you build it from source (or use the CD) the "configure" step takes
> care of all of this -- in principle. If it isn't working for you, we
> would like to fix it. Please report: Which system libs go in
> non-standard places, what are the non-standard places, and what
> method of installation are you using? Also, what type of system do
> you use (i.e. Linux distro)?

In the past, using source and ./configure, make, and make install, it did
do the right thing, but this latest 2004 release behaves differently.

>
> : If you want to install the gEDA system so it is available to all users on
> : a multiuser system, you have to give all of those users root privileges on
> : certain system directories...There is no excuse for that!
>
> Which system directories? And what method of installation?

This comes directly from one of the documentation file included with gEDA. If you
install using root, ./configure will put everything in the '/usr/local/' tree,
including all of the project files, and other files the user generates. I cannot
find the exact doc file where I found this written, but that file says that the
users must have write privileges on the /usr/local tree inorder to use the
system if it is installed that way. The author made it sound like something
that everyone would do... A very stupid windowsesque sort of thing.

>
> : All of the example designs are broken in such a way that they cannot find
> : the active components to put on the schematic.
>
> This is an interesting point. I can look into this. I don't know how
> the lib search paths are set in the examples. I believe they are
> configurable when you install from source, but if you are using a
> binary distro, then they might be hardcoded.

All of the transistors, diodes and IC's used in the example programs are
located in a subdirector or the individual example program. There is no
info present that explains how to encourage gSchem to connect the two.
Presumably that info would in the project file used for the project where
these examples reside... only no project files are included.

>
> : There are no examples or documents describing how the project manager is
> : supposed to work. Saying it is obvious isn't much help.
>
> True, certain things lack documentation. That problem is being
> worked, but ever-so-slowly. Please remember that gEDA is a volunteer
> effort, and getting engineers to document their stuff is not always
> easy. You probably know this.

I very much understand this. But at this time, it is well below the usual
level of documentation found in Gpl'd software.
>
> : The CDROM that was issued the other day is even worse than useless. It
> : chugs and churns, but it doesn't notice that it cannot find certain libraries,
> : and it just goes on like everything is ok. It also rebuilds and installs
> : the symbol libraries so many times I thought it was stuck in a loop.
>
> Again, what Linux distro & rev level are you using? The CD was tested
> on several modern Linux variants. In the CD's README are listed the
> systems which will and won't work. Did you read the README?

Absolutely! And I am running RedHat 9, a system that should work... All
the versions of my various tools are at or above the rev levels required.

The first time I ran the CDROM install, it built and installed the symbols
libraries at least 20 times before I killed the process. (I was getting
curious as to why it was taking so long, and why every hour or so I would
look at it and it was building the symbols yet again.)

>
> : Close, but not quite ready for prime time.
>
> With some work, and specific info about problems, it will become ever
> more polished over time. Keep in mind that generalized kvetching is
> cheap 'n easy, but offering bug details will help everybody.

I have a definite desire for gEDA to succeed, as I think
GPL'd software is the future. But at this stage, gEDA 20041228
shouldn't have been released to the public. If a guy like me who
has been working with unix for 30 years, and linux since the first
slackware distribution can't make your package work, how much chance
does anyone else have?

-Chuck



Relevant Pages

  • Re: Fwd: GEDA discussion on fedora-list
    ... Subject: GEDA discussion on fedora-list ... attempts to install the entire suite of gEDA tools onto an aribtrary ... January Linux Journal had an article, ... The original gEDA project was limited to a schematic capture program, ...
    (Fedora)
  • Fwd: GEDA discussion on fedora-list
    ... Subject: GEDA discussion on fedora-list ... attempts to install the entire suite of gEDA tools onto an aribtrary ... January Linux Journal had an article, ... The original gEDA project was limited to a schematic capture program, ...
    (Fedora)
  • Re: Looking for Circuit CAD and simulation (optinal) for Fedora!
    ... Fedora environment for it's filesystem structure ... Can anyone tell me how to properly install gEDA ... There are a bunch of gEDA packages in the review queue for Fedora Extras. ...
    (Fedora)
  • Re: Looking for Circuit CAD and simulation (optinal) for Fedora!
    ... and Fedora FC5 does not autorun. ... Fedora environment for it's filesystem structure ... Can anyone tell me how to properly install gEDA ...
    (Fedora)
  • Re: Exportability of EDA industry from North America?
    ... > I'm sorry to hear that you have problems installing gEDA. ... In the past, using source and ./configure, make, and make install, it did ... This comes directly from one of the documentation file included with gEDA. ... including all of the project files, and other files the user generates. ...
    (sci.electronics.cad)