[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
RE: gEDA-user: Help request

To: "gEDA user mailing list" <geda-user@xxxxxxxxxxxxxx>
Subject: RE: gEDA-user: Help request
From: "David Carr" <dc@xxxxxxxxx>
Date: Fri, 16 Jun 2006 13:50:13 -0500 (CDT)
Delivered-to: archiver@seul.org
Delivered-to: geda-user@moria.seul.org
Delivery-date: Fri, 16 Jun 2006 14:53:26 -0400
Importance: Normal
In-reply-to: <DE87437FE365CB458C265EA3D73B6F1D0157EB2E@xbc-mail1.xantrex.com>
List-archive: <http://www.seul.org/pipermail/geda-user>
List-help: <mailto:geda-user-request@moria.seul.org?subject=help>
List-id: gEDA user mailing list <geda-user.moria.seul.org>
List-post: <mailto:geda-user@moria.seul.org>
List-subscribe: <http://www.seul.org/cgi-bin/mailman/listinfo/geda-user>, <mailto:geda-user-request@moria.seul.org?subject=subscribe>
List-unsubscribe: <http://www.seul.org/cgi-bin/mailman/listinfo/geda-user>, <mailto:geda-user-request@moria.seul.org?subject=unsubscribe>
References: <DE87437FE365CB458C265EA3D73B6F1D0157EB2E@xbc-mail1.xantrex.com>
Reply-to: gEDA user mailing list <geda-user@xxxxxxxxxxxxxx>
Sender: geda-user-bounces@xxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.4
Adrian.

I think you're making this more complicated than it needs to be.  I
somewhat suspect that somewhere in trying to fix this problem it actually
got worse.

Try something along these lines:
-Delete the copy of the gEDA sources you're trying to compile
-Grab a copy of libgeda from CVS or from the download page
-Remove any special lines you've added to .bashrc and any other extra
environment variables you've added.  If you have anything that resembles a
standard Ubuntu install they won't be needed.
-Unpack and cd into the libgeda directory
-Run ./autogen.sh
-Run ./configure --prefix=/usr
-Run make

Let me know what happens at this point.  If something fails, one of a few
things could be wrong.  Firstly, you could have installed a broken version
of a library or tool.  For example I noticed that it looks like you
installed readline using the LFS instructions.  Thats probably not the
best idea, most software you'll ever need (including readline) will be in
Ubuntu's package repositories.  Just installing things from source using
random instructions often results in broken systems because you end up
with multiple versions of the software installed in different places at
the same time.  Alternately, you'll end up with things in a mix of /usr
/usr/local /opt, etc which also leads to brokeness.

If you need software, always look first in synaptic or apt-get.  If you
absolutely cannot find a package for what you need, use the --prefix=/usr
option when running configure.  This will make sure that files get put in
a location consistent with your Ubuntu system.

Also, if your environment variables are sufficently borked, it may be hard
to get them back to the stock configuration.  You might try creating a
temporary new user and try doing the compile using that user.  If you try
this, make sure you start with a virgin copy of the sources (ie: delete
your tree and unpack/download a clean copy).

This really isn't that hard on Ubuntu.  I just installed all of gEDA from
CVS a few days ago on my system.  After I had all the dependency packages
installed, I just did the ./autogen.sh, ./configure --prefix=/usr, make,
sudo make install process for each source and everything came out fine.

Hope this helps,
-David Carr

> Hi all,
>
> First, thanks you all for your response. Looks like I am the unlucky one
> or something is fishy with Ubuntu. I have checked as per Stuart
> recommendation the config.h.in file and it is there, but I have no clue if
> what is inside is right or not.
> automake --version -> automake (GNU automake) 1.4-p6
> autoconf --version -> autoconf (GNU autoconf) 2.59
> autoheader --version -> autoheader (GNU Autoconf) 2.59
> I have checked the missing dependencies suggested by David, the
> libgd2-noxpm-dev, nowebm, and libgdgeda-dev where the missing packages.
> Still, after I installed them I do have the same error:
>
> ...
> Making install in share
> make[2]: Entering directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/share'
> make[3]: Entering directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/share'
> make[3]: Nothing to be done for `install-exec-am'.
> /bin/sh ../mkinstalldirs /home/work/programs/gEDA/share/gEDA
>  /usr/bin/install -c -m 644 ./prolog.ps
> /home/work/programs/gEDA/share/gEDA/prolog.ps
> make[3]: Leaving directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/share'
> make[2]: Leaving directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/share'
> make[2]: Entering directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
> make[3]: Entering directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
> cd . && autoheader
> make[3]: Leaving directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
> cd . \
>           && CONFIG_FILES= CONFIG_HEADERS=[config.h] \
>              /bin/sh ./config.status
> config.status: creating [config.h]
> config.status: error: cannot find input file: [config.h].in
> make[2]: *** [stamp-h] Error 1
> make[2]: Leaving directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory
> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
> make: *** [libgeda_install] Error 2
>
> real    2m44.669s
> user    1m27.460s
> sys     0m22.847s
>
>
> I do realize the smart PATH work around from /root/.bashrc is just
> useless. I have seven new lines at the end of .bashrc:
>
> #aditional required variables
> LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/work/programs/gEDA/lib
> PATH=$PATH:/home/work/programs/gEDA/bin
> PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/home/work/programs/gEDA/lib/pkgconfig
> export LD_LIBRARY_PATH
> export PATH
> export PKG_CONFIG_PATH
>
> When I am opening a shell and I am running:
>
> $source /root/.bashrc
> $echo $LD_LIBRARY_PATH
> $echo $PATH, and
> echo $PKG_CONFIG_PATH
>
> I am able to see the variables. If I am closing this shell and verify
> again with $echo ..., the variables are not any more there. Only after I
> am running $source /root/.bashrc again for any new shell I can see them. I
> suspect this is bad. I have no idea how to set PATH variables in Ubuntu.
>
> So, I switched to SUSE 10.1 AMD64. With not too much trouble (just
> installing some missing dependencies like texinfo) I was able to install
> the CVS version of gEDA. I was getting ready to celebrate when sadly I
> realized I am not out of the woods. I do have a similar problem with the
> stubborn PATH. I used the standard set of export commands:
>
> export LD_LIBRARY_PATH=/home/work/programs/gEDA/lib:$LD_LIBRARY_PATH
> export PATH=/home/work/programs/gEDA/bin:${PATH}
> export
> PKG_CONFIG_PATH=/home/work/programs/gEDA/lib/pkgconfig:$PKG_CONFIG_PATH
>
> Only for an open shell I can set the PATH if I am exporting the command.
> As soon as I am closing that shell I am not any more able to see the gEDA
> PATH. And wait, is coming with more presents: many components like pcb are
> not installed. There is no trace of pcb on .../gEDA/bin. If I am not
> wrong, somewhere on gEDA site is an advice to delete any trace of the
> whole gEDA package before attempting any kind of update and clean-install
> everything. So, to install pcb I need to do what?
>
> I do not wish  to be mean, I have a great desire to learn linux and gEDA.
> Still, I can not stop myself not to characterize the gEDA installation
> procedure as ferociously anti-user-friendly. I hope this is a random
> result and not a policy with some hidden rationale.
>
> Please help me to figure out how to make a complete installation from CVS
> (I suspect this is the place where I hope to find any new patch and the
> latest and greatest version). And also, I need help to get rid of the PATH
> beast.
>
> Could somebody tell me where to redirect my request for a painless
> one-click online update button inside of gEDA?
>
> With many thanks,
> Adrian Nania
>
> -----Original Message-----
> From: geda-user-bounces@xxxxxxxxxxxxxx on behalf of Phil Taylor
> Sent: Thu 6/15/2006 9:51 AM
> To: gEDA user mailing list
> Subject: Re: gEDA-user: Help request
>
>
> Adrian,
>
> David is right.  I have built a fair amount of software with Ubuntu and
> it gives you an experience not unlike debian.  I've had pretty good luck
> with it as a distro, and the IRC support channel is very active.
>
> Phil
>
>
> David Carr wrote:
>> Stuart,
>>
>> I'd like to contend your point that Ubuntu is bad for building
>> software.  In fact I'd say its just as good as every other linux
>> distribution, you just need a few packages that are not installed by
>> default.
>>
>> For best results using Ubuntu, install the following packages using
>> synaptic or apt-get.
>> (eg: sudo apt-get install build-essential)
>>
>> build-essential
>> automake
>> autoconf
>> libgd2-noxpm-dev
>> libgtk2.0-dev
>> guile-1.6-dev
>> nowebm
>> zlib1g-dev
>> libpng12-dev
>> libgdgeda-dev (optional, because you may also compile if from the gEDA
>> sources)
>>
>> I think that will do it but I may have missed one or two.  Feel free to
>> ask for more help.
>>
>> As for whether or not its a good thing that these packages are not
>> installed by default, I think that depends on who you ask.  I will say
>> though that the Ubuntu install requires only one CD, and my last Fedora
>> install required 5.  Downloading 5 700MB ISOs over a slow connection ---
>> now thats a *complete* waste of time and bandwidth.
>>
>> -David Carr
>>
>> Stuart Brorson wrote:
>>> Hi --
>>>
>>> 1.  I don't recommend using Ubuntu to build software.  Ubuntu doesn't
>>> come with the usual build tools (gcc, header files and all that)
>>> installed.  That's why you had all the dependecies to deal with.
>>>
>>> Ubuntu is good for e-mail and text editing, but not at all good for
>>> the task you are attempting.  Try Fedora Core or SuSE instead.  They
>>> are reasonably user friendly, and are *complete* distributions.
>>>
>>> 2.  If you insist on using Ubuntu, your problem here:
>>>
>>>
>>>> cd . \
>>>>           && CONFIG_FILES=3D CONFIG_HEADERS=3D[config.h] \
>>>>              /bin/sh ./config.status
>>>> config.status: creating [config.h]
>>>> config.status: error: cannot find input file: [config.h].in
>>>> make[2]: *** [stamp-h] Error 1
>>>>
>>>
>>> occurs because you are missing the file config.h.in in the directory
>>> /home/backups/src/electro/geda/sources/geda/devel/libgeda.  Look in
>>> the directory to verify that it exists.  If it doesn't, there was a
>>> problem in either downloading the CVS stuff, or in createing
>>> config.h.in.
>>> This file is processed by the automake stuff to create the header file
>>> config.h.  This might be an issue with your build tools.  Can you run
>>> the following commands:
>>> automake --version
>>> autoconf --version
>>> autoheader --version
>>>
>>> (Does autoheader return a version string?)
>>>
>>> Good luck!
>>>
>>> Stuart
>>>
>>>
>>>
>>>
>>>> Hi all,
>>>>
>>>> I am trying to build gEDA from CVS. I do have really hard time to
>>>> travel >>> thru the linux flavors jungle, I have installed five linux
>>>> versions >>> simultaneously only to be able to find one useful for
>>>> gEDA. Only
>>>> Ubuntu >>> was friendly enough for me, still I could not overcome a
>>>> few
>>>> problems. I >>> am not familiar with linux or gEDA but I am committed
>>>> to learn. Please >>> help me to figure out what I am doing wrong.
>>>> Looks like the
>>>> instruction >>> from the official gEDA site are for =93standard=94?
>>>> linux distro. On
>>>> my >>> Ubuntu Dapper (AMD K7 kernel with AMD64 processor) it is not
>>>> possible
>>>> to >>> make use of a normal =93export=94 instruction. Only with help
>>>> from:
>>>> http://www.ubuntuforums.org/showthread.php?t=3D141647
>>>> sudo gedit /root/bashrc (added lines):
>>>>
>>>> LD_LIBRARY_PATH=3D/home/work/programs/gEDA/lib:$LD_LIBRARY_PATH
>>>> PATH=3D/home/work/programs/gEDA/bin:${PATH}
>>>> PKG_CONFIG_PATH=3D/home/work/programs/gEDA/lib/pkgconfig:$PKG_CONFIG_PATH=
>>>>
>>>>
>>>> export LD_LIBRARY_PATH
>>>> export PATH
>>>> export PKG_CONFIG_PATH
>>>>
>>>> I was able to set somehow the PATH variables. I suspected this is
>>>> what I >>> was missing according to =93- Set shell variables.  *VERY
>>>> IMPORTANT*=94 >>> from the README file. Still my adventure of:
>>>> $time { make install;  }
>>>> is ending with:
>>>>
>>>> ...
>>>> Processing s_undo.texi ...
>>>> Processing s_toplevel.texi ...
>>>> Processing u_basic.texi ...
>>>> cd . \
>>>>           && makeinfo `echo libgedadoc.texi | sed 's,.*/,,'`
>>>> make[3]: Entering directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/docs'
>>>> make[3]: Nothing to be done for `install-exec-am'.
>>>> /bin/sh ../mkinstalldirs /home/work/programs/gEDA/info
>>>> mkdir /home/work/programs/gEDA/info
>>>>  /usr/bin/install -c -m 644 ./libgedadoc.info >>>
>>>> /home/work/programs/gEDA/info/libgedadoc.info
>>>> make[3]: Leaving directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/docs'
>>>> make[2]: Leaving directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/docs'
>>>> Making install in share
>>>> make[2]: Entering directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/share'
>>>> make[3]: Entering directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/share'
>>>> make[3]: Nothing to be done for `install-exec-am'.
>>>> /bin/sh ../mkinstalldirs /home/work/programs/gEDA/share/gEDA
>>>>  /usr/bin/install -c -m 644 ./prolog.ps >>>
>>>> /home/work/programs/gEDA/share/gEDA/prolog.ps
>>>> make[3]: Leaving directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/share'
>>>> make[2]: Leaving directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda/share'
>>>> make[2]: Entering directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
>>>> make[3]: Entering directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
>>>> cd . && autoheader
>>>> make[3]: Leaving directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
>>>> cd . \
>>>>           && CONFIG_FILES=3D CONFIG_HEADERS=3D[config.h] \
>>>>              /bin/sh ./config.status
>>>> config.status: creating [config.h]
>>>> config.status: error: cannot find input file: [config.h].in
>>>> make[2]: *** [stamp-h] Error 1
>>>> make[2]: Leaving directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
>>>> make[1]: *** [install-recursive] Error 1
>>>> make[1]: Leaving directory >>>
>>>> `/home/backups/src/electro/geda/sources/geda/devel/libgeda'
>>>> make: *** [libgeda_install] Error 2
>>>>
>>>> real    2m44.956s
>>>> user    1m11.153s
>>>> sys     0m22.148s
>>>>
>>>> Please help me here, I have no clue at all what is wrong. I tried to
>>>> >>> satisfy somehow the endless dependencies with:
>>>>
>>>> sudo apt-get install pkg-config libgtk2.0-0 libgtk2.0-dev
>>>> libpango1.0-0 >>> libpango1.0-dev groff \
>>>>     guile-1.6 guile-1.6-dev libglib2.0-0 libglib2.0-dev gcc g++ gcc
>>>> make >>> build-essential \
>>>>     autoconf automake libtool gettext tetex-extra tetex-base tetex-doc
>>>> >>> latex2html texinfo \
>>>>     libwxgtk2.6-0 libwxgtk2.6-dev python-wxgtk2.6 libxaw7 libxaw7-dev
>>>> >>> xaw3dg xaw3dg-dev \
>>>>     libxaw-headers libxpm-dev python-wxversion wx2.6-headers gperf
>>>> flex >>> bison tcl8.4 tcl8.4-dev \
>>>>     libdirectfb-0.9-22 libdirectfb-dev libgtk+2.0-directfb-dev >>>
>>>> libgtk+2.0-directfb0 gawk \
>>>>     libgtk+2.0-directfb0 libgtk+2.0-directfb-dev libglade2-dev
>>>>
>>>> In addition, with help from =93Linux From Scratch=94  I installed some
>>>> >>> more packages:
>>>>
>>>> # install readline
>>>> # /usr/local/include/readline/readline.h or >>>
>>>> /usr/include/readline/readline.h
>>>> cd /home/backups/src/linux
>>>> #wget -c ftp://ftp.cwru.edu/pub/bash/readline-5.1.tar.gz
>>>> tar -xzf readline-5.1.tar.gz
>>>> cd readline-5.1
>>>> sudo ./configure --prefix=3D/usr/local
>>>> sudo make
>>>> sudo make install
>>>> sudo ldconfig
>>>> cd /home/backups/src/linux
>>>> sudo rm -rf ./readline-5.1
>>>>
>>>> # install diffutils
>>>> cd /home/backups/src/linux
>>>> tar -xzf diffutils-2.8.1.tar.gz
>>>> cd diffutils-2.8.1
>>>> patch -Np1 -i ../diffutils-2.8.1-i18n-1.patch
>>>> touch man/diff.1
>>>> ./configure --prefix=3D/usr
>>>> make
>>>> make install
>>>> cd /home/backups/src/linux
>>>> rm -rf ./diffutils-2.8.1
>>>> # install diffutils END
>>>>
>>>> glibc-2.3.6 (too long to paste the content here, if anyone is
>>>> interested >>> just ask)
>>>>
>>>> Some packages I choose here are not required at all but I do not have
>>>> >>> the knowledge to fine tune this. I spend quite a few nights and
>>>> weekends >>> with trials and errors to get here. Anyway, I was able to
>>>> install the >>> gEDA from geda-install-20060124.iso image with no
>>>> problems. I had no >>> time yet to verify that my CD installation is
>>>> working with the twisted >>> =93export=94 for PATH.
>>>> To avoid this painful update process and to stretch my lifespan, could
>>>> >>> somebody out there implement some sort of =93live update=94 mouse
>>>> click >>> shortcut for a quick on-line update for the whole gEDA
>>>> package at once?
>>>> And another request. I would like to avoid this unbelievable mess of
>>>> >>> PATH. It will be possible to replace this mechanism with some sort
>>>> of >>> *ini or *cfg file inside of gEDA distro (or any other software
>>>> trick) >>> where the main interface program to look for any required
>>>> PATH,
>>>> instead >>> of relaying on the myth of  =93standard=94 linux?
>>>>
>>>> Thanks,
>>>> Adrian Nania
>>>>
>>>> _______________________________________________
>>>> geda-user mailing list
>>>> geda-user@xxxxxxxxxxxxxx
>>>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>>>
>>>>
>>>
>>> _______________________________________________
>>> geda-user mailing list
>>> geda-user@xxxxxxxxxxxxxx
>>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>>
>>
>> _______________________________________________
>> geda-user mailing list
>> geda-user@xxxxxxxxxxxxxx
>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>
>>
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Follow-Ups:
- Re: gEDA-user: Help request
  - From: Svenn Are Bjerkem
References:
- RE: gEDA-user: Help request
  - From: Adrian Nania
Prev by Author: Re: gEDA-user: Help request
Next by Author: gEDA-user: illegal layer-group string
Previous by thread: RE: gEDA-user: Help request
Next by thread: Re: gEDA-user: Help request
Index(es):
- Author
- Thread