[49020] trunk/dports/devel/gdb/Portfile

[Ryan Schmidt]

On Apr 1, 2009, at 19:56, dweber at macports.org wrote:

> Revision: 49020
>           http://trac.macports.org/changeset/49020
> Author:   dweber at macports.org
> Date:     2009-04-01 17:56:40 -0700 (Wed, 01 Apr 2009)
> Log Message:
> -----------
> -m "tweaks to the configure installation paths"

And you added a dependency on expat, and you added --enable-objc-gc  
to configure.args, so probably you need to bump the revision so  
everyone gets these changes (I assume this changes at least some  
files the port installs).


> Modified Paths:
> --------------
>     trunk/dports/devel/gdb/Portfile
>
> Modified: trunk/dports/devel/gdb/Portfile
> ===================================================================
> --- trunk/dports/devel/gdb/Portfile	2009-04-02 00:53:41 UTC (rev  
> 49019)
> +++ trunk/dports/devel/gdb/Portfile	2009-04-02 00:56:40 UTC (rev  
> 49020)
> @@ -11,18 +11,18 @@
>  description     GDB: The GNU Project Debugger
>
>  long_description \
> -GDB, the GNU Project debugger, allows you to see what is going on  
> `inside'\
> -another program while it executes -- or what another program was  
> doing at the\
> -moment it crashed.  GDB can do four main kinds of things (plus  
> other things\
> -in support of these) to help you catch bugs in the act:\
> -    * Start your program, specifying anything that might affect  
> its behavior.\
> -    * Make your program stop on specified conditions.\
> -    * Examine what has happened, when your program has stopped.\
> -    * Change things in your program, so you can experiment with  
> correcting\
> -     the effects of one bug and go on to learn about another.\
> -The program being debugged can be written in Ada, C, C++,  
> Objective-C,\
> -Pascal (and many other languages). Those programs might be  
> executing on\
> -the same machine as GDB (native) or on another machine (remote). GDB\
> +GDB, the GNU Project debugger, allows you to see what is going on  
> 'inside' \
> +another program while it executes -- or what another program was  
> doing at the \
> +moment it crashed.  GDB can do four main kinds of things (plus  
> other things \
> +in support of these) to help you catch bugs in the act: \
> +    a) start your program, specifying anything that might affect  
> its behavior, \
> +    b) make your program stop on specified conditions, \
> +    c) examine what has happened, when your program has stopped, \
> +    d) change things in your program, so you can experiment with  
> correcting \
> +       the effects of one bug and go on to learn about another. \
> +The program being debugged can be written in Ada, C, C++,  
> Objective-C, \
> +Pascal (and many other languages). Those programs might be  
> executing on \
> +the same machine as GDB (native) or on another machine (remote).  
> GDB \
>  can run on most popular UNIX and Microsoft Windows variants.
>
>  homepage        http://www.gnu.org/software/gdb/
> @@ -39,3 +39,13 @@
>                  sha1 ba1394d59dd84a1dd3a83322bd82c799596f0bcf \
>                  rmd160 23fc9442290b6383ce8f943ef1eb117fa06e79fb
>
> +depends_build   \
> +                port:expat
> +                #port:gcc42
> +
> +configure.args-append \
> +    --infodir=${prefix}/share/info \
> +    --mandir=${prefix}/share/man \
> +    --with-docdir=${prefix}/share/doc \
> +    --enable-objc-gc