> /usr/include/gssapi/gssapi_generic.h:46: error: syntax error before
> 'extern'
> /usr/include/gssapi/gssapi_generic.h:47: error: syntax error before
> 'extern'
> /usr/include/gssapi/gssapi_generic.h:48: error: syntax error before
> 'extern'
> /usr/include/gssapi/gssapi_generic.h:50: error:
On Oct 27, 2007, at 22:02, Adam Mercer wrote:
Aquaterm is failing to build for me on Leopard, I get the following
error:
[EMAIL PROTECTED] ~]$ sudo port install aquaterm
---> Fetching aquaterm
---> Verifying checksum(s) for aquaterm
---> Extracting aquaterm
---> Configuring aquaterm
--->
On Oct 27, 2007, at 17:12, David Corking wrote:
On 10/27/07, Adam Mercer wrote:
I see it's out, and I have downloaded it. But is there any
benefit to
installing it or any risk of screwing things up if I do?
Xcode 3 will only work on Leopard, from the release notes:
Does it come with a
On Oct 27, 2007, at 13:32, Michael Staggs wrote:
Ok, tiff has been fixed in the bug reports. Someone submitted a
patch for the Portfile there. It has to do with the options that
were supplied to Leopard at configure time. However, now I make it
through all the dependencies, but when I g
On Oct 28, 2007, at 00:30, CHENG Gao wrote:
i was facing this problem earlier today - i simply downloaded the
official source tarball from the libtiff website, untarred
in the work dir of the package and installed away.. If you dont
care about the ports registry you could compile directly; i
On Oct 28, 2007, at 21:29, s g wrote:
hi, im interested in putting surfraw in the ports collection, i know
almost nothing about makefiles and the ports config files so any tips
would be appreciated, i am doing this to learn and contribute cause i
think surfraw is an awesome app. i got the latest
On Oct 29, 2007, at 01:03, Adam Mercer wrote:
The net/yafc port is failing to build on Leopard, getting the error:
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I. -I../src -I../src/ftp
-I../src/libmhe -I/opt/local/include -I/opt/local/include -O2 -MT
gssapi.o -MD -MP -MF ".deps/gssapi.Tpo" -c -
On Oct 29, 2007, at 00:07, Ryan Schmidt wrote:
On Oct 28, 2007, at 23:58, Tobias Weisserth wrote:
[snip]
The following ports are currently installed:
a2ps @4.13b_3 (active)
aalib @1.4rc5_2 (active)
apr @1.2.11_0 (active)
apr @1.2.8_0
apr @1.2.9_0
[snip]
(side note: it would be
Hi
The net/yafc port is failing to build on Leopard, getting the error:
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I. -I../src -I../src/ftp
-I../src/libmhe -I/opt/local/include -I/opt/local/include -O2 -MT
gssapi.o -MD -MP -MF ".deps/gssapi.Tpo" -c -o gssapi.o gssapi.c; \
then mv -f ".de
On Oct 29, 2007, at 1:05 AM, Ryan Schmidt wrote:
On Oct 28, 2007, at 23:38, William Davis wrote:
In port avahi portfile
"post-activate" is mis-spelled. however the port fails anyway after
corecting this so I wont make a diff file.
mac mini OSX 10.5
I fixed the typo in r30483.
In what
On Oct 29, 2007, at 00:22, paul beard wrote:
On Oct 28, 2007, at 10:12 PM, Ryan Schmidt wrote:
The hypothetical "dry run" command already exists anyway: "sudo
port destroot theport" and then look into the port's work/destroot
directory to see what's in there.
Not the same thing at all.
p
On Oct 29, 2007, at 00:15, William Davis wrote:
On Oct 29, 2007, at 12:58 AM, Tobias Weisserth wrote:
I have a very basic question that I couldn't answer for myself by
looking at the port manpage or by searching the macports website.
My install base is cluttered by many inactive versions o
On Oct 28, 2007, at 10:12 PM, Ryan Schmidt wrote:
The hypothetical "dry run" command already exists anyway: "sudo
port destroot theport" and then look into the port's work/destroot
directory to see what's in there.
Not the same thing at all.
ports contents avahi returns this:
Port avahi c
On Oct 29, 2007, at 12:58 AM, Tobias Weisserth wrote:
Hi everybody,
I have a very basic question that I couldn't answer for myself by
looking at the port manpage or by searching the macports website.
My install base is cluttered by many inactive versions of ports that
I cannot uninstall
On Oct 27, 2007, at 12:13, paul beard wrote:
On 10/26/07, Ryan Schmidt wrote:
No port (and no other non-Apple software) should ever install
anything under /System The port needs to be revised to install
not in /System/Library but in /Library, and the name of the plist
should begin with or
On Oct 28, 2007, at 23:58, Tobias Weisserth wrote:
I have a very basic question that I couldn't answer for myself by
looking at the port manpage or by searching the macports website.
My install base is cluttered by many inactive versions of ports
that I cannot uninstall without running in
On Oct 28, 2007, at 23:38, William Davis wrote:
In port avahi portfile
"post-activate" is mis-spelled. however the port fails anyway after
corecting this so I wont make a diff file.
mac mini OSX 10.5
I fixed the typo in r30483.
In what way does the port now fail? Please send us the outpu
Hi everybody,
I have a very basic question that I couldn't answer for myself by
looking at the port manpage or by searching the macports website.
My install base is cluttered by many inactive versions of ports that
I cannot uninstall without running in dependency problems.
For example, th
In port avahi portfile
"post-activate" is mis-spelled. however the port fails anyway after
corecting this so I wont make a diff file.
mac mini OSX 10.5
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/
hi, im interested in putting surfraw in the ports collection, i know
almost nothing about makefiles and the ports config files so any tips
would be appreciated, i am doing this to learn and contribute cause i
think surfraw is an awesome app. i got the latest source from the
debian dev page; http://
On 28 Oct 2007, at 20:10, paul beard wrote:
running a "clean all" and it bails when I get there.
---> Cleaning CrimsonFields
Error: Unable to open port: couldn't change working directory to "/
opt/local/var/macports/sources/rsync.macports.org/release/ports/
sysutils/DarwinPortsStartup": no
running a "clean all" and it bails when I get there.
---> Cleaning CrimsonFields
Error: Unable to open port: couldn't change working directory to "/
opt/local/var/macports/sources/rsync.macports.org/release/ports/
sysutils/DarwinPortsStartup": no such file or directory
_
On 10/29/07, Anders F Björklund <[EMAIL PROTECTED]> wrote:
> >> Note that some ports will fail to build, when using "make -j 2"
> >
> > What causes the build erorr? is it for bad Makefile or problem of "-j"
> > option itself?
>
> Bad makefiles, usually missing dependencies.
So, in a way, using -j
On 28 Oct 2007, at 12:37, James Sumners wrote:
Excellent. I suppose we will have to manually remove the old files
next upgrade?
I'll write something into the Portfile to take care of this.
On 10/28/07, Randall Wood <[EMAIL PROTECTED]> wrote:
This has been fixed in changeset 30458 (http://
Thank you very much. That does indeed work. I just added it into the
configure.args as such:
configure.args --prefix=${prefix} --disable-vhook \
--mandir=${prefix}/share/man \
--enable-shared --enable-pthreads --disable-mmx
On Oct 28, 2007, at 10:05 AM, Mark
The solution to this problem is to use the -i flag when connecting to the
server:
ssh [EMAIL PROTECTED] -i ~/.ssh/id_dsa
You can also make this permanent for all servers by adding this line to your
~/.ssh/config:
IdentityFile ~/.ssh/id_dsa
The above solution is courtesy of Allan Odgaard, autho
Seems like it'll be a while before Macports and the various software
programs will be Leopard-ized. Historically how long has that sort of
turnaround been?
--
David Orriss Jr.
My blog: http://www.codethought.com/blog
My PalmOS apps:
http://www.palmgear.com/index.cfm?fuseaction=software.develope
Excellent. I suppose we will have to manually remove the old files next upgrade?
On 10/28/07, Randall Wood <[EMAIL PROTECTED]> wrote:
> This has been fixed in changeset 30458 (http://trac.macosforge.org/
> projects/macports/changeset/30458) and reported upstream at http://
> avahi.org/ticket/177
>
Hi
I'm trying to build py25-numpy on Leopard, which has a dependency of
g95 and hence odcctools - when I try to install this port I get the
following error:
---> Building odcctools with target default
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_U
On 2007-10-28 16:11:48 +0100, Anders F Björklund wrote:
> js wrote:
>> What causes the build erorr? is it for bad Makefile or problem of "-j"
>> option itself?
>
> Bad makefiles, usually missing dependencies.
And this may be difficult to fix. For instance:
http://dev.mutt.org/trac/ticket/2538
This has been fixed in changeset 30458 (http://trac.macosforge.org/
projects/macports/changeset/30458) and reported upstream at http://
avahi.org/ticket/177
On 26 Oct 2007, at 17:42, James Sumners wrote:
I didn't look back at the wiki to verify /System versus /Library. I
just went with what t
js wrote:
Note that some ports will fail to build, when using "make -j 2"
What causes the build erorr? is it for bad Makefile or problem of "-j"
option itself?
Bad makefiles, usually missing dependencies.
--anders
___
macports-users mailing list
I added this to my portfile, seemed to do the trick. Seems that
assembly and OSX still don't get along.
configure.args-append --disable-mmx
Mark
On 10/27/07, Michael Staggs <[EMAIL PROTECTED]> wrote:
> I used the following command line: sudo port -v install ffmpeg +a52
> +faac +faad +gpl +lame
On 10/28/07, Anders F Björklund <[EMAIL PROTECTED]> wrote:
> > Can I make this behavior (-j) default for all ports using make?
>
> In MacPorts 1.6, you can set the -j parameter with "build.jobs".
> ( see http://trac.macports.org/projects/macports/ticket/12280 )
Great. I look forward to it!
> Howe
On 10/28/07, Bryan Blackburn <[EMAIL PROTECTED]> wrote:
> There is the 'buildmakejobs' option in /opt/local/etc/macports/
> macports.conf which should be passing a '-j #' to make, though I
> personally haven't tried it.
I didn't know that. I'll try.
But port(1) and macports.conf(5) don't have
any
On Oct 28, 2007, at 2:42 AM, js wrote:
http://www.macosxhints.com/article.php?story=20070524074057479
From this article, I learned how we can easily speed up build
phase of MacPorts.
$ sudo port clean lv
...
Can I make this behavior (-j) default for all ports using make?
There is the '
js wrote:
http://www.macosxhints.com/article.php?story=20070524074057479
From this article, I learned how we can easily speed up build phase
of MacPorts.
Can I make this behavior (-j) default for all ports using make?
In MacPorts 1.6, you can set the -j parameter with "build.jobs".
( see ht
On 28 Oct 2007, at 05:08, Guido Soranzio wrote:
On Oct 28, 2007, at 9:40 AM, macports-users-
[EMAIL PROTECTED] wrote:
However I'm still only a bit closer to building GIMP... libglade2
isn't building... I'm not the only one who's see this apparently:
On PowerPC machines there is also a
http://www.macosxhints.com/article.php?story=20070524074057479
>From this article, I learned how we can easily speed up build phase of
>MacPorts.
$ sudo port clean lv
---> Cleaning lv
$ sudo port configure lv
---> Fetching lv
---> Verifying checksum(s) for lv
---> Extracting lv
---> Applying
On 10/28/07, Anders F Björklund <[EMAIL PROTECTED]> wrote:
> David Orriss Jr wrote:
>
> > I'm really having fights with GIMP 2.4 getting it to run... I get
> > errors with the tiff libraries..
>
> See http://trac.macports.org/projects/macports/ticket/12997
I figured out where the portfile was...
On 10/28/07, Anders F Björklund <[EMAIL PROTECTED]> wrote:
> David Orriss Jr wrote:
>
> > I'm really having fights with GIMP 2.4 getting it to run... I get
> > errors with the tiff libraries..
>
> See http://trac.macports.org/projects/macports/ticket/12997
>
Where do I find the port file? Sorry.
Juan Manuel Palacios wrote:
2) Once the build product, the destroot, is done and considered
reliable, packaging it into, say, an rpm and/or a deb package is a
completely different topic, with its own intricacies and integration
issues between MacPorts and the packaging format we still need to
On Oct 28, 2007, at 9:40 AM, macports-users-
[EMAIL PROTECTED] wrote:
However I'm still only a bit closer to building GIMP... libglade2
isn't building... I'm not the only one who's see this apparently:
On PowerPC machines there is also a more basic problem with glib2
and the new linker;
David Orriss Jr wrote:
I'm really having fights with GIMP 2.4 getting it to run... I get
errors with the tiff libraries..
See http://trac.macports.org/projects/macports/ticket/12997
--anders
___
macports-users mailing list
macports-users@lists.mac
I'm really having fights with GIMP 2.4 getting it to run... I get
errors with the tiff libraries..
tiffgt.c: In function 'raster_keys':
tiffgt.c:303: warning: unused parameter 'x'
tiffgt.c:303: warning: unused parameter 'y'
tiffgt.c: In function 'raster_special':
tiffgt.c:348: warning: unused par
45 matches
Mail list logo