Re: [Gnucap-devel] Gnucap-devel Digest, Vol 79, Issue 7

[Travis Ayres]

If work continues on gnucap, why isnt the web page updated?
On Apr 30, 2013 9:01 AM, <address@hidden> wrote:

> Send Gnucap-devel mailing list submissions to
>         address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.gnu.org/mailman/listinfo/gnucap-devel
> or, via email, send a message with subject or body 'help' to
>         address@hidden
>
> You can reach the person managing the list at
>         address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Gnucap-devel digest..."
>
>
> Today's Topics:
>
>    1. Re: [Help-gnucap] gnucap development snapshot     2013-04-23
>       (al davis)
>    2. Re: [Help-gnucap] gnucap development snapshot     2013-04-23
>       (address@hidden)
>    3. git repo proposal (Felix Salfelder)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 29 Apr 2013 21:30:12 -0400
> From: al davis <address@hidden>
> To: address@hidden, address@hidden
> Subject: Re: [Gnucap-devel] [Help-gnucap] gnucap development snapshot
>         2013-04-23
> Message-ID: <address@hidden>
> Content-Type: Text/Plain;  charset="iso-8859-1"
>
> On Thursday 25 April 2013, Felix Salfelder wrote:
> > On Thu, Apr 25, 2013 at 08:03:20PM -0400, al davis wrote:
> > > > didn't work for me.
> > >
> > >
> > >
> > > What didn't work?
> >
> >g++ -DUNIX -O2 -DNDEBUG -I. -I../include -I../../include -W mg_main.o
> mg_error.o mg_in.o mg_out_h.o mg_out_dump.o mg_out_common.o mg_out_dev.o
> mg_out_lib.o mg_out_model.o
> mg_out_root.o -o gnucap-modelgen -lgnucap  -rdynamic -L../../lib/O
> >../../lib/O/libgnucap.so: undefined reference to `dlerror'
> >../../lib/O/libgnucap.so: undefined reference to `dlopen'
> >../../lib/O/libgnucap.so: undefined reference to `dlclose'
> >collect2: error: ld returned 1 exit status
> >make[2]: *** [gnucap-modelgen] Error 1
> >make[2]: Leaving directory `/tmp/gnucap-2013-04-23/modelgen/O'
> >make[1]: *** [default] Error 2
> >make[1]: Leaving directory `/tmp/gnucap-2013-04-23/modelgen'
> >make: *** [gnucap] Error 2
>
> Try this ..
>
> Bug in lib/configure.
> Change this line.
>
> diff -r26.138 configure
> 28c28
> < echo "LIBS =  \\" >Make.libs
> ---
> > echo "LIBS = -ldl \\" >Make.libs
>
> Left out the library.
>
> It got removed in a "Muntzing".
>
> Although the error appeared when compiling "modelgen",
> the actual error is in "lib".
>
> The problem doesn't show on my system, apparently
> because of how the system libraries are organized.
> Test it and let me know how it works.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 30 Apr 2013 07:34:07 +0530
> From: "address@hidden" <address@hidden>
> To: al davis <address@hidden>
> Cc: address@hidden, gnucap <address@hidden>
> Subject: Re: [Gnucap-devel] [Help-gnucap] gnucap development snapshot
>         2013-04-23
> Message-ID:
>         <
> address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, Apr 30, 2013 at 7:00 AM, al davis <address@hidden> wrote:
>
> >
> > The problem doesn't show on my system, apparently
> > because of how the system libraries are organized.
> > Test it and let me know how it works.
> >
> >
> I can verify that it works.
>
> --
> Savant Krishna | Junior Undergraduate | Electrical Engineering | IIT Bombay
> bit.ly/sksavant
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 30 Apr 2013 09:23:00 +0200
> From: Felix Salfelder <address@hidden>
> To: address@hidden
> Subject: [Gnucap-devel] git repo proposal
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> Hi there.
>
> i've decided to base my work on (my clone of) the upstream branch inside
> the debian repository [1], where i'm going to track (at least) the
> release tarballs.
>
> moving files within a git repo is not a big deal after reading the
> manual a bit. i've split the tarball import into 2 commits. the first
> *only* moving files around. see the "mergetest" branch for a
> demonstration of what "git merge" magically does.
>
> this way i expect to be able to rebase my work to prior to the move and
> then *transparently* merge into commits/branches beyond the move.
>
> i propose to use this "upstream" branch, more precisely
>
>    git commit 1c31d8f2b3be2f3aee8bb751e34e16629b07c987
>          "import gnucap-2013-04-23.tar.gz"
>
> as "official" gnucap source base.
>
> regards
> felix
>
> PS: well, given that we don't switch to a toy RCS.
>
> [1] git://tool.em.cs.uni-frankfurt.de/git/gnucap_deb
>
>
>
> ------------------------------
>
> _______________________________________________
> Gnucap-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnucap-devel
>
>
> End of Gnucap-devel Digest, Vol 79, Issue 7
> *******************************************
>