Problems with libgnomcanvas

[David Evans]

After upgrading this morning to the latest version of libgnomecanvas, 
I've been getting the following type
of message from applications and/or libraries (of which there are a lot) 
that are built against the previous

version of libgnomecanvas:

Gtk-Message: Failed to load module "gail-gnome": 
dlopen(/opt/local/lib/gtk-2.0/modules/libgail-gnome.so, 1): Library not 
loaded: /opt/local/lib/libgnomecanvas-2.0.dylib

 Referenced from: /opt/local/lib/libpanel-applet-2.0.dylib
 Reason: Incompatible library version: libpanel-applet-2.0.dylib 
requires version 2001.0.0 or later, but libgnomecanvas-2.0.dylib 
provides version 1999.0.0


This can be fixed by re-building the dependent ports but it appears that 
there may have been some regression

in the upgraded libgnomecanvas port from version 2001.0.0-> 1999.0.0

So the question is, is this intentional (so start rebuilding) or is 
something wrong with libgnomecanvas?



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

dcraw conflict

[David Evans]

Attempting to install dcraw today resulted in the following error:

--->  Installing dcraw 8.81_1
This port conflicts with ufraw. If this port fails to
activate, uninstall or deactivate ufraw and attempt to
activate this port again.
--->  Activating dcraw 8.81_1
Error: Target org.macports.activate returned: Image error:
/opt/local/bin/dcraw is being used by the active ufraw port.  Please
deactivate this port first, or use the -f flag to force the activation.
Error: Status 1 encountered during processing.


Both ports  dcraw and ufraw provide a version of dcraw.  (ufraw provides
a gui and gimp plugin for dcraw)

Would it be possible to remove dcraw from ufraw and have it depend on
the dcraw port instead or is there something
special about the version of dcraw bundled with ufraw?  If so perhaps it
could be renamed to avoid the conflict?


Thanks for any help

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users

Re: JHymn distfiles

[David Evans]

Ryan Schmidt wrote:
> The developer apparently received a cease and desist order in  
> February 2008 and had to remove the files.
>
> http://www.hymn-project.org/forums/viewtopic.php?t=1314
>
> We don't seem to have the files on our mirror either.
>
> http://distfiles.macports.org/JHymn/
>
> The forum topic above seems to list some alternatives.
>
> Maybe we should remove the JHymn port.
>
>   
If so port hymn should probably go as well (and is equally broken)

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: tclsh eats all available memory (port -d upgrade installed)

[David Evans]

Dave Evans wrote:
> I have 317 ports installed. None require upgrading.
>
> Starting  sudo port -d upgrade installed  and monitoring
> the memory usage with Activity Monitor, after a few seconds
> tclsh RSIZE is up to 300 MB.   After a couple of minutes
> the RSIZE is up to 1.5GB and the free memory is down
> to  8 MB.  They stay at these values for another couple of minutes
> when tclsh gives up with an out of memory error.
>
> DEBUG: Found port in file:///opt/local/var/macports/sources/
> rsync.macports.org/r
> elease/ports/gnome/gnome-icon-theme
> tclsh(34820,0xa0592fa0) malloc: *** mmap(size=1884160) failed (error
> code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> unable to alloc 1882835 bytes
> Abort trap
>
> Does any one know why tclsh is using so much memory?  The only
> message in this mailing list referring to the problem was a couple of
> months ago. See http://tinyurl.com/5vn3qu and
> (on another mailing list) http://tinyurl.com/6s7sxh
>
> My configuration: 2GB memory, OSX 10.5.4, Xcode 3.1,
> 500 GB of free disk space (so swap space cannot be a problem)
>
>   
I've now installed tcl 8.5.4 from Macports and modified
port to use it.  I then rerun
sudo port -d upgrade installed

It ran right through to the end.  It still used up nearly all
of the free memory though, even though it did not
need to upgrade any ports.

Apologies for the html text in the previous message. I've now
installed Thunderbird which should avoid this - I hope.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

cdrtools is not building and installing mkisofs, cdda2wav and various other programs

[David Evans]

In cdrtools version 2.01.01a46_0,  it does not build and install mkisofs,
cdda2wav and various other programs. It does build and install
cdrecord

I do not know whether it is related to this error message:

-
W A R N I N GMessages like:

gmake[2]: Entering directory `/tmp/cdrtools-2.01/libschily'

../RULES/r-gmake.dep:76: OBJ//ffilewrite.d: No such file or 
directory
../RULES/r-gmake.dep:76: OBJ//fgetline.d: No such file or 
directory
../RULES/r-gmake.dep:76: OBJ//fgetstr.d: No such file or directory
../RULES/r-gmake.dep:76: OBJ//file_raise.d: No such file or 
directory
../RULES/r-gmake.dep:76: OBJ//fileclose.d: No such file or 
directory


are caused by a GNU make bug and not by the Schily makefile system.

The related bug has been reported to the GNU make maintainers in 1998 but
as the bug has not yet been fixed, it seems that GNU make is 
unmaintained :-(
A working highly portable make program is at ftp://ftp.berlios.de/pub/smake
--


Perhaps we should be using smake.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: cdrtools is not building and installing mkisofs, cdda2wav and various other programs

[David Evans]

Bryan Blackburn wrote:
> I just attached a patch to ticket #15934 [1] which updates cdrtools to  
> the current version and switches to using smake; hopefully using smake  
> to do the build will fix these issues you've seen.
>
> Bryan
>
> [1] - 
>
>   
I've been patiently waiting for cdrtools to appear in my list of 
outdated ports.
Today, I decided to force the build, whereupon port detected that the
port file had been changed and rebuilt and installed cdrtools.


Should there have been a version number bump so that outdated will
recognise it?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: cdrtools is not building and installing mkisofs, cdda2wav and various other programs

[David Evans]

Bryan Blackburn wrote:
> On Tue, Sep 16, 2008 at 11:29:33AM +0100, David Evans said:
>   
>> Bryan Blackburn wrote:
>> 
>>> I just attached a patch to ticket #15934 [1] which updates cdrtools to  
>>> the current version and switches to using smake; hopefully using smake  
>>> to do the build will fix these issues you've seen.
>>>
>>> Bryan
>>>
>>> [1] - <http://trac.macports.org/ticket/15934>
>>>
>>>   
>>>   
>> I've been patiently waiting for cdrtools to appear in my list of 
>> outdated ports.
>> Today, I decided to force the build, whereupon port detected that the
>> port file had been changed and rebuilt and installed cdrtools.
>>
>>
>> Should there have been a version number bump so that outdated will
>> recognise it?
>> 
>
> How often do you run selfupdate?  macsforever2000@ committed the update [1]
> over a week ago so 'port outdated' should have seen the change with the
> next PortIndex (within 12 hours) and a selfupdate.
>
>   
I hardly ever run port selfupdate.  I thought that port sync was 
sufficient every couple of days.
Perhaps that's where I'm going wrong.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Patch of doxygen failed

[David Evans]

--->  Applying patches to doxygen
--->  Applying 
/opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/doxygen/files/patch-qfiledefs_p.h
DEBUG: Environment:
DEBUG: Assembled command: 'cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_doxygen/work/doxygen-1.5.6"
 
&& patch -p0'
patching file qtools/qfiledefs_p.h
Hunk #1 FAILED at 56.
1 out of 1 hunk FAILED -- saving rejects to file qtools/qfiledefs_p.h.rej

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: upgrading gimp2

[David Evans]

Duc N Nguyen wrote:
> I am trying to upgrade gimp2 with python scripting enabled.  However,
> during the install ports is trying to install python24.  Why is that?
> Shouldn't port know that I have python25 already installed?
>
> I already have python25 installed and don't want to install python24.
> Is there a way to keep gimp2 from trying to install python24.  I was
> looking at the dependencies of gimp2 and saw that only py25-gtk is the
> only python dependency.  Are there any other dependencies of gimp2
> that have python24 as a dependent?
>
> Any help or clarification is much appreciated.
>
> Thank you,
> Duc
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>   
Yes, it looks like asciidoc depends on python24.  Perhaps the asciidoc
maintainer can comment on
this.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: upgrading gimp2

[David Evans]

David Evans wrote:
> Duc N Nguyen wrote:
>   
>> I am trying to upgrade gimp2 with python scripting enabled.  However,
>> during the install ports is trying to install python24.  Why is that?
>> Shouldn't port know that I have python25 already installed?
>>
>> I already have python25 installed and don't want to install python24.
>> Is there a way to keep gimp2 from trying to install python24.  I was
>> looking at the dependencies of gimp2 and saw that only py25-gtk is the
>> only python dependency.  Are there any other dependencies of gimp2
>> that have python24 as a dependent?
>>
>> Any help or clarification is much appreciated.
>>
>> Thank you,
>> Duc
>> ___
>>
>> 
> Yes, it looks like asciidoc depends on python24.  Perhaps the asciidoc
> maintainer can comment on
> this.
>
>
>   
To be a bit clearer, gimp2 depends on gegl which depends on asciidoc to
generate documentation.

I have just submitted a patch for gegl which disables docs unless you
explicitly ask for them via
the +html_doc variant.   When this is committed, it should avoid the
dependency you mention.
Also upgrades gegl to 0.0.20.

See https://trac.macports.org/ticket/16796

Let me know if this helps

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: upgrading gimp2

[David Evans]

Duc N Nguyen wrote:
> Thanks for submitting the patch report.
>
> I upgraded gimp2.6 last night and it runs fine.  I modified the
> portfile for asciidoc to use python25 instead of python24 which
> installed without errors.  However, when I ran the actual upgrade, I
> still had to install python24.  Was there another dependency that we
> missed?
>
> --Duc
>
>   
The patch for gegl hasn't been committed yet so that may be the problem
still.  However,
using the patch locally, I uninstalled python24 and rebuilt gegl and
gimp2 with no reinstallation of
python24.

Suggest you file a ticket against asciidoc about the python24 issue if
you haven't already including
details and what platform and OS version you are using.

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gimp-user-manual error

[David Evans]

Ryan Schmidt wrote:
> On Oct 11, 2008, at 23:48, William Davis wrote:
>
>> error in variants gimp-user-manual:
>>
>> DEBUG: gimp-user-manual 2.4.2_0 exists in the ports tree
>> DEBUG: gimp-user-manual 0.13_0 is installed
>> DEBUG: Not following dependencies
>> DEBUG: variants to install {} fetch
>> DEBUG: available variants are : universal fetch build without_gimp cs
>> de en es fr hr it ko nl no ru sv zh_CN
>> DEBUG: variant fetch is present in gimp-user-manual 2.4.2_0
>> DEBUG: new portvariants: with_gnome + fetch +
>> DEBUG: Changing to port directory: /opt/local/var/macports/sources/
>> rsync.macports.org/release/ports/graphics/gimp-user-manual
>> DEBUG: Requested variant darwin is not provided by port gimp-user-
>> manual.
>> DEBUG: Requested variant with_gnome is not provided by port gimp-user-
>> manual.
>> DEBUG: Requested variant i386 is not provided by port gimp-user-manual.
>> DEBUG: Requested variant macosx is not provided by port gimp-user-
>> manual.
>> DEBUG: Executing variant fetch provides fetch
>> DEBUG: Executing variant build provides build
>> Error: Variant build conflicts with fetch
>> DEBUG: Error evaluating variants
>>  while executing
>> "error "Error evaluating variants""
>>  (procedure "mportopen" line 51)
>>  invoked from within
>> "mportopen $porturl [array get options] [array get variations]"
>> Error: Unable to open port: Error evaluating variants
>>
>> cleaning did not help
>
>
> There's another thread where this was brought up too:
>
> http://lists.macosforge.org/pipermail/macports-users/2008-October/011855.html
>
>
> The problem was r40710:
>
> http://trac.macports.org/changeset/40710
>
>  * It changed the default variant from +fetch to +en
>  * +en requires +build
>  * +build conflicts with +fetch
>  * The +fetch variant was "disabled" by commenting out its contents,
> but the empty variant is still there
>
> So anybody who had gimp-user-manual 0.13 installed will have the
> +fetch variant selected, because it was the default. Now they want to
> upgrade, and because there is still a fetch variant in the new port,
> +fetch will again be selected, but since the port now has +en as the
> default, which requires +build, +build will also be selected, which
> conflicts with +fetch.
>
> So the "fetch" variants should simply be commented out or deleted
> entirely -- including its definition. And this was done in r40724 and
> r40725.
>
> http://trac.macports.org/changeset/40724
>
> http://trac.macports.org/changeset/40725

Yes, this fix should be available shortly (during the next hour by my
clock).
>
> I'm still not happy with the variant names "fetch" and "build". It's
> not clear from that name what's being fetched or built, and the names
> unintentionally evoke the fetch and build MacPorts phases. (Granted
> they do have descriptions which make it clear, but as we see these
> aren't shown in the error messages.) They could be renamed "fetch_doc"
> and "build_doc" to be more clear. But since there is now no fetch
> variant, I would remove the build variant as well which would fix all
> the problems.
>
> Is the plan to go back to fetching the documentation at a later time
> instead of building it?
>
>
This is definitely a work in progress right now.  As you know, I have
just taken maintainership
of this and other gimp related ports to try and get them all up to date
and working properly and
there are a number of problems in various places.  I don't like the
fetch and build variants (for their
names if nothing else) but building the full documentation with all
locales (which is what the
previous build variant did is a very long process and probably
unnecessary for the average
user.  Therefore, I understand the idea to be able to build a prebuilt
version.

However, since the documentation was so far out of date, I have changed
this to build
en locale by default as you say so get the documentation up to the
latest released state
2.4.2 which still isn't up to the current 2.6.1 state of the app itself
but is closer.  If you want
another locale you can do that by added the appropriate variant.

In addition, it's possible to build a pdf version of the documentation
but this requires
dblatex for which we do not have a port right now.

Finally, is this port necessary at all?  The exact same html
documentation is available on
line and gimp (in principal) can be configured via preferences so refer
to that if local documentation
is not available.  However, this is broken right now because it wants to
use gvfs which is
not working correctly yet.

Also gimp-jp2 seems to be broken due to problems with the openjpeg port.

So lots of work to be done in the gimp area.  Please let me know your
suggestions on
the documentation issues.  What is the correct selection of ports to
include in the
gimp meta-port?  Are there other plugins that you think are essential
that should be
included as part of a basic install?

Thanks

Dave

___
macports-user

GIMP toolbar work-around

[David Evans]

If you're one of those who have gone to all the effort (and pain) of
building the new gimp2 (2.6.1) port
here's a few work-arounds for a big problem with the Toolbar and other
"dock" windows in the program.

You can see the problem on startup of the application by just going to
the Toolbar which is forced to always
be on top of any other windows.  When you hover over an item, the
corresponding tool tip
is displayed behind the Toolbar window and obscured by it.  Similarly,
clicking on a tool property button
(such as Brush on the Paintbrush Tool) produces a popup window that is
again behind and obscured
by the Toolbar window.  This is true for other "dock" windows as well
(not the main image window).

For more details, see my bug report at

http://bugzilla.gnome.org/show_bug.cgi?id=556337.


This behavior can be changed in one of two ways:

1)  To change this for an individual user, go to
Edit->Preferences->Window Management and
under Window Manager Hints set both "Hint for the toolbox" and "Hint for
other docks" to Normal
window instead of Utility window.

or

2) To change this globally for all users on your system, add the
following lines

(toolbox-window-hint normal)
(dock-window-hint normal)

to the end of the GIMP global preference file

${prefix}/etc/gimp/2.0/gimprc

where ${prefix} is the MacPorts installation prefix (typically /opt/local)

In either case you need to restart GIMP for the changes to take effect. 
The tool tips, child
menus and pop-up windows will display in front of the dock windows so
you can actually
see and use them.

I intend to modify the gimp2 port to preset these preferences but I
don't intend to increment
the revision number for this (unless there is an outpouring of demand)
as it doesn't seem
appropriate to force a rebuild of the entire program for something that
can be handled much
easier otherwise.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: pango 1.22.0 requires glib 2.17.3 or later but you have glib 2.16.5.

[David Evans]

Ryan Schmidt wrote:
> On Oct 16, 2008, at 03:20, David Epstein wrote:
>
>   
>> My error message must have been dealt with somewhere in the list,  
>> possibly
>> many times, but I haven't been able to find it. I was trying to  
>> install
>> gimp:
>> sudo port install gimp
>> Eventually I got the error message
>> Target org.macports.configure returned: pango 1.22.0 requires glib  
>> 2.17.3 or
>> later but you have glib 2.16.5.
>>
>> I tried sudo port deactivate glib, which resulted in
>> Password:
>> --->  Deactivating glib
>> Error: port deactivate failed: Registry error: glib not registered as
>> installed & active.
>>
>> Help would be appreciated.
>> 
>
> Your glib2 is out of date, so you should update it:
>
> sudo port sync
> sudo port upgrade glib2
>
> To see which other ports are out of date and in need of updating:
>
> port outdated
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>   
After doing

port selfupdate

Of course.  Several of the gimp dependencies have been updated recently
so be sure
you have the latest ports before you start.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Pango anti-aliasing

[David Evans]

Ryan Schmidt wrote:
> On Oct 18, 2008, at 12:37, David Trem wrote:
>
>   
>>  It seems that I run into trouble with anti-aliasing and gtk2/pango.
>> With the latest gtk2 2.14.3, Revision 3
>> I do not have/see anti-aliasing with pango 1.22.0, x11/pango
>>
>> Any idea where I should look for...
>> 
>
> What do I need to do on my system to reproduce the problem? What does  
> one do with gtk2 to see it? I don't usually use gtk2.
>
> What OS, Xcode and MacPorts versions do you have and on what kind of  
> Mac?
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>   
I believe that anti-aliasing is done during rendering in cairo and gtk
and pango take advantage of
this internally.

Perhaps this would be a good question for the gtk list.

http://mail.gnome.org/mailman/listinfo/gtk-list

Also note that the following were released yesterday and so you might
want to wait until
they are available on MacPorts to see if the behavior you describe is
changed in the new
versions.

GTK+ 2.14.4
GLib 2.18.2



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: how to build gimp +quartz?

[David Evans]

Olaf Foellinger wrote:
> Hi,
>
> today I've tried to build 
>
> $ sudo port install gimp-app +quartz
>
> on a relative freshly installed macports. Before I've installed the x11
> version of gnucash.
>
> Macports has installed the x11 version of gimp to. What do I have to do
> to install the quartz version? My next target would be the quartz
> version of gnucash which should be possible according to 
>
> http://wiki.gnucash.org/wiki/MacOSX/Quartz 
>
> Gruß Olaf
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
>   
I'm not sure that anyone has succeeded doing this with version 2.6.1
yet.  Even the
official GIMP On MacOSX prebuilt version is X11.

The general idea is that you have to rebuild gtk2 and its dependencies
with +quartz or +no_x11 as is the case
by looking at each port and then rebuild gimp using these as the
dependencies.

This will break a lot of things that expect x11 support in other apps so
you probably would
want to do this using a separate MacPorts installation just for this
purpose.

Another approach is to build separate copies of the underlying
dependencies using Imendio's
system for building GTK in native mode.  A description of how to go
about this can be found
on the gimp.org wiki (Wilber's Wiki)  here

http://wiki.gimp.org/gimp/HowToCompileGimp/MacOSX

Hope this helps and if you have any success or run into specific
problems please let us know.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: ASSP out of date

[David Evans]

Scott Haneda wrote:
> This port installs clean, and really nice:
> http://trac.macports.org/browser/trunk/dports/mail/assp/Portfile
>
> however, I can not locate a maintainer, as it is woefully out of date.
> nameassp
> version 1.1.0
>
> ASSP 1.3.3.10 is current, and also, there is a very strong beta of 2.x
> as well I would love to see in the ports system.  What is the best way
> to find the maintainer, and see about getting this updated.
> -- 
> Scott
>
Since the maintainer is "nomaintainer" then maintainership is up for
grabs.  So you can become the
maintainer if you like.  Just update the Portfile as necessary with
yourself as maintainer
and also openmaintainer if you are willing to let others make changes to
the port.  Then
create a ticket on Trac and attach your changes, preferably as a patch
to the current Portfile.

See http://guide.macports.org/  for procedural details.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Problems Installing gtk2 +quartz

[David Evans]

Tim Visher wrote:
> Ah. That was the problem. That's funny but I never knew the correct
> way to get what was installed out of port. Oh well.
>
> Is there anyway to switch which variant you have installed?
>
>   
You can deactivate the currently installed version and then install with
the variant you want.

sudo port deactivate gtk2
sudo port install gtk2 +quartz

Note also you need to make sure that you have the +no_x11 variants
installed for
cairo and pango.

In my installation:

$ port installed cairo pango gtk2
The following ports are currently installed:
  cairo @1.8.0_0+macosx+no_x11 (active)
  gtk2 @2.14.4_0+darwin_8+no_x11+quartz (active)
  pango @1.22.2_0+no_x11 (active)

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: ASSP out of date

[David Evans]

Scott --

Can you post a copy of your Portfile as it currently is? Or did I miss
it?  Concerning the dependencies
if there are so many, perhaps if you published a list of what's needed
others might lend a hand. 

It does look like you picked a tough case for your first Portfile.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: ASSP out of date

[David Evans]

Scott Haneda wrote:
>> Concerning the dependencies
>> if there are so many, perhaps if you published a list of what's needed
>> others might lend a hand.
>
> Sure, I can find some, but not others:
> Net::DNS
> Compress::Zlib
> Digest::MD5
> Email::MIME::Modifier new
> Email::Valid
> File::ReadBackwards
> Mail::SPF new
> Mail::SPF::Query
> Mail::SRS
> Net::CIDR::Lite new
> Net::IP::Match::Regexp new
> Net::LDAP
> Net::SMTP new
> Net::SenderBase new
> Net::Syslog
> Sys::Syslog
> Tie::RDBM
> Time::HiRes
> Win32::Daemon
A lot of these are there already you can use

port contents perl5.8

to see a list of the files installed with the basic perl (after you have
installed it)

and

port search p5-

will give you a list of other perl modules available such as

p5-compress-zlib
p5-digest-md5
p5-email-valid
p5-net-dns
p5-time-hires

to pick just a few quickly -- you get the idea

Dave
>
> I assume ClamAV, which is not in that list, should be already
> available, and ready to go.
>

___
macports-dev mailing list
[EMAIL PROTECTED]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Updating gstreamer and friends

[David Evans]

I've just updated the gstreamer and associated ports namely

gstreamer
gst-plugins-base
gst-plugins-good
gst-plugins-bad
gst-plugins-ugly

However, if you're planning on upgrading from an older version, be aware
that while the new gst-plugins-good, bad, ugly are consistent with each
other they conflict with the older versions by the same name because
some of the plug-ins have been moved from one category to another.

I recommend the following procedure for upgrading:

sudo port upgrade gstreamer gst-plugins-base
sudo port uninstall gst-plugins-good gst-plugins-bad gst-plugins-ugly
sudo port install gst-plugins-good gst-plugins-bad gst-plugins-ugly

Dave





___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Updating gstreamer and friends

[David Evans]

William Davis wrote:
> - Installing ./html/up.png
> -- Installing ./html/style.css
> -- Installing ./html/gstreamer.devhelp
> make[5]: *** [install-data-local] Error 1
> make[4]: *** [install-am] Error 2
> make[3]: *** [install] Error 2
> make[2]: *** [install-recursive] Error 1
> make[1]: *** [install] Error 2
> make: *** [install-recursive] Error 1
>
> Error: The following dependencies failed to build: gst-plugins-base
> gstreamer
> Error: Status 1 encountered during processing.
>
>
>
> William Davis
> frstanATbellsouthDOTnet
> Mac OS X.5.5 Darwin 9.5.0
> XQuartz 2.3.2_beta3 (xorg-server 1.4.2-apple22)
> Mac Mini Intel Duo @ 1.86 GHz
>
> Mundus vult decepi, ego non
>
I can't really tell what happened from the fragment that you posted.

Suggest you make sure you have the latest by executing

sudo port selfupdate
sudo port clean --all gstreamer

then

sudo port -d upgrade gstreamer  |& tee gstreamer.log

Look like it built ok but had a problem during destroot?



and attach the result to your reply (or to a ticket) so I can compare
it to my results.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Updating gstreamer and friends

[David Evans]

>
>
> Thank you, David. I will do that.  At the moment I am compliing gnome
> (sudo port install gnome) and that is going to take a while. Would it
> be safe to run the commands you gave in another Terminal Window?
>
>
> William Davis
I haven't had any problems with this as long as the two processes aren't
trying to build the same thing. 

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: MPlayer Port Suggestion

[David Evans]

On Thu, 2008-11-20 at 16:29 -0600, Altoine Barker wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> I had discussed with Eric Cronin on this list about using svn source of
> mplayer to build a port. 

I'm not sure if this is what you had in mind or not, but port ffmpeg is
an example of a port that uses svn to fetch a specific revision from a
repository (because that's the only way they do it).

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Fwd: guile doesn't build for me]

[David Evans]

--- Begin Message ---
Hello, I don't know if this email will end up anywhere, but I'm  
trying anyway. Guile 1.8 or 1.6 do not build on my computer. I'm  
using osx 10.4.11. This is the output from the failed attempt:

Thank you

(I'm only copying this to dev...@macports because the last change  
made was signed by him, I don't know if he has anything to do with  
guile)



jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo / 
opt/local/bin/port clean guile

--->  Cleaning guile
jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo / 
opt/local/bin/port install guile

--->  Fetching guile
--->  Verifying checksum(s) for guile
--->  Extracting guile
--->  Applying patches to guile
--->  Configuring guile
--->  Building guile with target all
Error: Target org.macports.build returned: shell command " cd "/opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gu 
ile/work/guile-1.8.5" && make all " returned error 2

Command output: mv -f .deps/regex-posix.Tpo .deps/regex-posix.Plo
/bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0 -I/opt/ 
local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes -Werror - 
lintl -Wl,-framework -Wl,CoreFoundation -version-info 19:0:2 -export- 
dynamic -no-undefined -L/opt/local/lib -o libguile.la -rpath /opt/ 
local/lib libguile_la-alist.lo libguile_la-arbiters.lo libguile_la- 
async.lo libguile_la-backtrace.lo libguile_la-boolean.lo libguile_la- 
chars.lo libguile_la-continuations.lo libguile_la-convert.lo  
libguile_la-debug.lo libguile_la-deprecation.lo libguile_la- 
deprecated.lo libguile_la-discouraged.lo libguile_la-dynwind.lo  
libguile_la-environments.lo libguile_la-eq.lo libguile_la-error.lo  
libguile_la-eval.lo libguile_la-evalext.lo libguile_la-extensions.lo  
libguile_la-feature.lo libguile_la-fluids.lo libguile_la-fports.lo  
libguile_la-futures.lo libguile_la-gc.lo libguile_la-gc-mark.lo  
libguile_la-gc-segment.lo libguile_la-gc-malloc.lo libguile_la-gc- 
card.lo libguile_la-gc-freelist.lo libguile_la-gc_os_dep.lo  
libguile_la-gdbint.lo libguile_la-gh_data.lo libguile_la-gh_eval.lo  
libguile_la-gh_funcs.lo libguile_la-gh_init.lo libguile_la-gh_io.lo  
libguile_la-gh_list.lo libguile_la-gh_predicates.lo libguile_la- 
goops.lo libguile_la-gsubr.lo libguile_la-guardians.lo libguile_la- 
hash.lo libguile_la-hashtab.lo libguile_la-hooks.lo libguile_la- 
i18n.lo libguile_la-init.lo libguile_la-inline.lo libguile_la- 
ioext.lo libguile_la-keywords.lo libguile_la-lang.lo libguile_la- 
list.lo libguile_la-load.lo libguile_la-macros.lo libguile_la- 
mallocs.lo libguile_la-modules.lo libguile_la-numbers.lo libguile_la- 
objects.lo libguile_la-objprop.lo libguile_la-options.lo libguile_la- 
pairs.lo libguile_la-ports.lo libguile_la-print.lo libguile_la- 
procprop.lo libguile_la-procs.lo libguile_la-properties.lo  
libguile_la-random.lo libguile_la-rdelim.lo libguile_la-read.lo  
libguile_la-root.lo libguile_la-rw.lo libguile_la-scmsigs.lo  
libguile_la-script.lo libguile_la-simpos.lo libguile_la-smob.lo  
libguile_la-sort.lo libguile_la-srcprop.lo libguile_la-stackchk.lo  
libguile_la-stacks.lo libguile_la-stime.lo libguile_la-strings.lo  
libguile_la-srfi-4.lo libguile_la-srfi-13.lo libguile_la-srfi-14.lo  
libguile_la-strorder.lo libguile_la-strports.lo libguile_la-struct.lo  
libguile_la-symbols.lo libguile_la-threads.lo libguile_la-null- 
threads.lo libguile_la-throw.lo libguile_la-values.lo libguile_la- 
variable.lo libguile_la-vectors.lo libguile_la-version.lo libguile_la- 
vports.lo libguile_la-weaks.lo libguile_la-ramap.lo libguile_la- 
unif.lo dynl.lo filesys.lo posix.lo net_db.lo socket.lo regex- 
posix.lo -lgmp -lm -lltdl
/usr/bin/gcc-4.0 -dynamiclib  -o .libs/libguile.17.2.0.dylib  .libs/ 
libguile_la-alist.o .libs/libguile_la-arbiters.o .libs/libguile_la- 
async.o .libs/libguile_la-backtrace.o .libs/libguile_la- 
boolean.o .libs/libguile_la-chars.o .libs/libguile_la- 
continuations.o .libs/libguile_la-convert.o .libs/libguile_la- 
debug.o .libs/libguile_la-deprecation.o .libs/libguile_la- 
deprecated.o .libs/libguile_la-discouraged.o .libs/libguile_la- 
dynwind.o .libs/libguile_la-environments.o .libs/libguile_la- 
eq.o .libs/libguile_la-error.o .libs/libguile_la-eval.o .libs/ 
libguile_la-evalext.o .libs/libguile_la-extensions.o .libs/ 
libguile_la-feature.o .libs/libguile_la-fluids.o .libs/libguile_la- 
fports.o .libs/libguile_la-futures.o .libs/libguile_la-gc.o .libs/ 
libguile_la-gc-mark.o .libs/libguile_la-gc-segment.o .libs/ 
libguile_la-gc-malloc.o .libs/libguile_la-gc-card.o .libs/libguile_la- 
gc-freelist.o .libs/libguile_la-gc_os_dep.o .libs/libguile_la- 
gdbint.o .libs/libguile_la-gh_data.o .libs/libguile_la- 
gh_eval.o .libs/libguile_la-gh_funcs.o .libs/libguile_la- 
gh_init.o .libs/libguile_la-gh_io.o .libs/libguile_la-gh_list.o .libs/ 
libguile_la-gh_predicates.o .libs/libguile_la-goops.o .libs/ 
libguile_la-gsubr.o .libs/libguile_la-guardians.o .libs/li

Re: guile doesn't build for me

[David Evans]

james wrote:
> Hello, I don't know if this email will end up anywhere, but I'm trying
> anyway. Guile 1.8 or 1.6 do not build on my computer. I'm using osx
> 10.4.11. This is the output from the failed attempt:
> Thank you
>
> (I'm only copying this to dev...@macports because the last change made
> was signed by him, I don't know if he has anything to do with guile)
>
>
> jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo
> /opt/local/bin/port clean guile
> --->  Cleaning guile
> jamesebaileys-computer:/Users/jamesebailey/Downloads bigdaddy$ sudo
> /opt/local/bin/port install guile
> --->  Fetching guile
> --->  Verifying checksum(s) for guile
> --->  Extracting guile
> --->  Applying patches to guile
> --->  Configuring guile
> --->  Building guile with target all
> Error: Target org.macports.build returned: shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile/work/guile-1.8.5"
> && make all " returned error 2
> Command output: mv -f .deps/regex-posix.Tpo .deps/regex-posix.Plo
> /bin/sh ../libtool --tag=CC   --mode=link /usr/bin/gcc-4.0
> -I/opt/local/include -D_THREAD_SAFE  -O2 -Wall -Wmissing-prototypes
> -Werror -lintl -Wl,-framework -Wl,CoreFoundation -version-info 19:0:2
> -export-dynamic -no-undefined -L/opt/local/lib -o libguile.la -rpath
> /opt/local/lib libguile_la-alist.lo libguile_la-arbiters.lo
> libguile_la-async.lo libguile_la-backtrace.lo libguile_la-boolean.lo
> libguile_la-chars.lo libguile_la-continuations.lo
> libguile_la-convert.lo libguile_la-debug.lo libguile_la-deprecation.lo
> libguile_la-deprecated.lo libguile_la-discouraged.lo
> libguile_la-dynwind.lo libguile_la-environments.lo libguile_la-eq.lo
> libguile_la-error.lo libguile_la-eval.lo libguile_la-evalext.lo
> libguile_la-extensions.lo libguile_la-feature.lo libguile_la-fluids.lo
> libguile_la-fports.lo libguile_la-futures.lo libguile_la-gc.lo
> libguile_la-gc-mark.lo libguile_la-gc-segment.lo
> libguile_la-gc-malloc.lo libguile_la-gc-card.lo
> libguile_la-gc-freelist.lo libguile_la-gc_os_dep.lo
> libguile_la-gdbint.lo libguile_la-gh_data.lo libguile_la-gh_eval.lo
> libguile_la-gh_funcs.lo libguile_la-gh_init.lo libguile_la-gh_io.lo
> libguile_la-gh_list.lo libguile_la-gh_predicates.lo
> libguile_la-goops.lo libguile_la-gsubr.lo libguile_la-guardians.lo
> libguile_la-hash.lo libguile_la-hashtab.lo libguile_la-hooks.lo
> libguile_la-i18n.lo libguile_la-init.lo libguile_la-inline.lo
> libguile_la-ioext.lo libguile_la-keywords.lo libguile_la-lang.lo
> libguile_la-list.lo libguile_la-load.lo libguile_la-macros.lo
> libguile_la-mallocs.lo libguile_la-modules.lo libguile_la-numbers.lo
> libguile_la-objects.lo libguile_la-objprop.lo libguile_la-options.lo
> libguile_la-pairs.lo libguile_la-ports.lo libguile_la-print.lo
> libguile_la-procprop.lo libguile_la-procs.lo libguile_la-properties.lo
> libguile_la-random.lo libguile_la-rdelim.lo libguile_la-read.lo
> libguile_la-root.lo libguile_la-rw.lo libguile_la-scmsigs.lo
> libguile_la-script.lo libguile_la-simpos.lo libguile_la-smob.lo
> libguile_la-sort.lo libguile_la-srcprop.lo libguile_la-stackchk.lo
> libguile_la-stacks.lo libguile_la-stime.lo libguile_la-strings.lo
> libguile_la-srfi-4.lo libguile_la-srfi-13.lo libguile_la-srfi-14.lo
> libguile_la-strorder.lo libguile_la-strports.lo libguile_la-struct.lo
> libguile_la-symbols.lo libguile_la-threads.lo
> libguile_la-null-threads.lo libguile_la-throw.lo libguile_la-values.lo
> libguile_la-variable.lo libguile_la-vectors.lo libguile_la-version.lo
> libguile_la-vports.lo libguile_la-weaks.lo libguile_la-ramap.lo
> libguile_la-unif.lo dynl.lo filesys.lo posix.lo net_db.lo socket.lo
> regex-posix.lo -lgmp -lm -lltdl
> /usr/bin/gcc-4.0 -dynamiclib  -o .libs/libguile.17.2.0.dylib 
> .libs/libguile_la-alist.o .libs/libguile_la-arbiters.o
> .libs/libguile_la-async.o .libs/libguile_la-backtrace.o
> .libs/libguile_la-boolean.o .libs/libguile_la-chars.o
> .libs/libguile_la-continuations.o .libs/libguile_la-convert.o
> .libs/libguile_la-debug.o .libs/libguile_la-deprecation.o
> .libs/libguile_la-deprecated.o .libs/libguile_la-discouraged.o
> .libs/libguile_la-dynwind.o .libs/libguile_la-environments.o
> .libs/libguile_la-eq.o .libs/libguile_la-error.o
> .libs/libguile_la-eval.o .libs/libguile_la-evalext.o
> .libs/libguile_la-extensions.o .libs/libguile_la-feature.o
> .libs/libguile_la-fluids.o .libs/libguile_la-fports.o
> .libs/libguile_la-futures.o .libs/libguile_la-gc.o
> .libs/libguile_la-gc-mark.o .libs/libguile_la-gc-segment.o
> .libs/libguile_la-gc-malloc.o .libs/libguile_la-gc-card.o
> .libs/libguile_la-gc-freelist.o .libs/libguile_la-gc_os_dep.o
> .libs/libguile_la-gdbint.o .libs/libguile_la-gh_data.o
> .libs/libguile_la-gh_eval.o .libs/libguile_la-gh_funcs.o
> .libs/libguile_la-gh_init.o .libs/libguile_la-gh_io.o
> .libs/libguile_la-gh_list.o .libs/libguile_la-gh_predicates.o
> .libs/libguile_la-goops.o .libs/libguile_la-gsubr.o
> .libs/libguile_l

Re: guile doesn't build for me

[David Evans]

William Davis wrote:
> Given the way you gave the port command:
>>> bigdaddy$ sudo
>>> /opt/local/bin/port clean guile
>
> I wonder if the bug in macports 1.6 install that failed to setup the
> macports path in your ~.profile has bitten you. if so this bug (and
> many others) is fixed in macports 1.7.  I suggest you download that. 
> Im not sure that sudo port selfupdate will run correctly if your PATH
> is not correctly set.
> William Davis
Yes, updating to MacPorts 1.7.0 is a good idea for everyone.

Have just updated guile to version 1.8.6 in r43824.  Perhaps this will help.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

gtk2 fails to build - libXdamage wrong version

[David Evans]

After gtk2 builds its objects, at the final link stage
I get this error:

i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No 
such file or directory



libXdamage does exist but not this version.

After this error message is displayed there is one final error:

Warning: the following items did not execute (for gtk2): 
org.macports.destroot org.macports.build

DEBUG: invalid command name "::ui_init"
   while executing
"::ui_init $priority $prefix $channels $message"
   ("uplevel" body line 2)
   invoked from within
"uplevel 1 $body"
Error: Unable to upgrade port: 1


OSX 10.5.6
Xcode 3.1.2
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gtk2 fails to build - libXdamage wrong version

[David Evans]

David Evans wrote:
> After gtk2 builds its objects, at the final link stage
> I get this error:
>
> i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No
> such file or directory
>
>
> libXdamage does exist but not this version.
>
> After this error message is displayed there is one final error:
>
> Warning: the following items did not execute (for gtk2):
> org.macports.destroot org.macports.build
> DEBUG: invalid command name "::ui_init"
>while executing
> "::ui_init $priority $prefix $channels $message"
>("uplevel" body line 2)
>invoked from within
> "uplevel 1 $body"
> Error: Unable to upgrade port: 1
>
>
> OSX 10.5.6
> Xcode 3.1.2
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
David --

There's an open ticket on this

http://trac.macports.org/ticket/17356

although the fix isn't completely clear (to me anyway) as yet.

The other Dave Evans


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gtk2 fails to build - libXdamage wrong version

[David Evans]

David Evans wrote:

David Evans wrote:
  

After gtk2 builds its objects, at the final link stage
I get this error:

i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXdamage.1.1.0.dylib: No
such file or directory


libXdamage does exist but not this version.

After this error message is displayed there is one final error:

Warning: the following items did not execute (for gtk2):
org.macports.destroot org.macports.build
DEBUG: invalid command name "::ui_init"
   while executing
"::ui_init $priority $prefix $channels $message"
   ("uplevel" body line 2)
   invoked from within
"uplevel 1 $body"
Error: Unable to upgrade port: 1


OSX 10.5.6
Xcode 3.1.2
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users



David --

There's an open ticket on this

http://trac.macports.org/ticket/17356

although the fix isn't completely clear (to me anyway) as yet.

The other Dave Evans

  
I installed xorg-libXdamage and gtk2 now compiles and links.  Thanks for 
the pointer.


Macports moves in mysterious ways as the installation of xorg-libXdamage 
claimed at

the end that it was already installed.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gtk2 fails to build - libXdamage wrong version

[David Evans]

David Evans wrote:
> I installed xorg-libXdamage and gtk2 now compiles and links.  Thanks
> for the pointer.
>
> Macports moves in mysterious ways as the installation of
> xorg-libXdamage claimed at
> the end that it was already installed.
>
By the time it gets to the end, it is! ;-)

I've wondered about this myself.  Glad you got it working.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: New Mac user and gdk-pixbuf-2-0

[David Evans]

Fabrizio Bartolomucci wrote:
> Hullo everyone,
> sorry if this question has been already asked and in that case I would
> be happy if someone pointed me to the answer.
> I own a Mac PowerBook with MacPorts installed and since some time the
> 'upgrade outdated' procedure loops on the following message and I do not
> know what to do:
>
> Thanks everyone,
> Fabrizio Bartolomucci
>
> No package 'gdk-pixbuf-2.0' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables LIBRSVG_CFLAGS
> and LIBRSVG_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
>
> Error: Unable to upgrade port: 1
> --->  Activating gtk2 @2.14.5_0+x11
> Error: Target org.macports.activate returned: Image error:
> /opt/local/include/gail-1.0/gail/gailwidget.h is being used by the
> active gail port.  Please deactivate this port first, or use the -f flag
> to force the activation.
> Error: The following dependencies failed to build: gtk2
> Error: Unable to upgrade port: 1
>
Fabrizio --

Both gail and gdk-pixbuf-2.0 are now provided by gtk2.  The gail port is
obsolete and
should be removed.

Try this (as per the error message)

sudo port deactivate gail
sudo port activate gtk2
sudo port upgrade outdated

then you should be able to uninstall gail

sudo port uninstall gail



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: New Mac user and gdk-pixbuf-2-0

[David Evans]

Fabrizio Bartolomucci wrote:
> Thanks, but if I do so it asks me for a version; if I specify one at
> random it says it is not installed:
> $ sudo ./port activate gtk2
> --->  The following versions of gtk2 are currently installed:
> --->  gtk2 @2.12.9_0+x11
> --->  gtk2 @2.14.3_2+x11
> --->  gtk2 @2.14.5_0+x11
> Error: port activate failed: Registry error: Please specify the full
> version as recorded in the port registry.
>
> $ sudo ./port activate "gtk2 @2.14.5_0+x11"
> Error: port activate failed: Registry error: gtk2  2.14.5_0+x11 not
> registered as installed.
>
This is because you have more than one version installed. 

To activate the latest version:

sudo port activate gtk2 @2.14.5_0+x11

To remove a previous version (if you don't need it anymore)

sudo port uninstall gtk2 @2.12.9_0+x11

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: skey uninstallable again

[David Evans]

Ed Ravin wrote:
> I see from the archive that this problem also happened last year around
> this time.  The fix then was to add the Fink mirror to the portfolio,
> but skey isn't on that server anymore either.
>
> Why did skey disappear from all those sites in the first place?
>
>   
No idea but it looks like it is available from gentoo mirrors in bz2
format.

Updated master_sites list in r44725.  Try again after next port sync.

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: skey uninstallable again

[David Evans]

Ed Ravin wrote:
> On Fri, Jan 02, 2009 at 08:30:13AM -0800, David Evans wrote:
>   
>> Ed Ravin wrote:
>> 
>>> I see from the archive that this problem also happened last year around
>>> this time.  The fix then was to add the Fink mirror to the portfolio,
>>> but skey isn't on that server anymore either.
>>>
>>> Why did skey disappear from all those sites in the first place?
>>>
>>>   
>>>   
>> No idea but it looks like it is available from gentoo mirrors in bz2
>> format. 
>>
>> Updated master_sites list in r44725.  Try again after next port sync.
>> 
>
> Thanks!  But it still won't install, at least not on my Mac Mini PPC
> running 10.4.  See the output below.  Note that sha1.h is indeed in
> the work dir, but it's not being found.
>   
On my machine (10.4.11 ppc) configure correctly determines that there is
no sha1.h installed
and it subsequently builds without error and installs one as part of the
port.
> Also, I see this skey tarball has a bug that generates incorrect
> SHA1 passwords.  It's been fixed in the NetBSD distribution that the
> code originated from.
>   
Do you have a reference for this?  I downloaded a copy of the tarball from

http://ftp.netbsd.org/pub/NetBSD/packages/distfiles/

and it has the same checksums as the gentoo tarball. 

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: skey uninstallable again

[David Evans]

Ed Ravin wrote:
> I already have sha1.h since it came in from the previous install of skey:
>
> $ locate sha1.h | grep sha1.h$
> /Developer/SDKs/MacOSX10.3.9.sdk/usr/include/httpd/ap_sha1.h
> /Developer/SDKs/MacOSX10.3.9.sdk/usr/include/php/ext/standard/sha1.h
> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/httpd/ap_sha1.h
> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/php/ext/standard/sha1.h
> /opt/local/include/sha1.h
> /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_aqua_qt4-mac/work/qt-mac-opensource-src-4.2.2/examples/network/torrent/3rdparty/sha1.h
> /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_net_ethereal/work/ethereal-0.99.0/epan/sha1.h
> /opt/local/var/macports/software/skey/1.1.5_0/opt/local/include/sha1.h
> /usr/include/httpd/ap_sha1.h
> /usr/include/php/ext/standard/sha1.h
>   
So if you deactivate (or otherwise remove) the old version does the
package install properly?  Was the old
version installed with MacPorts or otherwise?
>
>   
> It was fixed in the NetBSD OS distribution back in 2001:
>
>http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=12045
>>Number: 12045
>>Category:   lib
>>Synopsis:   skey generates incorrect passwords when using SHA-1
>
> but the fix never seems to have made it out of the OS and into pkgsrc.
> I'll have to ask about this on pkgsrc-users.
>
>   
OK, let us know what you find out.  Since you have an interest in this,
if you want, once you have the
port working correctly locally, make a patch relative to the old one and
post it as a ticket on trac.  Since
there is currently no maintainer, you can be it if you like.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Perl 5.8 @5.8.9 does not get on with Ccache during configure

[David Evans]

Perl does not get on with CCACHE during the configure phase.
It works if ccache is disabled.
With ccache enabled in the macports config file I get:

two:~ davidevans$ sudo port -df configure perl5.8
DEBUG: Found port in 
file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8
DEBUG: Changing to port directory: 
/opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8

DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing 
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a 
pre-existing procedure. Target override will not be provided
DEBUG: 'universal_variant no' specified, so not adding the default 
universal variant

DEBUG: Requested variant darwin is not provided by port perl5.8.
DEBUG: Requested variant i386 is not provided by port perl5.8.
DEBUG: Requested variant macosx is not provided by port perl5.8.
DEBUG: Executing org.macports.main (perl5.8)
DEBUG: Skipping completed org.macports.fetch (perl5.8)
DEBUG: Skipping completed org.macports.checksum (perl5.8)
DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
DEBUG: Skipping completed org.macports.extract (perl5.8)
DEBUG: Skipping completed org.macports.patch (perl5.8)
--->  Configuring perl5.8
DEBUG: Using compiler 'Mac OS X gcc 4.0'
DEBUG: Executing org.macports.configure (perl5.8)
DEBUG: Environment: CFLAGS='-O2' CPPFLAGS='-I/opt/local/include' 
CXXFLAGS='-O2' MACOSX_DEPLOYMENT_TARGET='10.5' CPP='ccache 
/usr/bin/cpp-4.0' CXX='ccache /usr/bin/g++-4.0' F90FLAGS='-O2' 
LDFLAGS='-L/opt/local/lib' FCFLAGS='-O2' OBJC='ccache /usr/bin/gcc-4.0' 
INSTALL='/usr/bin/install -c' OBJCFLAGS='-O2' FFLAGS='-O2' CC='ccache 
/usr/bin/gcc-4.0' LC_ALL='C'
DEBUG: Assembled command: 'cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_perl5.8/work/perl-5.8.9" 
&& /bin/sh Configure -des -D prefix='/opt/local' -D 
cppflags="${CPPFLAGS}" -D ldflags="${LDFLAGS}" -D 
vendorprefix='/opt/local' -D man3ext='3pm' -D cc=${CC} -D ld=${CC}'

First let's make sure your kit is complete.  Checking...
Would you like to see the instructions? [n] 
Locating common programs...

Checking compatibility between /bin/echo and builtin echo (if any)...
Symbolic links are supported.
Checking how to test for symbolic links...
You can test for symbolic links with 'test -h'.
Good, your tr supports [:lower:] and [:upper:] to convert case.
Using [:upper:] and [:lower:] to convert case.
ccache: illegal option -- o
You need to find a working C compiler.
Either (purchase and) install the C compiler supplied by your OS vendor,
or for a free C compiler try http://gcc.gnu.org/
I cannot continue any further, aborting.




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: ufraw Not Build

[David Evans]

Altoine Barker wrote:
> /usr/bin/g++-4.0  -O2   -L/opt/local/lib -o ufraw ufraw.o libufraw.a
> -R/opt/local/lib -Wl,-framework -Wl,CoreFoundation -L/opt/local/lib
> -lexiv2 -lintl -lc -liconv -lz -lexpat   -L/opt/local/lib -lglib-2.0
> -lintl -liconv   -L/opt/local/lib -llcms-L/opt/local/lib -lpng12 -lz
>   -L/opt/local/lib -lgtkimageview -lgtk-quartz-2.0 -lgdk-quartz-2.0
> -latk-1.0 -lgio-2.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo
> -lpangoft2-1.0 -lpango-1.0 -lm -lpixman-1 -lfontconfig -lexpat
> -lfreetype -lpng12 -lz -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl
> -liconv   -ltiff -ljpeg -lbz2 -lz  -lintl
> Undefined symbols:
>   "_CMCloseProfile", referenced from:
>   _uf_get_display_profile in libufraw.a(uf_gtk.o)
>   "_CMFlattenProfile", referenced from:
>   _uf_get_display_profile in libufraw.a(uf_gtk.o)
>   "_CMGetProfileByAVID", referenced from:
>   _uf_get_display_profile in libufraw.a(uf_gtk.o)
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[2]: *** [ufraw] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Warning: the following items did not execute (for ufraw):
> org.macports.destroot org.macports.build
> Error: Unable to upgrade port: 1
> 
>
> I upgraded my XCode SDK to XCode 3.1.2 and the problem is the same. TIA
>
> -Altoine
>
Altoine -

>From this I assume that you are building against gtk2 +quartz variant as
the code referenced above is
only built in that case.   The offending symbols are from ColorSync Manager
provided by the ApplicationServices framework which is not referenced by
this link
command.

I just tried building the current ufraw port (0.15) in the gtk2 +quartz
environment
and was unable to reproduce your problem.  The corresponding link command
included the ApplicationServices framework.

So I wonder if you are using the latest version of ufraw?

Please try

sudo port selfupdate
sudo port clean --all ufraw
sudo port upgrade ufraw

and see if you still have the problem.  If so you should probably file a
ticket against ufraw
citing the details.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Perl 5.8.9 port activation failed

[David Evans]

Shawn Protsman wrote:
> On Jan 8, 2009, at 8:51 AM, Frank Schima wrote:
>
>> sudo port -f activate perl5.8
>
> Thanks for the tip, Frank. Unless I'm doing something wrong, it didn't
> work out for me:
>
> @naiad ~] sudo port -f activate perl5.8
> Password:
> --->  The following versions of perl5.8 are currently installed:
> --->  perl5.8 @5.8.8_3+darwin_9
> --->  perl5.8 @5.8.9_1
> Error: port activate failed: Registry error: Please specify the full
> version as recorded in the port registry.
>
> @naiad ~] sudo port -f activate perl5.8.9_1
> Error: port activate failed: Registry error: perl5.8.9_1 not
> registered as installed.
>
> Ideas?
Try

sudo port -f activate perl5.8 @5.8.9_1
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Mesa

[David Evans]

Joel Thibault (MacPorts) wrote:


On Wed, Jan 21, 2009 at 2:49 AM, Jeremy Huddleston 
jeremyhu-at-macports.org  wrote:


Should be fixed in r45750


On Jan 20, 2009, at 23:26, Ryan Schmidt wrote:

Frank J. R. Hanstick wrote:

   Oops.  Forgot xcode and MacPorts:  2.5 and
1.7.0 respectively.



Ok, and based on other output you sent, running Mac OS X 10.4
on a PowerPC Mac.


http://trac.macports.org/ticket/17995


After a selfupdate and cleaning mesa, the problem in #17995 no longer 
occurs, but it can't find the command "makedepend":


DEBUG: Assembled command: 'cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mesa/work/Mesa-7.2" 
&& nice

-n 10 make default INSTALL_DIR=/opt/local X11_DIR=/opt/local'
Making sources for darwin
touch depend
makedepend -fdepend -I. -I../../../include 
-I../../../include/GL/internal -I../../../src/mesa/main 
-I../../../src/mesa/glapi   glcontextmodes.c clientattrib.c
 compsize.c eval.c glxcmds.c glxcurrent.c glxext.c glxextensions.c 
indirect.c indirect_init.c indirect_size.c indirect_window_pos.c 
indirect_texture_compressi
on.c indirect_transpose_matrix.c indirect_vertex_array.c 
indirect_vertex_program.c pixel.c pixelstore.c render2.c renderpix.c 
single2.c singlepix.c vertarr.c
xfont.c glx_pbuffer.c glx_query.c drisw_glx.c dri_common.c dri_glx.c 
XF86dri.c glxhash.c \
../../../src/mesa/main/dispatch.c 
../../../src/mesa/glapi/glapi.c ../../../src/mesa/glapi/glthread.c

make[2]: makedepend: Command not found
make[2]: *** [depend] Error 127
make[1]: *** [subdirs] Error 1
make: *** [default] Error 1

[also Xcode 2.5 and OS X 10.4 on PPC but a newer Trunk MacPorts]


--
Joel Thibault [AIM: Jole Tebo]
Software Engineer in Boston
See also http://trac.macports.org/ticket/18132 


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: bug in asciidoc port?

[David Evans]

Joerg van den Hoff wrote:

hi there,

I recently installed the `asciidoc` port (MacOS 10.4.11) and
I noted that the first line in the python source of `asciidoc`
reads:

#!/usr/bin/env python

which finds the system's python binary in /usr/bin. at least
for me this is version 2.3.5 but, `asciidoc' needs the macports
provided python2.5. so the first line should read

#!/usr/bin/env python2.5

or probably even better specify directly the path to the
correct python executable.

I presume...

regards,

joerg

  
Another solution is to use port python_select (which I think is 
recommended by the python25 port)  to select which

python binary will be used in the default case

sudo port install python_select
sudo python_select python25

then

% python --version
Python 2.5.4

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

some kde ports, phonon, and qt4-mac

[David Evans]

While upgrading phonon I get this message:

-- Found Qt-Version 4.4.3 (using /opt/local/libexec/qt4-mac/bin/qmake)
-- Found Threads: TRUE
-- Found Automoc4: /opt/local/bin/automoc4
CMake Error at CMakeLists.txt:134 (message):
 Qt compiled without support for -fvisibility=hidden.  This will break
 plugins and linking of some applications.  Please fix your Qt 
installation.


I get the same message with these ports:

kdebase4   4.1.3_3 < 4.2.0_0
kdelibs4   4.1.3_3 < 4.2.0_0
kdepimlibs44.1.3_3 < 4.2.0_0
phonon 4.2.0_3 < 4.3.0_0 


I've recompiled qt4-mac and still get the same message.

It has been like this for several weeks.

Any suggestions gratefully received.
I don't know why I am the only one getting the error.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: mesa conflict with xorg-glproto

[David Evans]

Takashi Yoshida wrote:

Hi,

I'm also wondering about the same thing.
Any clue?

Thanks,

--
Takashi Yoshida

email: taka...@takashiyoshida.org
web: http://takashiyoshida.org

On Feb 24, 2009, at 11:14 PM, William Davis wrote:



--->  Activating mesa @7.2_5+hw_render
Error: Target org.macports.activate returned: Image error: 
/opt/local/include/GL/glxint.h is being used by the active 
xorg-glproto port.  Please deactivate this port first, or use the -f 
flag to force the activation.

Error: The following dependencies failed to build: mesa
Error: Unable to upgrade port: 1

Should I use -f as this mesg indicates?

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.6 Darwin 9.5.0
XQuartz 2.3.2 (xorg-server 1.4.2-apple31)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Well, this is anecdotal evidence at best, but after forcing activation
of mesa @7.2_5+hw_render on 10.4.11 ppc, GL based GTK applications
that I have tried so far (using the gtkglgraph widget, for instance)
seem to build and run properly.

However, I'd defer to Jeremy for any official guidance.

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: libpixbufloader

[David Evans]

Andy Schmitt wrote:
I just compiled something that had expected to find: 
/lib/gtk-2.0/*/loaders/libpixbufloader-bmp.so


Googling suggests that's a pretty common location for that folder and 
that perhaps gdk-pixbuf was installed along with gtk2 as recently as 
2.8. But I had to manually install the gdk-pixbuf port and adjust that 
path to /lib/gdk-pixbuf/loaders/libpixbufloader-bmp.so.


So, did something change or did I manage to screw something up 
somewhere along the way.


andy
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Andy --

I think you are mixing two different versions of gtk.

The gdk_pixbuf library is now included as part of gtk2 and bmp file
format is one of the default file types that can be loaded or
saved without using an external loader module. (also jpeg, png, ico at
least)

The command

gdk-pixbuf-query-loaders

will show you what additional external loader modules are installed and
where. These are usually installed by other ports
to add support for their own file types.

The port gdk-pixbuf is an old version that is compatible with gtk1,
glib1 where it was a separate library and a loader module was required
for bmp.

Perhaps the application you are trying to build is a gtk1 application?
If you have port gdk-pixbuf installed then you also have its
dependencies installed gtk1, glib1.

Try

port contents 

to see what files have been installed for a given port.

gtk1 and gtk2 can coexist without interfering with each other AFAIK. (As
long as you don't link them together) ;-)

Dave



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: libpixbufloader

[David Evans]

David Evans wrote:

Andy Schmitt wrote:
I just compiled something that had expected to find: 
/lib/gtk-2.0/*/loaders/libpixbufloader-bmp.so


Googling suggests that's a pretty common location for that folder and 
that perhaps gdk-pixbuf was installed along with gtk2 as recently as 
2.8. But I had to manually install the gdk-pixbuf port and adjust 
that path to /lib/gdk-pixbuf/loaders/libpixbufloader-bmp.so.


So, did something change or did I manage to screw something up 
somewhere along the way.


andy
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Andy --

I think you are mixing two different versions of gtk.

The gdk_pixbuf library is now included as part of gtk2 and bmp file
format is one of the default file types that can be loaded or
saved without using an external loader module. (also jpeg, png, ico at
least)

The command

gdk-pixbuf-query-loaders

will show you what additional external loader modules are installed and
where. These are usually installed by other ports
to add support for their own file types.

The port gdk-pixbuf is an old version that is compatible with gtk1,
glib1 where it was a separate library and a loader module was required
for bmp.

Perhaps the application you are trying to build is a gtk1 application?
If you have port gdk-pixbuf installed then you also have its
dependencies installed gtk1, glib1.

Try

port contents 

to see what files have been installed for a given port.

gtk1 and gtk2 can coexist without interfering with each other AFAIK. (As
long as you don't link them together) ;-)

Dave

Just for completeness here is the list of loaders that are currently 
built in to  the gdk_pixbuf library in gtk2 (from the configure output):


checking pixbuf loaders to build... 
ani,icns,pcx,ras,tga,png,pnm,wbmp,xbm,xpm,jasper,bmp,gif,ico,jpeg,tiff



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: libpixbufloader

[David Evans]

Andy Schmitt wrote:



So wait, are you saying that /opt/local/lib/gtk-2.0/2.10.0/loaders 
*should* be present after gtk2 is installed?
No, I'm saying this is where it looks for loaders that are installed by 
other ports.  This path is hard coded into

the library (determined at configure). For instance on my system

# GdkPixbuf Image Loader Modules file
# Automatically generated file, do not edit
# Created by gdk-pixbuf-query-loaders from gtk+-2.14.7
#
# LoaderDir = /opt/local/lib/gtk-2.0/2.10.0/loaders
#
"/opt/local/lib/gtk-2.0/2.10.0/loaders/libopenraw_pixbuf.so"
"Digital camera RAW" 0 "gtk20" "Digital camera RAW images loader." "LGPL"
"image/x-adobe-dng" "image/x-canon-cr2" "image/x-canon-crw" 
"image/x-nikon-nef" "image/x-olympus-orf" "image/x-pentax-pef" 
"image/x-sony-arw" "image/x-epson-erf" "image/x-minolta-mrw" ""

"dng" "cr2" "crw" "nef" "orf" "pef" "arw" "erf" "mrw" ""
"MM *" "  z " 80
"II* \020   CR\002 " "   z zzz   z" 100
"II* " "   z" 80
"IIRO" "" 100
" MRM" "z   " 100
"II\032   HEAPCCDR" "   zzz" 100

"/opt/local/lib/gtk-2.0/2.10.0/loaders/svg_loader.so"
"svg" 2 "gtk20" "Scalable Vector Graphics" "LGPL"
"image/svg+xml" "image/svg" "image/svg-xml" "image/vnd.adobe.svg+xml" 
"text/xml-svg" "image/svg+xml-compressed" ""

"svg" "svgz" "svg.gz" ""
" libopenraw_pixbuf.so is installed by port libopenraw to allow loading of 
raw digital camera images

svg_loader.so is installed by port librsvg to allow loading of svg images

nothing installed by gtk2 because the loaders for the formats I 
mentioned in the last email are not loadable modules

but are built into the gdk_pixbuf library directly.


No it's gtk2. The application in question is NetRadiant- an attempt at 
maintaining a reliable stabilized distribution of gtkRadiant 1.5, 
since no others are being maintained. Rudolf Polzer has 
single-handedly taken this on, but I don't think he has the resources 
to be testing OS X builds. Historically most OS X Radiant SRC and 
binaries needed/were built with the Fink tools and libraries. Long 
story short: the current post-make scripts packs up the executables 
and dynamic libraries into an .app, but they assumed Fink, and in 
particular /sw/lib/gtk-2.0/*/loaders/libpixbufloader-bmp.so.


If the app is built against the current gtk2 port, 
libpixbufloader-bmp.so is unnecessary and will never be called by the 
program because
the built in loader code will be used instead for loading a bmp.  So I 
think you can modify the post-make script to skip this and it should

work.

Doing:
port contents gtk2
shows no sign of any of the libpixbufloader-xxx.so files
Right, shouldn't be any unless some other port puts one here to extend 
the range of files that can be loaded beyond what's built in.


BTW does "port contents " return what *was installed* with that 
port or what *was supposed to have been installed*?


It shows what was actually installed -- there's no way in MacPorts to 
find out what *would* be installed without actually doing it.
So, I don't know where that leaves me. Thanks for the informative 
reply Dave.
Well, I hope this helps.  To summarize, I don't think you need the 
external bmp loader module at all.  It should work without it (assuming

everything built properly).

This is a common misunderstanding partly because gkdpixbuf's name 
doesn't make it clear this is a gtk1 version.  It will probably go
away one of these days (along with gtk1 and glib1) but for now there are 
a few gtk1 ports left that depend upon it.


Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: How to run

[David Evans]

Keith Kaiser wrote:

OK, I've installed an application using MacPorts. How do I run it?

Actually, you can

port info 

and go look at the homepage there for information about the software.

Another possibility is to

port contents 

to see what was installed (maybe documentation, binaries, etc)

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: How to run

[David Evans]

Keith Kaiser wrote:

OK, I've installed an application using MacPorts. How do I run it?


Which one?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: some kde ports, phonon, and qt4-mac

[David Evans]

Previously I said:

>While upgrading phonon I get this message:
>
>-- Found Qt-Version 4.4.3 (using /opt/local/libexec/qt4-mac/bin/qmake)
>-- Found Threads: TRUE
>-- Found Automoc4: /opt/local/bin/automoc4
>CMake Error at CMakeLists.txt:134 (message):
> Qt compiled without support for -fvisibility=hidden.  This will break
> plugins and linking of some applications.  Please fix your Qt
installation.
>
>I get the same message with these ports:
>
>kdebase4   kdelibs4   kdepimlibs4   phonon
>I've recompiled qt4-mac and still get the same message.


I believe I have now found the cause of this.  I think it is because
of ccache.  I've disabled ccache in /opt/local/etc/macports/macports.conf
and recompiled qt4-mac (both the old version and the one that appeared
a couple of days ago.  Now I no longer get the above message about
-fvisibility=hidden.  Rebuilding qt4-mac with ccache makes the message
reappear.

See also bug 18912 which says more or less the same thing.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: can't build mesa upgrade 7.4

[David Evans]

Chris Jones wrote:

Hi,

Mesa fails for me also, but with a slightly different error.

--->  Fetching mesa
--->  Attempting to fetch MesaLib-7.4.tar.bz2 from 
http://kent.dl.sourceforge.net/mesa3d
--->  Attempting to fetch MesaGLUT-7.4.tar.bz2 from 
http://kent.dl.sourceforge.net/mesa3d
--->  Attempting to fetch AppleSGLX-56.tar.bz2 from 
http://arn.se.distfiles.macports.org/mesa
--->  Attempting to fetch AppleSGLX-56.tar.bz2 from 
http://trd.no.distfiles.macports.org/mesa
--->  Attempting to fetch AppleSGLX-56.tar.bz2 from 
http://distfiles.macports.org/mesa

--->  Verifying checksum(s) for mesa
--->  Extracting mesa
--->  Applying patches to mesa
--->  Configuring mesa
--->  Building mesa
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mesa/work/Mesa-7.4" 
&& make default INSTALL_DIR=/opt/local " returned error 2
Command output: dri2.c:164: error: 'xDRI2AuthenticateReply' undeclared 
(first use in this function)

dri2.c:164: error: syntax error before 'rep'
dri2.c:169: error: 'sz_xDRI2AuthenticateReq' undeclared (first use in 
this function)

dri2.c:169: error: syntax error before ')' token
dri2.c:169: error: 'X_DRI2Authenticate' undeclared (first use in this 
function)

dri2.c:175: error: 'rep' undeclared (first use in this function)
dri2.c: In function 'DRI2GetBuffers':
dri2.c:227: error: 'xDRI2GetBuffersReply' undeclared (first use in 
this function)

dri2.c:227: error: syntax error before 'rep'
dri2.c:228: error: 'xDRI2GetBuffersReq' undeclared (first use in this 
function)

dri2.c:228: error: 'req' undeclared (first use in this function)
dri2.c:230: error: 'xDRI2Buffer' undeclared (first use in this function)
dri2.c:230: error: syntax error before 'repBuffer'
dri2.c:237: error: 'sz_xDRI2GetBuffersReq' undeclared (first use in 
this function)

dri2.c:237: error: syntax error before ')' token
dri2.c:237: error: 'X_DRI2GetBuffers' undeclared (first use in this 
function)

dri2.c:246: error: 'rep' undeclared (first use in this function)
dri2.c:258: error: 'repBuffer' undeclared (first use in this function)
dri2.c: In function 'DRI2CopyRegion':
dri2.c:283: error: 'xDRI2CopyRegionReq' undeclared (first use in this 
function)

dri2.c:283: error: 'req' undeclared (first use in this function)
dri2.c:284: error: 'xDRI2CopyRegionReply' undeclared (first use in 
this function)

dri2.c:284: error: syntax error before 'rep'
dri2.c:289: error: 'sz_xDRI2CopyRegionReq' undeclared (first use in 
this function)

dri2.c:289: error: syntax error before ')' token
dri2.c:289: error: 'X_DRI2CopyRegion' undeclared (first use in this 
function)

dri2.c:297: error: 'rep' undeclared (first use in this function)
make[2]: *** [dri2.o] Error 1
make[1]: *** [subdirs] Error 1
make: *** [default] Error 1

Error: Unable to upgrade port: 1

cheers Chris


See  https://trac.macports.org/ticket/19105
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: totem-pl-parser not upgrading from 2.22.3_0 to 2.24.4_0

[David Evans]

Ryan Schmidt wrote:


On Apr 9, 2009, at 07:16, David Rowe wrote:

This upgrading is failing during the build stage - here is an extract 
from the error report:


[snip]


ld: library not found for -lssl3


[snip]

There doesn't seem to be a maintainer for this port. Does anyone know 
how to fix the problem?


So the question is, what port is supposed to provide libssl3.dylib, 
and is that port installed on your system?


/opt/local/lib/nss/libssl3.dylib is provided by port nss

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: totem-pl-parser not upgrading from 2.22.3_0 to 2.24.4_0

[David Evans]

/opt/local/lib/nss/libssl3.dylib is provided by port nss


I do have port  nss @3.12_1 (active) installed on my system.
In /opt/local/lib/nss/ there is an entry: libssl3.dylib created on 3 
April 09


Does that make it any clearer?

Thanks

David Rowe

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


totem-pl-parser depends on evolution-data-server
evolution-data-server depends on nss

so the -lssl3 is probably coming via pkg-config from 
evolution-data-server but I see no  -L/opt/local/lib/nss to allow it to 
find the library


nss was changed 4/3/2009 r49081 to move the libraries from nss from 
/opt/local/lib to /opt/local/lib/nss


so I'm guessing that if you haven't rebuilt evolution-data-server since 
nss was last updated then it could be providing the old pkg-config

information instead of the new.

if you think this is the case then try rebuilding evolution-data-server

sudo port -fn upgrade  evolution-data-server

and see if this fixes the problem
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Gimp 2.6 & Pango 1.8 : no font rendering

[David Evans]

Ryan Schmidt wrote:

Pango reports the following when starting gimp:

Dynamic session lookup supported but failed: launchd did not provide 
a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide 
a socket path, verify that org.freedesktop.dbus-session.plist is loaded!


I get these messages too. Then again, I also have not started dbus, 
because I did not feel like starting a system service of unknown 
purpose just to run an application. But, you may want to activate dbus.
The purpose of dbus here is to handle the case of more than one instance 
of gimp being active.  If you launch gimp initially with a file name
on the command line, it will open that file.  If you launch a second 
instance with a different file name, the second will pass the file name
to the first via dbus and terminate with the result that the original 
now has images open in two windows, etc.  So not likely to have anything

to do with fonts at all.

(gimp:259): Pango-WARNING **: Error loading GDEF table 0x6EAD

(gimp:259): Pango-WARNING **: Error loading GSUB table 0x6EAD

(gimp:259): Pango-WARNING **: Error loading GPOS table 0x6EAD


I've been getting these errors forever, with other pango-using 
software. I don't know what to do about it. The latest bug on this is 
filed here:


http://trac.macports.org/ticket/19171


I too see these with other (X11) apps using pango (inkscape for 
instance).  They seem to be harmless but I don't really understand it 
either.



As the maintainer of gimp2 (both X11 and no_x11/quartz versions) and who 
does a lot of development in the quartz environment, in my
experience, the only practical way to avoid this type of problem is to 
use separate instances of MacPorts for X11 and for no_x11/quartz.


While you might be able to get a mixed instance to work, the effort is 
tremendous because to build and run a specific version you
have to make sure that not only the port in question but all of its 
dependencies are built with the correct variants (in this case +no_x11
+quartz).  So Ryan's solution to set up a separate instance of MacPorts 
with a different base path is really what I recommend.  Then build
all your +no_x11 +quartz variants there (setting these as global 
variants in $prefix/etc/macports/variants.conf).  You can easily then change
from an X11 instance to a quartz instance by just changing your PATH to 
point at the one you want.  I am currently maintaining 3 such

X11, no_x11/quartz and system_x11 with good success.

The only other caveat is that using the trunk version of MacPorts 
helpful when doing this as it is the only version that currently
honors the variants of dependents when doing an upgrade.  Hopefully a 
released version of MacPorts with this functionality

will be released before long.

So using a clean no_x11/quartz environment for gimp2, I get no error 
messages at all starting gimp and the same results as Ryan

has displayed.

I suspect that a  number of the reports of GOffice and other apps not 
working correctly no_x11/quartz is due to the same problem of mixing X11
and no_x11 in the same instance of MacPorts -- not realistic to think 
that you can do this and have the right selection of ports/variants

active at any given point in time.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Gimp 2.6 & Pango 1.8 : no font rendering

[David Evans]

Ryan Schmidt wrote:
the recommendation is that you must make the choice to use quartz and 
no_x11 before you have installed any ports, and if you have installed 
any ports, you should remove them, then set the default variants, or 
else as David said, install a new MacPorts to a new prefix where you 
set the default variants and then install your ports.

Exactly.

Glad to see that you solved your problem, Luc.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Devhelp does not work

[David Evans]

David Trem wrote:

Hello,

I'm running into trouble with devhelp.
It returns the following error when trying to run it either froom 
glade3 or the commande line:


(devhelp:98244): Devhelp-CRITICAL **: 
bacon_message_connection_get_is_server: assertion `conn != NULL' failed


(devhelp:98244): Devhelp-CRITICAL **: bacon_message_connection_send: 
assertion `conn != NULL' failed



I'm on MacBook OSX 10.5.6 (Intel)
MacPorts 1.710
Fresh "upgrade outdated" done


David,

I can't reproduce this on 10.4.11 ppc with devhelp @0.22_0.  Works fine 
for me with both from glade-3 and the command line.


However, I'm looking further to see where this message is coming from.

In addition, am working on updating to 0.23 although there are some 
build problems with latest webkit-gtk.


Suggest you open ticket on trac about this.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gnome-menus v kde4

[David Evans]

William Davis wrote:


DEBUG: Executing org.macports.activate (gnome-menus)
--->  Activating gnome-menus @2.26.1_0
Error: Target org.macports.activate returned: Image error: 
/opt/local/etc/xdg/menus/applications.menu is being used by the active 
kdelibs4 port.  Please deactivate this port first, or use 'port -f 
activate gnome-menus' to force the activation.
Warning: the following items did not execute (for gnome-menus): 
org.macports.activate

Error: The following dependencies failed to build: gnome-menus
DEBUG: Image error: /opt/local/etc/xdg/menus/applications.menu is 
being used by the active kdelibs4 port.  Please deactivate this port 
first, or use 'port -f activate gnome-menus' to force the activation.

while executing
"_activate_contents $name $imagefiles $imagedir"
(procedure "portimage::activate" line 57)
Error: Unable to upgrade port: 1
macintosh:~ frstan$

Is it safe to use -f here?
Probably not. 

If you're trying to set up a complete desktop environment (this file 
defines a desktop applications menu) then you probably need to decide

whether you want to use gnome or kde.

If you are just running some gnome apps and some kde apps (without a 
complete desktop environment) then it may not matter. In which

case, maybe you don't need to install gnome-menus?

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gnome-menus v kde4

[David Evans]

I've been working through the gnome dependency tree from the bottom up 
upgrading to 2.26 which is way over due.  However, I think on going
maintainership of gnome is more than a one man task.  So I'm willing to 
be a co-maintainer if others will also participate. 

With regard to QA, a major problem with MacPorts is the lack of a 
separate port tree for ports under test.  With something as far reaching
as gnome or kde, when a major revision occurs, it would be better to 
work out all the kinks for the suite of ports in such a testing environment
without inflicting it on the MacPorts user community at large.  Then, 
the next step would be to establish a testing protocol and recruiting
a group of testers who are willing to work with less than perfect ports. 


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gnome-menus v kde4

[David Evans]

I've been working through the gnome dependency tree from the bottom up
upgrading to 2.26 which is way over due.  However, I think on going
maintainership of gnome is more than a one man task.  So I'm willing to
be a co-maintainer if others will also participate.

With regard to QA, a major problem with MacPorts is the lack of a
separate port tree for ports under test.  With something as far reaching
as gnome or kde, when a major revision occurs, it would be better to
work out all the kinks for the suite of ports in such a testing environment
without inflicting it on the MacPorts user community at large.  Then,
the next step would be to establish a testing protocol and recruiting
a group of testers who are willing to work with less than perfect ports.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gnome-menus v kde4

[David Evans]

Rainer Müller wrote:

David Evans wrote:
  

With regard to QA, a major problem with MacPorts is the lack of a
separate port tree for ports under test.  With something as far reaching
as gnome or kde, when a major revision occurs, it would be better to
work out all the kinks for the suite of ports in such a testing environment
without inflicting it on the MacPorts user community at large.  Then,
the next step would be to establish a testing protocol and recruiting
a group of testers who are willing to work with less than perfect ports.



I still think we do not have the resources to support more than one
tree. With so many unmaintained ports, who would decide if updates
should go into stable or not?

Rainer

  
Yes, I agree that is already a problem.  For instance, there is code in 
MacPorts trunk that would be
useful in a release but it has been deferred because "it hasn't been 
tested enough" but there is no
plan in place to test or any criteria to say when something is ready for 
release.  Thus there is no

way to advance the situation other than by ad hoc decision.

Even if we don't have a lot of testers yet, if we create a role for 
them, maybe they will come.  At any
rate, because individual contributors may not have hardware or other 
resources to test ports in all configurations
it makes sense to make testing a group activity and come up with some 
basic guidelines as to what constitutes

good enough to turn loose on the user community.

Ryan's idea to informally make test branches for specific collections of 
ports while they are being upgraded
and tested as a whole is a reasonable alternative to a formal test tree 
and is a whole lot better QA than just
committing the ports with minimal testing as see if anyone complains 
(and they do!).


So how much testing is enough (open topic for discussion).

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: sudo port upgrade outdated

[David Evans]

Frank J. R. Hanstick wrote:

Hello,
Just a report to keep you updated on how upgrading went.  The 
following successfully upgraded:  pango, gtk2, popt, libproxy, 
gnome-platform-suite (following the new installations of: 
 libgweather, libical, libarchive, and gvfs), lcms, libcanberra, 
metis, and python26.  libcanberra had failed to upgrade in earlier 
attempts.  The following still failed:


evolution-data-server (new port file displayed prior to the attempt) 
with the following error message:


/usr/bin/gcc-4.0 -dynamiclib  -o ../.libs/libgdraw.4.0.7.dylib 
 .libs/choosericons.o .libs/ctlvalues.o .libs/drawboxborder.o 
.libs/gaskdlg.o .libs/gbuttons.o .libs/gcolor.o .libs/gchardlg.o 
.libs/gcontainer.o .libs/gdraw.o .libs/gdrawbuildchars.o 
.libs/gdrawerror.o .libs/gdrawtxt.o .libs/gdrawtxtinit.o 
.libs/gfilechooser.o .libs/gfiledlg.o .libs/ggadgets.o 
.libs/ggroupbox.o .libs/gimageclut.o .libs/gimagecvt.o 
.libs/gimagepsdraw.o .libs/gimagewriteeps.o .libs/gdrawgimage.o 
.libs/gimagexdraw.o .libs/gkeysym.o .libs/glist.o .libs/gmenu.o 
.libs/gprogress.o .libs/gpsdraw.o .libs/gpstxtinit.o .libs/gradio.o 
.libs/gresource.o .libs/gresourceimage.o .libs/gresedit.o 
.libs/gsavefiledlg.o .libs/gscrollbar.o .libs/gtabset.o 
.libs/gtextfield.o .libs/gtextinfo.o .libs/gwidgets.o .libs/gxdraw.o 
.libs/gxcdraw.o .libs/ghvbox.o .libs/gmatrixedit.o .libs/gdrawable.o 
.libs/gspacer.o .libs/xkeysyms_unicode.o  -L/opt/local/lib 
-L/usr/local/lib ../.libs/libgutils.dylib 
/opt/local/lib/libgunicode.dylib ../.libs/libgunicode.dylib 
/opt/local/lib/libiconv.dylib -lpthread -L/usr/X11R6/lib 
/opt/local/lib/libSM.dylib /opt/local/lib/libICE.dylib 
/opt/local/lib/libXi.dylib /opt/local/lib/libXext.dylib 
/opt/local/lib/libXau.dylib /opt/local/lib/libXdmcp.dylib 
/opt/local/lib/libX11.dylib /opt/local/lib/libxkbui.dylib 
/opt/local/lib/libXt.dylib /opt/local/lib/libxkbfile.dylib 
 -Wl,/System/Library/Frameworks/CoreServices.framework/CoreServices 
-Wl,/System/Library/Frameworks/Carbon.framework/Carbon -install_name 
 /opt/local/lib/libgdraw.4.dylib -compatibility_version 5 
-current_version 5.7 -Wl,-single_module

ld: Undefined symbols:
_utf8_strchr
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link 
edit command failed

make[1]: *** [../libgdraw.la] Error 1
make: *** [libgdraw] Error 2

along with qemu and textlive_base.

Frank J. R. Hanstick
tro...@comcast.net 

The developers of evolution-data-server apparently never contemplated 
the MacPorts upgrade scenario, that is, building a new copy
while the old copy is still installed -- because of the way the link 
command is ordered, it will link against the old libraries in preference
to the new ones if they exist. 


So instead of upgrading evolution-data-server  try this

sudo port deactivate evolution-data-server
sudo port install evolution-data-server

It's a work around but it may help.  If not please file a ticket.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: sudo port upgrade outdated

[David Evans]

Frank J. R. Hanstick wrote:

Hello,
Evolution-data-server installed under the guidelines provided.  Is 
anyone in a discussion with the developers of evolution-data-server to 
correct this oversight because I do not know of too many people who 
uninstall before upgrading and I do not think evolution-data-server is 
so perfect that it would never need to be upgraded.  This would not be 
a problem just with MacPorts; but, everyone who wishes to upgrade an 
already installed evolution-data server.


On Apr 28, 2009, at 10:26 PM, David Evans wrote:


Frank J. R. Hanstick wrote:

Hello,
Just a report to keep you updated on how upgrading went.  The 
following successfully upgraded:  pango, gtk2, popt, libproxy, 
gnome-platform-suite (following the new installations of:  
libgweather, libical, libarchive, and gvfs), lcms, libcanberra, 
metis, and python26.  libcanberra had failed to upgrade in earlier 
attempts.  The following still failed:


evolution-data-server (new port file displayed prior to the attempt) 
with the following error message:


/usr/bin/gcc-4.0 -dynamiclib  -o ../.libs/libgdraw.4.0.7.dylib  
.libs/choosericons.o .libs/ctlvalues.o .libs/drawboxborder.o 
.libs/gaskdlg.o .libs/gbuttons.o .libs/gcolor.o .libs/gchardlg.o 
.libs/gcontainer.o .libs/gdraw.o .libs/gdrawbuildchars.o 
.libs/gdrawerror.o .libs/gdrawtxt.o .libs/gdrawtxtinit.o 
.libs/gfilechooser.o .libs/gfiledlg.o .libs/ggadgets.o 
.libs/ggroupbox.o .libs/gimageclut.o .libs/gimagecvt.o 
.libs/gimagepsdraw.o .libs/gimagewriteeps.o .libs/gdrawgimage.o 
.libs/gimagexdraw.o .libs/gkeysym.o .libs/glist.o .libs/gmenu.o 
.libs/gprogress.o .libs/gpsdraw.o .libs/gpstxtinit.o .libs/gradio.o 
.libs/gresource.o .libs/gresourceimage.o .libs/gresedit.o 
.libs/gsavefiledlg.o .libs/gscrollbar.o .libs/gtabset.o 
.libs/gtextfield.o .libs/gtextinfo.o .libs/gwidgets.o .libs/gxdraw.o 
.libs/gxcdraw.o .libs/ghvbox.o .libs/gmatrixedit.o .libs/gdrawable.o 
.libs/gspacer.o .libs/xkeysyms_unicode.o  -L/opt/local/lib 
-L/usr/local/lib ../.libs/libgutils.dylib 
/opt/local/lib/libgunicode.dylib ../.libs/libgunicode.dylib 
/opt/local/lib/libiconv.dylib -lpthread -L/usr/X11R6/lib 
/opt/local/lib/libSM.dylib /opt/local/lib/libICE.dylib 
/opt/local/lib/libXi.dylib /opt/local/lib/libXext.dylib 
/opt/local/lib/libXau.dylib /opt/local/lib/libXdmcp.dylib 
/opt/local/lib/libX11.dylib /opt/local/lib/libxkbui.dylib 
/opt/local/lib/libXt.dylib /opt/local/lib/libxkbfile.dylib  
-Wl,/System/Library/Frameworks/CoreServices.framework/CoreServices 
-Wl,/System/Library/Frameworks/Carbon.framework/Carbon 
-install_name  /opt/local/lib/libgdraw.4.dylib 
-compatibility_version 5 -current_version 5.7 -Wl,-single_module

ld: Undefined symbols:
_utf8_strchr
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link 
edit command failed

make[1]: *** [../libgdraw.la] Error 1
make: *** [libgdraw] Error 2

along with qemu and textlive_base.

Frank J. R. Hanstick
tro...@comcast.net <mailto:tro...@comcast.net>

The developers of evolution-data-server apparently never contemplated 
the MacPorts upgrade scenario, that is, building a new copy
while the old copy is still installed -- because of the way the link 
command is ordered, it will link against the old libraries in preference
to the new ones if they exist. 
So instead of upgrading evolution-data-server  try this


sudo port deactivate evolution-data-server
sudo port install evolution-data-server

It's a work around but it may help.  If not please file a ticket.

Dave

Yes.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: sudo port upgrade outdated

[David Evans]

Frank J. R. Hanstick wrote:
evolution-data-server (new port file displayed prior to the attempt) 
with the following error message:


/usr/bin/gcc-4.0 -dynamiclib  -o ../.libs/libgdraw.4.0.7.dylib  
.libs/choosericons.o .libs/ctlvalues.o .libs/drawboxborder.o 
.libs/gaskdlg.o .libs/gbuttons.o .libs/gcolor.o .libs/gchardlg.o 
.libs/gcontainer.o .libs/gdraw.o .libs/gdrawbuildchars.o 
.libs/gdrawerror.o .libs/gdrawtxt.o .libs/gdrawtxtinit.o 
.libs/gfilechooser.o .libs/gfiledlg.o .libs/ggadgets.o 
.libs/ggroupbox.o .libs/gimageclut.o .libs/gimagecvt.o 
.libs/gimagepsdraw.o .libs/gimagewriteeps.o .libs/gdrawgimage.o 
.libs/gimagexdraw.o .libs/gkeysym.o .libs/glist.o .libs/gmenu.o 
.libs/gprogress.o .libs/gpsdraw.o .libs/gpstxtinit.o .libs/gradio.o 
.libs/gresource.o .libs/gresourceimage.o .libs/gresedit.o 
.libs/gsavefiledlg.o .libs/gscrollbar.o .libs/gtabset.o 
.libs/gtextfield.o .libs/gtextinfo.o .libs/gwidgets.o .libs/gxdraw.o 
.libs/gxcdraw.o .libs/ghvbox.o .libs/gmatrixedit.o .libs/gdrawable.o 
.libs/gspacer.o .libs/xkeysyms_unicode.o  -L/opt/local/lib 
-L/usr/local/lib ../.libs/libgutils.dylib 
/opt/local/lib/libgunicode.dylib ../.libs/libgunicode.dylib 
/opt/local/lib/libiconv.dylib -lpthread -L/usr/X11R6/lib 
/opt/local/lib/libSM.dylib /opt/local/lib/libICE.dylib 
/opt/local/lib/libXi.dylib /opt/local/lib/libXext.dylib 
/opt/local/lib/libXau.dylib /opt/local/lib/libXdmcp.dylib 
/opt/local/lib/libX11.dylib /opt/local/lib/libxkbui.dylib 
/opt/local/lib/libXt.dylib /opt/local/lib/libxkbfile.dylib  
-Wl,/System/Library/Frameworks/CoreServices.framework/CoreServices 
-Wl,/System/Library/Frameworks/Carbon.framework/Carbon 
-install_name  /opt/local/lib/libgdraw.4.dylib 
-compatibility_version 5 -current_version 5.7 -Wl,-single_module

Frank,

I'm a little concerned that the term "-L/usr/X11R6/lib 
/opt/local/lib/libSM.dylib /opt/local/lib/libICE.dylib" is appearing in 
the link command
above.  This implies that one or more of evolution-data-servers's 
dependents is configuring against the 10.4 system supplied version of X11
instead of the xorg version from MacPorts and is passing this along via 
pkgconfig.  Probably something left over from the transition to the
xorg libraries. 


Try the following to see where this is coming from

grep X11R6 /opt/local/lib/pkgconfig/*.pc

and if you see any hits then

port provides /opt/local/lib/pkgconfig/.pc

to see which port is providing that pkgconfig file.

It may then be as simple as using

sudo port -fn upgrade 

to rebuild the effected port to fix this.  But if there is more than one 
such file, then be sure to check and see if one depends on the other
and start with the earliest dependency first to keep it from passing the 
bad term to the next etc.


Here

sudo port depsshows a port's dependencies

and

sudo port dependents   shows installed ports that depend on this port

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: sudo port upgrade outdated

[David Evans]

Frank J. R. Hanstick wrote:
I assume that this exercise has nothing to do with 
evolution-data-server failing to upgrade because of a previous 
installation; but, a side issue.
That's right.  Just cleaning things up.  at-spi probably hadn't  been 
rebuilt since the change over to xorg was completed. 
___

macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: error installing ffmpeg

[David Evans]

Travis Griggs wrote:

Fwd'ed, since I sent from the wrong account originally.



I'm trying to install ffmpeg. Here's what happens:

iboard17:~ travis$ sudo port install ffmpeg
--->  Building libsdl
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_libsdl/work/SDL-1.2.13" 
&& make all " returned error 2
Command output: /bin/sh ./libtool --mode=compile /usr/bin/gcc-4.0 -O2 
-I/opt/local/include -I./include -D_GNU_SOURCE=1 
-DTARGET_API_MAC_CARBON -DTARGET_API_MAC_OSX -fvisibility=hidden  
-I/usr/X11R6/include -DXTHREADS -D_THREAD_SAFE -force_cpusubtype_ALL 
-fpascal-strings -c ./src/video/x11/SDL_x11gl.c  -o build/SDL_x11gl.lo
/usr/bin/gcc-4.0 -O2 -I/opt/local/include -I./include -D_GNU_SOURCE=1 
-DTARGET_API_MAC_CARBON -DTARGET_API_MAC_OSX -fvisibility=hidden 
-I/usr/X11R6/include -DXTHREADS -D_THREAD_SAFE -force_cpusubtype_ALL 
-fpascal-strings -c ./src/video/x11/SDL_x11gl.c  -fno-common -DPIC -o 
build/.libs/SDL_x11gl.o

./src/video/x11/SDL_x11gl.c: In function 'X11_GL_GetVisual':
./src/video/x11/SDL_x11gl.c:188: error: 'GLX_NONE_EXT' undeclared 
(first use in this function)
./src/video/x11/SDL_x11gl.c:188: error: (Each undeclared identifier 
is reported only once
./src/video/x11/SDL_x11gl.c:188: error: for each function it appears 
in.)

make: *** [build/SDL_x11gl.lo] Error 1

Error: The following dependencies failed to build: libsdl libtheora 
libvorbis schroedinger liboil x264 yasm

Error: Status 1 encountered during processing.
iboard17:~ travis$


Any help/hints widely appreciated. I'd be willing to show up on 
#MacPorts to work it out if that would help...


--
Travis Griggs
Objologist
My Other Machine runs OSX. But then... so does this one.

You should file this as a ticket against libsdl which is where the 
problem is and attach the full output of


sudo port -d install libsdl

to aid in debugging the problem

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: X11.app

[David Evans]

Frank J. R. Hanstick wrote:

Hello,
Where can I find the MacPorts X11.app that references the ported xorg 
X11 that runs under MacOS 10.4.11?

Frank J. R. Hanstick
tro...@comcast.net 


port xorg-server installs /Applications/MacPorts/X11.app
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: More upgrade

[David Evans]

Frank J. R. Hanstick wrote:

Hello,

Following the:

sudo port selfupdate,
sudo port sync

commands, the:

sudo port upgrade outdated

resulted in successful upgrades of:  gd2, gmp, glpk, python25, pango, 
python26, and textlive_base (mark as fixed for PowerPC G4 
Quicksilver).  The following two modules failed to upgrade:


--->  Building fontforge
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_fontforge/work/fontforge-20090224" 
&& make all " returned error 2

Command output: ( cd Unicode ; make )
make[1]: `../libgunicode.la' is up to date.
( cd gutils ; make )
make[1]: Nothing to be done for `both'.
( cd gdraw ; make )
/bin/sh ../libtool --mode=link /usr/bin/gcc-4.0 -no-undefined -O2 
-I/opt/local/include/freetype2/ -I/opt/local/include/freetype2 
-I/opt/local/include -I/usr/include/libxml2/ -I/sw/include/cairo 
-I/opt/local/include/pango-1.0 -I/opt/local/include 
-I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
-I/opt/local/include/freetype2   -I/opt/local/include/pango-1.0 
-I/opt/local/include/cairo -I/opt/local/include/glib-2.0 
-I/opt/local/lib/glib-2.0/include -I/opt/local/include 
-I/opt/local/include/pixman-1 -I/opt/local/include/freetype2 
-I/opt/local/include/libpng12   -I/opt/local/include -I../inc -I../inc 
-I/usr/pkg/include -I/usr/pkg/include/giflib -Wmissing-prototypes 
-Wunused -Wimplicit -Wreturn-type -Wparentheses -Wformat 
-Wchar-subscripts -I/usr/X11R6/include -DNOTHREADS -DHAVE_CONFIG_H 
-DLIBDIR='"/opt/local/lib"' -L/opt/local/lib -L/usr/local/lib -o 
../libgdraw.la choosericons.lo ctlvalues.lo drawboxborder.lo 
gaskdlg.lo gbuttons.lo gcolor.lo gchardlg.lo gcontainer.lo gdraw.lo 
gdrawbuildchars.lo gdrawerror.lo gdrawtxt.lo gdrawtxtinit.lo 
gfilechooser.lo gfiledlg.lo ggadgets.lo ggroupbox.lo gimageclut.lo 
gimagecvt.lo gimagepsdraw.lo gimagewriteeps.lo gdrawgimage.lo 
gimagexdraw.lo gkeysym.lo glist.lo gmenu.lo gprogress.lo gpsdraw.lo 
gpstxtinit.lo gradio.lo gresource.lo gresourceimage.lo gresedit.lo 
gsavefiledlg.lo gscrollbar.lo gtabset.lo gtextfield.lo gtextinfo.lo 
gwidgets.lo gxdraw.lo gxcdraw.lo ghvbox.lo gmatrixedit.lo gdrawable.lo 
gspacer.lo xkeysyms_unicode.lo \
../libgutils.la ../libgunicode.la -L/opt/local/lib 
-L/usr/local/lib -liconv 
-Wl,/System/Library/Frameworks/CoreServices.framework/CoreServices 
-Wl,/System/Library/Frameworks/Carbon.framework/Carbon  -lpthread \

 -L/usr/X11R6/lib -lSM -lICE -lXi -lX11 -lxkbui   \
-rpath /opt/local/lib -version-info 4:7:0
/usr/bin/gcc-4.0 -dynamiclib  -o ../.libs/libgdraw.4.0.7.dylib 
 .libs/choosericons.o .libs/ctlvalues.o .libs/drawboxborder.o 
.libs/gaskdlg.o .libs/gbuttons.o .libs/gcolor.o .libs/gchardlg.o 
.libs/gcontainer.o .libs/gdraw.o .libs/gdrawbuildchars.o 
.libs/gdrawerror.o .libs/gdrawtxt.o .libs/gdrawtxtinit.o 
.libs/gfilechooser.o .libs/gfiledlg.o .libs/ggadgets.o 
.libs/ggroupbox.o .libs/gimageclut.o .libs/gimagecvt.o 
.libs/gimagepsdraw.o .libs/gimagewriteeps.o .libs/gdrawgimage.o 
.libs/gimagexdraw.o .libs/gkeysym.o .libs/glist.o .libs/gmenu.o 
.libs/gprogress.o .libs/gpsdraw.o .libs/gpstxtinit.o .libs/gradio.o 
.libs/gresource.o .libs/gresourceimage.o .libs/gresedit.o 
.libs/gsavefiledlg.o .libs/gscrollbar.o .libs/gtabset.o 
.libs/gtextfield.o .libs/gtextinfo.o .libs/gwidgets.o .libs/gxdraw.o 
.libs/gxcdraw.o .libs/ghvbox.o .libs/gmatrixedit.o .libs/gdrawable.o 
.libs/gspacer.o .libs/xkeysyms_unicode.o  -L/opt/local/lib 
-L/usr/local/lib ../.libs/libgutils.dylib 
/opt/local/lib/libgunicode.dylib ../.libs/libgunicode.dylib 
/opt/local/lib/libiconv.dylib -lpthread -L/usr/X11R6/lib 
/opt/local/lib/libSM.dylib /opt/local/lib/libICE.dylib 
/opt/local/lib/libXi.dylib /opt/local/lib/libXext.dylib 
/opt/local/lib/libXau.dylib /opt/local/lib/libXdmcp.dylib 
/opt/local/lib/libX11.dylib /opt/local/lib/libxkbui.dylib 
/opt/local/lib/libXt.dylib /opt/local/lib/libxkbfile.dylib 
 -Wl,/System/Library/Frameworks/CoreServices.framework/CoreServices 
-Wl,/System/Library/Frameworks/Carbon.framework/Carbon -install_name 
 /opt/local/lib/libgdraw.4.dylib -compatibility_version 5 
-current_version 5.7 -Wl,-single_module

ld: Undefined symbols:
_utf8_strchr
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link 
edit command failed

make[1]: *** [../libgdraw.la] Error 1
make: *** [libgdraw] Error 2


Frank --

With regard to the fontforge problem see the following:

http://www.nabble.com/Re%3A-Fail-when-compiling-FF-on-Mac-OS-X-10.4-p20409006.html

based on this I would try the same procedure as with evolution-data-server

sudo port deactivate fontforge
sudo port install fontforge

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Error with FFMPEG

[David Evans]

Gus wrote:


Hi I am a newbie with this stuff but I have been trying to install 
ffmpeg via mac ports.
There was a failure building the x264 part which was due to an out 
dated version of Xcode which I have now updated to 3.1.2.


When I attempt the installation again I get the following error

GusLaptop:~ Gus$ sudo port install ffmpeg
--->  Building x264
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_x264/work/x264-snapshot-20090408-2245" 
&& make default " returned error 2
Command output: /usr/bin/gcc-4.0 -shared -o libx264.67.dylib 
common/mc.o common/predict.o common/pixel.o common/macroblock.o 
common/frame.o common/dct.o common/cpu.o common/cabac.o 
common/common.o common/mdate.o common/set.o common/quant.o 
common/vlc.o encoder/analyse.o encoder/me.o encoder/ratecontrol.o 
encoder/set.o encoder/macroblock.o encoder/cabac.o encoder/cavlc.o 
encoder/encoder.o common/x86/mc-c.o common/x86/predict-c.o 
common/x86/cabac-a.o common/x86/dct-a.o common/x86/deblock-a.o 
common/x86/mc-a.o common/x86/mc-a2.o common/x86/pixel-a.o 
common/x86/predict-a.o common/x86/quant-a.o common/x86/sad-a.o 
common/x86/cpu-a.o common/x86/dct-32.o common/x86/pixel-32.o 
-dynamiclib -Wl,-single_module -Wl,-read_only_relocs,suppress 
-install_name /opt/local/lib/libx264.67.dylib -L/opt/local/lib -lm 
-lmx -lpthread -s

ld64: warning: option -s is obsolete and being ignored
ld: absolute addressing (perhaps -mdynamic-no-pic) used in 
_x264_cabac_encode_decision_asm from common/x86/cabac-a.o not allowed 
in slidable image

collect2: ld returned 1 exit status
make: *** [libx264.67.dylib] Error 1

Error: The following dependencies failed to build: x264 zlib
Error: Status 1 encountered during processing.
GusLaptop:~ Gus$

I have subsequently tried to obtain zlib which appears have been OK
GusLaptop:~ Gus$ sudo port install zlib
Password:
--->  Fetching zlib
--->  Attempting to fetch zlib-1.2.3.tar.bz2 from 
http://internap.dl.sourceforge.net/libpng

--->  Verifying checksum(s) for zlib
--->  Extracting zlib
--->  Applying patches to zlib
--->  Configuring zlib
--->  Building zlib
--->  Staging zlib into destroot
--->  Installing zlib @1.2.3_2
--->  Activating zlib @1.2.3_2
--->  Cleaning zlib

subsequently reran the ffmpeg install and ..
GusLaptop:~ Gus$ sudo port install ffmpeg
--->  Building x264
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_x264/work/x264-snapshot-20090408-2245" 
&& make default " returned error 2
Command output: /usr/bin/gcc-4.0 -shared -o libx264.67.dylib 
common/mc.o common/predict.o common/pixel.o common/macroblock.o 
common/frame.o common/dct.o common/cpu.o common/cabac.o 
common/common.o common/mdate.o common/set.o common/quant.o 
common/vlc.o encoder/analyse.o encoder/me.o encoder/ratecontrol.o 
encoder/set.o encoder/macroblock.o encoder/cabac.o encoder/cavlc.o 
encoder/encoder.o common/x86/mc-c.o common/x86/predict-c.o 
common/x86/cabac-a.o common/x86/dct-a.o common/x86/deblock-a.o 
common/x86/mc-a.o common/x86/mc-a2.o common/x86/pixel-a.o 
common/x86/predict-a.o common/x86/quant-a.o common/x86/sad-a.o 
common/x86/cpu-a.o common/x86/dct-32.o common/x86/pixel-32.o 
-dynamiclib -Wl,-single_module -Wl,-read_only_relocs,suppress 
-install_name /opt/local/lib/libx264.67.dylib -L/opt/local/lib -lm 
-lmx -lpthread -s

ld64: warning: option -s is obsolete and being ignored
ld: absolute addressing (perhaps -mdynamic-no-pic) used in 
_x264_cabac_encode_decision_asm from common/x86/cabac-a.o not allowed 
in slidable image

collect2: ld returned 1 exit status
make: *** [libx264.67.dylib] Error 1

Error: The following dependencies failed to build: x264
Error: Status 1 encountered during processing.


What do i need to do to get this back on track ?
Muchas Graias Todos !

Angus Denton
Asparagus Arts
Web and Database constructions
You need to upgrade XCode to version 3.1 or better.  This is a know 
error in version 3.0.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Error with FFMPEG

[David Evans]

You need to upgrade XCode to version 3.1 or better.  This is a know 
error in version 3.0.


In that case, the x264 port should prevent installation on Leopard 
with Xcode versions earlier than 3.1. Some code for doing this which 
has been used in many ports already can be copied to the x264 portfile 
from e.g. the graphviz portfile (though you'd adjust the required 
Xcode version number to 3.1).


The code you mention was added in r49663 so I'm not sure what happened 
here.  Looks like it should work.


Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: More upgrade

[David Evans]

Ryan Schmidt wrote:


On May 5, 2009, at 22:46, Frank J. R. Hanstick wrote:

Fontforge installed with the deactivate.  I while back, I raised 
the issue of deactivating and/or uninstalling ports before 
upgrading.  Since then, I have run into four ports that have required 
the deactivation before hand.  The number seems to be increasing.  
Maybe some things need to be rethought.


By all means. If you have specific ideas for what could be changed in 
base to fix this, please share them on macports-dev.


I posted an idea and some thoughts and questions about this topic 
there a month ago to which nobody responded:


http://lists.macosforge.org/pipermail/macports-dev/2009-April/008148.html

I am still interested in feedback on that message.

From what I have seen, while this general type of problem has popped up 
in several ports, the specific solution is often port specific and depends
on what the upstream developer thought was "standard" usage.  In open 
source development, this is often a statement of personal preferences.


For example, some might think it is "standard" to uninstall a port 
before attempting to install a new version.


So I think the idea that a single global change in MacPorts would do 
away with this sort of problem entirely without causing problems
elsewhere is a bit optimistic.  While these problems look similar, the 
specific fix often involves evaluation of the specific occurance.  And

standard usage is in the eye of the beholder -- developer actually.

A simple example that I ran across today is gimp-gap-devel.   In this 
port, if ffmpeg-devel is installed, the build of an internal copy of ffmpeg
fails because the port lists (accidentally) a MacPorts include path 
before the internal include path in its build.  Thus the MacPorts 
(incompatible)
include files are used and build fails due to conflicting symbol 
definitions. The MacPorts path came from the pkgconfig defined include 
path for glib which was ordered first in the include path list.  The 
solution was to move the local include paths to the front of the list.   
See r50862, r50863.


evolution-data-server is a much harder problem as it uses a very 
complicated build system so its much harder to track down exactly
what behavior is causing the problem and therefore where the correct 
change should be made.


At any rate, these are problems that need to be tracked down and fixed 
one by one.  And the magnitude of the task is not too great if we are

only talking about 4 ports out of almost 6000.

Dave




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: seahorse-2.24.1 fails while installing gnome [was Install Fail: Gnome]

[David Evans]

Jalaluddin Morris wrote:

On OS 10.5.7

with hardware

Model Name:Mac Pro
 Model Identifier:MacPro4,1
 Processor Name:Quad-Core Intel Xeon
 Processor Speed:2.66 GHz
 Number Of Processors:1
 Total Number Of Cores:4
 L2 Cache (per core):256 KB
 L3 Cache:8 MB
 Memory:3 GB

port install gnome

fails as per attachment.

Regards,

Jalaluddin



Jalaluddin --

Your attempting to build an old version of seahorse (2.24.1).  Seahorse 
was upgraded to 2.26.2 in r51200 yesterday along with a number of other 
GNOME ports.  Please update your ports tree to the latest, upgrade any 
outdated ports and then try again.



sudo port selfupdate
port outdated
sudo port upgrade outdated
sudo port clean gnome seahorse
sudo port install gnome


or your might start with something smaller like

gnome-platform-suite  (base libraries and tools for creating GNOME apps)
gnome-desktop-suite (what's necessary for a basic GNOME desktop)

Also see https://trac.macports.org/wiki/GNOME for information on how to 
configure your computer to run GNOME. 




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: netcdf4

[David Evans]

Christopher Barker wrote:

Bryan Blackburn wrote:

On Thu, May 21, 2009 at 05:39:08PM -0700, Christopher Barker said:


so it looks like netcdf4 support has been commented out. Anyone know 
why?


Probably related to ticket #16262:




arrgg! I just spent a couple hours learning about how to write port 
files and hacked the netcdf portfile, then found that 7 hours ago 
someone had already fixed it!


Oh well, at least I learned something. However:


I'd also love to get '--enable-dap if possible

It also looks like the recent release is 4.0.1, it would be nice to 
get  that updated.


The current port file does support netcdf4, which was the big one, but 
it's still using version 4.0, rather than 4.0.1, and it isn't using 
--enable-dap


How might those changed get in? I've tested them, and they work for 
me. As there is no maintainer, and the ticket has been closed, I'm not 
sure how to proceed.


--enable-dap required libcurl, which got pulled in from:

/usr/lib/libcurl.3.dylib

Should it use a macport libcurl instead? If so, how do I get it to do 
that?


By the way, I used python's hashlib module to generate the sha1 hash 
-- is there a simple mac-ports way to do that?


I've enclosed my version of the portfile (re-named to netcdf-4 to not 
stomp on netcdf) in case anyone wants a look.


-Chris


Chris --

The standard approach is to submit your changes in the form of a patch
against the current Portfile as an attachment to a new ticket requesting
the update.  A committer should then help you.

To use the MacPorts  libcurl (MacPorts libraries should be used when at
all possible to maintain a known environment) add

port:curl

to the depends_lib statement.

if you run

sudo port -d checksum

on your Portfile,  if the checksums are not correct, port will give you
a debug message with what it has calculated for the hashs
for this file  in terms of a checksum statement.  Of course, you need to
make sure that you really have an official copy of
the distribution file if you are going to assign checksums to it.

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gnome missing file

[David Evans]

William Davis wrote:

when I tried to upgrade the gnome metaport got this error:
DEBUG: Executing org.macports.destroot (gnome)
Error: Target org.macports.destroot returned: error copying 
"/opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/gnome/files/README.gnome.txt.in": 
no such file or directory
Warning: the following items did not execute (for gnome): 
org.macports.destroot

DEBUG: invalid command name "::ui_init"
while executing
"::ui_init $priority $prefix $channels $message"
("uplevel" body line 2)
invoked from within
"uplevel 1 $body"
Error: Unable to upgrade port: 1


Fixed in r51602.  Thanks.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: ardour2 build fails

[David Evans]

William Davis wrote:

install of ardour2 failed with this mesg:

s/ardour/rb_effect.cc", "libs/ardour/audio_unit.cc"])
po_builder(["libs/ardour/el_GR.po"], ["libs/ardour/po/el_GR.po", 
"libs/ardour/libardour2.pot"])

Updating libs/ardour/el_GR.po
... 
done.

msgmerge: `libs/ardour/el_GR.po': No such file or directory
scons: *** [libs/ardour/el_GR.po] Error 1
scons: building terminated because of errors.

Warning: the following items did not execute (for ardour2): 
org.macports.activate org.macports.destroot org.macports.install

Error: Status 1 encountered during processing.
macintosh:~ frstan$


I can't reproduce this error.   Look for this file relative to the ports
${worksrcpath} and if it seems to be missing
then I suggest you clean the port entirely and try again

sudo port clean --all ardour2

If that doesn't work please report as a ticket rather than to the user
list, build with -d option and attach the full output
as an attachment to the ticket so there is some information available to
try and diagnose the problem.

Thanks

Dave

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: loss of pdflatex

[David Evans]

 On 9/17/10 2:12 PM, Emden R. Gansner wrote:
>  I recently updated the macports on my macbook. I now find that latex,
> pdflatex and many tex packages have disappeared.
> port reports that the various texlive packages are installed. I
> thought these were the ones that supplied /opt/local/bin/pdflatex.
> I have tried reinstalling some of these to no effect. How can I get
> pdflatex back? More generally, is there some way to find out
> which macport package supplies some program in /opt/local/bin?
>
> Thanks.
>
> Emden
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
% port provides /opt/local/bin/pdflatex
/opt/local/bin/pdflatex is provided by: texlive-latex

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Insight still failed to build.

[David Evans]

 On 9/19/10 6:38 PM, Frank J. R. Hanstick wrote:
> Hello,
> Sorry, it was three in the morning and I was a little tired.  I
> have not tried the Inkscape yet, just the inkscape_devel.  Maybe,
> should uninstall the devel and install the inkscape.  I was not aware
> that the latter outpaced the former.

Currently, inkscape-devel represents a pre-release version of inkscape
0.48, the final version of
which is the inkscape port.   Due to changes in how the inkscape
development repository is
maintained, it has been difficult to provide a "trunk" version in
inkscape-devel, sorry.

At any rate, the inkscape is to be preferred at this point.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: latex packages too old

[David Evans]

 On 9/26/10 9:03 AM, Peng Yu wrote:
> On Sat, Sep 25, 2010 at 7:09 PM, Arno Hautala  wrote:
>> On Sat, Sep 25, 2010 at 19:43, Peng Yu  wrote:
>>> Hi,
>>>
>>> It seems that the latex packages is already 3 years old. I tried to
>>> 'sudo port upgrade textlive'. But it doesn't upgrade. Is the port
>>> outdated or there is something wrong when I update the package?
>> The current TexLive port is "texlive @2009, Revision 3".
>>
>> Have you run "port selfupdate" lately?
> I just run 'sudo port selfupdate' then 'sudo port upgrade outdated'.
> But I see the following error. How to 'deactivate this port'?
>
> --->  Computing dependencies for texlive-bin
> --->  Dependencies to be installed: poppler
> --->  Activating poppler @0.14.3_0
> Error: Target org.macports.activate returned: Image error:
> /opt/local/bin/pdffonts is being used by the active xpdf port.  Please
> deactivate this port first, or use 'port -f activate poppler' to force
> the activation.
> Log for poppler is at:
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_poppler/main.log
> Error: The following dependencies failed to build: poppler
> Error: Problem while installing texlive-bin
> To report a bug, see 
>
>
I think you can get poppler and xpdf to co-exist by doing this:

sudo port selfupdate
sudo port install xpdf +with_poppler
sudo port upgrade outdated


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: deluge 1.3.0 checksum error

[David Evans]

 On 9/30/10 9:23 AM, Bayard Bell wrote:
> I've been trying to build deluge 1.3.0 but am getting failures for all
> three checksums. Here's what I see in the logs:
>
> :msg:fetch --->  Attempting to fetch deluge-1.3.0.tar.bz2
> from http://download.deluge-torrent.org/source/
> :msg:fetch --->  Verifying checksum(s) for deluge
> :debug:checksum checksum phase started at Thu Sep 30 15:48:32 BST 2010
> :debug:checksum Executing org.macports.checksum (deluge)
> :info:checksum --->  Checksumming deluge-1.3.0.tar.bz2
> :error:checksum Checksum (md5) mismatch for deluge-1.3.0.tar.bz2
> :info:checksum Portfile checksum: deluge-1.3.0.tar.bz2 md5
> d3cdb501983fcf793ee368b5a8e429c0
> :info:checksum Distfile checksum: deluge-1.3.0.tar.bz2 md5
> 5fca34e2e31753a8ba0ccb942f0e993e
> :error:checksum Checksum (sha1) mismatch for deluge-1.3.0.tar.bz2
> :info:checksum Portfile checksum: deluge-1.3.0.tar.bz2 sha1
> 75c1030bbd32c9eebea53c021e19035ebe343c14
> :info:checksum Distfile checksum: deluge-1.3.0.tar.bz2 sha1
> 8acefff67bd82e38314b43887bd5f10da9a12052
> :error:checksum Checksum (rmd160) mismatch for deluge-1.3.0.tar.bz2
> :info:checksum Portfile checksum: deluge-1.3.0.tar.bz2 rmd160
> 28d2162d67684f1969ed5a8882dea358bb022bd2
> :info:checksum Distfile checksum: deluge-1.3.0.tar.bz2 rmd160
> dca83b23603a140d4abbb4de7672bf4259018167
> :info:checksum The correct checksum line may be:
> :info:checksum checksums   md5
> 5fca34e2e31753a8ba0ccb942f0e993e \
> sha18acefff67bd82e38314b43887bd5f10da9a12052 \
> rmd160  dca83b23603a140d4abbb4de7672bf4259018167
> :error:checksum Target org.macports.checksum returned: Unable to
> verify file checksums
> :debug:checksum Backtrace: Unable to verify file checksums
> while executing
> "$procedure $targetname"
>
> I've checked the release notes
> (http://dev.deluge-torrent.org/wiki/ReleaseNotes/1.3.0), and it
> appears that either someone has completely hijacked the distribution
> infrastructure for deluge and replaced the checksum values or that
> macports has got it wrong. I'm not sure why macports would have this
> wrong, but I did notice the following further details:
>
> 1) these aren't the checksums for the earlier 1.3.0 release candidates
> 2) the changeset for 1.3.0 that provides these checksums
> (https://trac.macports.org/changeset/71478) is dated September 14,
> whereas the distribution I'm trying to download dates the bz2 source
> September 18, which is the same date as given on the release notes,
> suggesting that macports pushed 1.3.0 pre-release and thus ended up
> with the wrong checksums
> 3) trying to find copies of 1.3.0 through alternate distribution
> channels, I don't find anyone else's bz2 distro to compare, but I do
> notice that numerous sites announce the release on the 14th and
> provide various other types of distribution as of that date, noting
> that release notes are not yet available, suggesting that something
> changed between announcement and initial availability and the release
> for which notes are available, which may be as trivial a difference as
> the addition of release notes
> 4) unfortunately there's neither SSL-verifiable release notes
> (deluge-torrent.org  is a virtual domain
> running on the OSU Open Source Lab, where the certificate is expired
> and doesn't support validation of the virtually hosted domains) nor
> signed checksums (I've posted to the deluge forums about this problem
> in attributing the checksums and verifying their integrity)
>
> All the same, I tend to think that this is not a case of hijacking a
> distribution channel to propagate trojaned software. I'm going to go
> ahead and build this via a local Portfile override, but I'd appreciate
> another pair of eyes on this, just in case I'm wrong.
>
> Cheers,
> Bayard
>
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
It appears that the deluge-torrent.org prematurely published a copy of
1.3.0 on their site and later retracted
it, substituting a different file with the same version number. 
Unfortunately, the deluge port was
updated to 1.3.0 while the old file still existed. 

I agree that the new version is probably legitimate but there is
difficulty in verifying the checksums as
you have stated.

In addition, the earlier version of the file is cached on the macports
own mirrors so the port will fetch
a different version of the file depending on which site it thinks is
closer.  In my case, I always get
it from distfiles.macports.org, which is geographically closer to me
than the OSU site. So the checksums
pass.

So a question for the more knowledgable is how to purge the old file
from the macports mirrors
and/or under which circumstances it will be automatically updated.

Dave



___
macports-users mailing list
macpo

Re: deluge 1.3.0 checksum error

[David Evans]

 On 9/30/10 11:15 AM, Joshua Root wrote:
> Going back to the OP's concerns: since the old version is available on
> our server, you can just diff its contents against the new one's to see
> what changed.
>
> - Josh
Changes are limited to minor changes to setup.py and a date update to
the ChangeLog
Nothing that looks too nefarious.

Diff follows.

Will update port per Ryan's suggestion

Dave

diff -ur deluge-mp/deluge-1.3.0/ChangeLog deluge-dt/deluge-1.3.0/ChangeLog
--- deluge-mp/deluge-1.3.0/ChangeLog2010-09-13 18:22:08.0 -0700
+++ deluge-dt/deluge-1.3.0/ChangeLog2010-09-18 11:31:31.0 -0700
@@ -1,4 +1,4 @@
-=== Deluge 1.3.0 (13 September 2010) ===
+=== Deluge 1.3.0 (18 September 2010) ===
* Fix issue where the save_timer is cancelled when it's not active
* Fix unhandled exception when adding a torrent to the session
* Moved xdg import so it is not called on Windows, where it is
unused. fixes #1343
diff -ur deluge-mp/deluge-1.3.0/setup.py deluge-dt/deluge-1.3.0/setup.py
--- deluge-mp/deluge-1.3.0/setup.py 2010-09-13 19:23:05.0 -0700
+++ deluge-dt/deluge-1.3.0/setup.py 2010-09-18 11:31:31.0 -0700
@@ -35,7 +35,6 @@
 from distutils.command.build import build as _build
 from distutils.command.build_ext import build_ext as _build_ext
 from distutils.command.clean import clean as _clean
-from setuptools.command.install import install as _install
 try:
 from sphinx.setup_command import BuildDoc
 except ImportError:
@@ -387,14 +386,6 @@
 self.run_command(cmd_name)
 _clean.run(self)
 
-class install(_install):
-def run(self):
-for cmd_name in self.get_sub_commands():
-self.run_command(cmd_name)
-_install.run(self)
-if not self.root:
-self.do_egg_install()
-
 cmdclass = {
 'build': build,
 'build_trans': build_trans,
@@ -404,7 +395,6 @@
 'build_ext_debug': build_ext_debug,
 'clean_plugins': clean_plugins,
 'clean': clean,
-'install': install
 }
 
 # Data files to be installed to the system
@@ -452,14 +442,11 @@
 data_files = _data_files,
 ext_package = "deluge",
 ext_modules = _ext_modules,
-include_package_data = True,
 package_data = {"deluge": ["ui/gtkui/glade/*.glade",
 "data/pixmaps/*.png",
 "data/pixmaps/*.svg",
 "data/pixmaps/*.ico",
 "data/pixmaps/flags/*.png",
-"data/revision",
-"data/GeoIP.dat",
 "plugins/*.egg",
 "i18n/*.pot",
 "i18n/*/LC_MESSAGES/*.mo",
@@ -470,8 +457,16 @@
 "ui/web/images/*.gif",
 "ui/web/images/*.png",
 "ui/web/js/*.js",
+"ui/web/js/*/*.js",
+"ui/web/js/*/.order",
+"ui/web/js/*/*/*.js",
+"ui/web/js/*/*/.order",
 "ui/web/render/*.html",
-"ui/web/themes/*/*/*/*"
+"ui/web/themes/css/*.css",
+"ui/web/themes/images/*/*.gif",
+"ui/web/themes/images/*/*.png",
+"ui/web/themes/images/*/*/*.gif",
+"ui/web/themes/images/*/*/*.png"
 ]},
 packages = find_packages(exclude=["plugins", "docs", "tests"]),
 entry_points = """

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: deluge 1.3.0 checksum error

[David Evans]

 On 9/30/10 9:23 AM, Bayard Bell wrote:
> I've been trying to build deluge 1.3.0 but am getting failures for all
> three checksums. Here's what I see in the logs:
deluge updated to 1.3.0_1 in r72027.

Thanks for the report, Bayard.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gedit

[David Evans]

 On 10/6/10 1:59 PM, Ryan Schmidt wrote:
>
> I don't know what to say about the theme icon message.
This is also a warning message only and can be safely disregarded.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gnome-desktop-suite build fail

[David Evans]

 On 10/19/10 6:53 AM, Bob Katz wrote:
> Hi I have included the output for the reason gnome-desktop-suite failed to 
> build. If anyone can point me in the right direction that would be great ! 
>
> Thanks
> Bob
>
>
> Couldn't find include 'Gst-0.10.gir' (search path: 
> ['/opt/local/share/gir-1.0', '/opt/local/share/gir-1.0', 
> '/opt/local/share/gir-1.0', '/usr/share/gir-1.0', '/opt/local/share/gir-1.0'])
> g-ir-scanner: warning: Option --strip-prefix has been deprecated;
> see --identifier-prefix and --symbol-prefix.
> make[4]: *** [GstTag-0.10.gir] Error 1
> make[3]: *** [tag] Error 2
> make[3]: *** Waiting for unfinished jobs
> Couldn't find include 'Gst-0.10.gir' (search path: 
> ['/opt/local/share/gir-1.0', '/opt/local/share/gir-1.0', 
> '/usr/share/gir-1.0', '/opt/local/share/gir-1.0'])
> g-ir-scanner: warning: Option --strip-prefix has been deprecated;
> see --identifier-prefix and --symbol-prefix.
> make[5]: *** [GstInterfaces-0.10.gir] Error 1
> make[4]: *** [all] Error 2
> make[3]: *** [interfaces] Error 2
> make[2]: *** [all-recursive] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
> shell command " cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gst-plugins-base/work/gst-plugins-base-0.10.30"
>  && /usr/bin/make -j2 all " returned error 2
> Error: Target org.macports.build returned: shell command failed
> DEBUG: Backtrace: shell command failed
> while executing
> "command_exec build"
> (procedure "portbuild::build_main" line 8)
> invoked from within
> "$procedure $targetname"
> Warning: the following items did not execute (for gst-plugins-base): 
> org.macports.activate org.macports.build org.macports.destroot 
> org.macports.install
> Log for gst-plugins-base is at: 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gst-plugins-base/main.log
> Error: The following dependencies failed to build: empathy telepathy-farsight 
> farsight2 libnice gst-plugins-base telepathy-glib vala telepathy-haze pidgin 
> libao telepathy-mission-control webkit-gtk icu eog exempi gnome-desktop 
> gnome-themes gnome-icon-theme hicolor-icon-theme icon-naming-utils 
> p5-xml-simple p5-xml-namespacesupport p5-xml-sax p5-xml-sax-expat 
> gtk-engines2 startup-notification xorg-xcb-util epiphany evince libspectre 
> nautilus t1lib file-roller gcalctool gconf-editor gdm gnome-panel libwnck 
> xorg-libXres xorg-resourceproto policykit-gnome gnome-session upower 
> gnome-settings-daemon libgnomekbd libxklavier xkbcomp xorg-libxkbfile xmodmap 
> gedit py26-pygtksourceview gtksourceview2 gnome-applets gucharmap 
> gnome-backgrounds gnome-control-center metacity xorg-libXScrnSaver 
> xorg-scrnsaverproto gnome-games guile gnome-mag gnome-media 
> gnome-python-desktop gtksourceview libgnomeprint libgnomecups libgnomeprintui 
> totem-pl-parser gmime gnome-speech gnome-terminal vte gnome-u
 se
>  r-docs gnome-utils gst-plugins-good flac libcaca libcdio libcddb libdv 
> libshout2 taglib wavpack gvfs libarchive libgail-gnome libgtkhtml3 liboobs 
> system-tools-backends p5-net-dbus p5-xml-twig seahorse gpgme gnupg pth 
> openssh xauth seahorse-plugins totem gst-ffmpeg gst-plugins-bad jack 
> libsamplerate libsndfile libdca libmms libmodplug libmpcdec neon soundtouch 
> gst-plugins-ugly a52dec libdvdread libdvdcss libid3tag libmad libmpeg2 
> xorg-libXv xorg-videoproto twolame libgdata xorg-libXxf86vm 
> xorg-xf86vidmodeproto vino zenity
> Error: Status 1 encountered during processing.
> To report a bug, see 
> bash-3.2$ 
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
Bob --

Port gst-plugins-base is failing during the generation of GObject
introspection data because
you have gobject-introspection installed and ports that gst-plugins-base
depends on have
not been configured to generate introspection data. 

GObject introspect disabled for now for gst-plugins-base in r72514.

You should be able to re-sync your ports tree and proceed as follows

sudo port selfupdate
sudo port clean gst-plugins-base
sudo port install gnome-desktop-suite

Dave



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Please Help - can't install ufraw

[David Evans]

 On 10/19/10 8:00 AM, Ryan Schmidt wrote:
> On Oct 19, 2010, at 09:56, Mo Issa wrote:
>
>> I’m trying to install ufraw on Mac OS X Leopard to use with ResourceSpace 
>> and every time I try to install the package using MacPorts, it fails and 
>> gives me this error message:
>>
>> sudo port install ufraw
>> Password:
>> --->  Computing dependencies for ufrawError: Unable to execute port: Can't 
>> install poppler because conflicting ports are installed: xpdf
> You are trying to install ufraw, which eventually depends on poppler, but you 
> already have xpdf installed.
> You cannot have xpdf and poppler installed and active at the same time.
> Deactivate xpdf if you want to install ufraw (and therefore poppler)
>
> sudo port deactivate xpdf
>
>
>> I researched this quite a bit and can’t find a solution for it.
> The ports were only marked as conflicting a few days ago (though the conflict 
> itself has existed forever).
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
Note that poppler and xpdf can co-exist if poppler is installed first
and then xpdf is installed
with the +with_poppler variant.

sudo port deactivate xpdf
sudo port install poppler
sudo port install xpdf +with_poppler


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Please Help - can't install ufraw

[David Evans]

 On 10/19/10 8:31 AM, Ryan Schmidt wrote:
> On Oct 19, 2010, at 10:24, David Evans wrote:
>> On 10/19/10 8:14 AM, Ryan Schmidt wrote:
>>> Why don't we delete that variant and make the xpdf port always do that?
>>>
>> I agree but there is a political history behind this.
>>
>> Xpdf was first and poppler is an off-shoot of the original xpdf code written
>> as a library to allow other projects to use it.
>>
>> The two have diverged some-what and it has only been relatively recently
>> that
>> xpdf  was modified to allow linking to poppler rather than use its own code.
>>
>> Xpdf web site still doesn't mention poppler although it is the variant
>> that is
>> currently being maintained (xpdf hasn't had a change in a year and then only
>> minor).
>>
>> But the solution that you propose would be the one that works.
>>
>> Perhaps just making the +with_poppler variant a default variant would
>> fix the
>> problem and allow xpdf purists to use xpdf without poppler (if they
>> really never
>> want to use poppler).
> If the variant is kept, I would want it renamed to just "+poppler" (we do not 
> name variants with "with_" or "without_" prefixes in MacPorts).
>
> Also if the variant is kept my addition of the conflicts keywords needs to be 
> fixed to only apply the conflict if it's actually relevant.
>
>
Well, saying it that way sounds a bit too contrived to me so I would
vote to just make the poppler dependency
the default behavior without any variant.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Please Help - can't install ufraw

[David Evans]

 On 10/19/10 8:48 AM, David Evans wrote:
>  On 10/19/10 8:31 AM, Ryan Schmidt wrote:
>> On Oct 19, 2010, at 10:24, David Evans wrote:
>>> On 10/19/10 8:14 AM, Ryan Schmidt wrote:
>>>> Why don't we delete that variant and make the xpdf port always do that?
>>>>
>>> I agree but there is a political history behind this.
>>>
>>> Xpdf was first and poppler is an off-shoot of the original xpdf code written
>>> as a library to allow other projects to use it.
>>>
>>> The two have diverged some-what and it has only been relatively recently
>>> that
>>> xpdf  was modified to allow linking to poppler rather than use its own code.
>>>
>>> Xpdf web site still doesn't mention poppler although it is the variant
>>> that is
>>> currently being maintained (xpdf hasn't had a change in a year and then only
>>> minor).
>>>
>>> But the solution that you propose would be the one that works.
>>>
>>> Perhaps just making the +with_poppler variant a default variant would
>>> fix the
>>> problem and allow xpdf purists to use xpdf without poppler (if they
>>> really never
>>> want to use poppler).
>> If the variant is kept, I would want it renamed to just "+poppler" (we do 
>> not name variants with "with_" or "without_" prefixes in MacPorts).
>>
>> Also if the variant is kept my addition of the conflicts keywords needs to 
>> be fixed to only apply the conflict if it's actually relevant.
>>
>>
> Well, saying it that way sounds a bit too contrived to me so I would
> vote to just make the poppler dependency
> the default behavior without any variant.
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
Conflict between xpdf and poppler resolved in r72519, r72520 as
suggested by Ryan. Conflicts statements
removed.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Please Help - can't install ufraw

[David Evans]

 On 10/19/10 10:05 AM, Eric Hall wrote:
> On Tue, Oct 19, 2010 at 09:55:37AM -0700, David Evans wrote:
>>  On 10/19/10 8:48 AM, David Evans wrote:
>>>  On 10/19/10 8:31 AM, Ryan Schmidt wrote:
>>>> On Oct 19, 2010, at 10:24, David Evans wrote:
>>>>> On 10/19/10 8:14 AM, Ryan Schmidt wrote:
>>>>>> Why don't we delete that variant and make the xpdf port always do that?
>>>>>>
>>>>> I agree but there is a political history behind this.
>>>>>
>>>>> Xpdf was first and poppler is an off-shoot of the original xpdf code 
>>>>> written
>>>>> as a library to allow other projects to use it.
>>>>>
>>>>> The two have diverged some-what and it has only been relatively recently
>>>>> that
>>>>> xpdf  was modified to allow linking to poppler rather than use its own 
>>>>> code.
>>>>>
>>>>> Xpdf web site still doesn't mention poppler although it is the variant
>>>>> that is
>>>>> currently being maintained (xpdf hasn't had a change in a year and then 
>>>>> only
>>>>> minor).
>>>>>
>>>>> But the solution that you propose would be the one that works.
>>>>>
>>>>> Perhaps just making the +with_poppler variant a default variant would
>>>>> fix the
>>>>> problem and allow xpdf purists to use xpdf without poppler (if they
>>>>> really never
>>>>> want to use poppler).
>>>> If the variant is kept, I would want it renamed to just "+poppler" (we do 
>>>> not name variants with "with_" or "without_" prefixes in MacPorts).
>>>>
>>>> Also if the variant is kept my addition of the conflicts keywords needs to 
>>>> be fixed to only apply the conflict if it's actually relevant.
>>>>
>>>>
>>> Well, saying it that way sounds a bit too contrived to me so I would
>>> vote to just make the poppler dependency
>>> the default behavior without any variant.
>>>
>>> ___
>>> macports-users mailing list
>>> macports-users@lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>>
>> Conflict between xpdf and poppler resolved in r72519, r72520 as
>> suggested by Ryan. Conflicts statements
>> removed.
>>
> [snip]
>
>   As I noted in the reopened ticket:
>
>   Did anyone do any testing to verify that the poppler
> command line utilities perform in the same way the xpdf command
> line utilities do? If not, (and there are differences) then I agree
> that this is a "dangerous" sort of change - people who know what
> the xpdf package contains (not just the xpdf X11 pdf viewer) won't
> get what they are expecting.
>   Making an xpdf-tools and poppler-tools set of ports (or similar)
> and making them not conflict seems like the best solution. I'd suggest
> that the poppler-tools alter the binary and man page names to reflect
> their origin (as they came later than the xpdf tools).
>
>
>
>   If anyone has a bit of time to make the xpdf-tools (or xpdf-utils,
> take your pick) and poppler-tools ports, that would be a great help.
>
>
>
>   -eric
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
Since you seem to have a better idea of the issues involved here, I
would suggest that you
take a crack at creating these Portfiles yourself and submit them via
trac for review.  MacPorts
is a self-serve lunch counter and we can always use help from
knowledgeable individuals.

The current fix removes the forced conflict between the two ports which
just makes them
both unusable for anyone.  This is an improvement but there is always
room for more.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: gnome desktop suite fail part 2

[David Evans]

 On 10/19/10 2:45 PM, Bob Katz wrote:
> Hi
>
>  The error that I reported earlier devans reply did the trick and I
> thank him for that. However I have a new error that stopped the show.
> If anybody can offer any help on the below output error. Please send.
>
>
> Thanks
> Bob
>
>
>
>
> checking for zenity... no
> configure: error: zenity not found in your path - needed for dialogs
> shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_metacity/work/metacity-2.30.3"
> && ./configure --prefix=/opt/local --mandir=/opt/local/share/man
> --x-includes=/opt/local/include --x-libraries=/opt/local/lib
> --disable-scrollkeeper --disable-schemas-install " returned error 1
> Error: Target org.macports.configure returned: configure failure:
> shell command failed
> DEBUG: Backtrace: configure failure: shell command failed
> while executing
> "$procedure $targetname"
> Warning: the following items did not execute (for metacity):
> org.macports.activate org.macports.configure org.macports.build
> org.macports.destroot org.macports.install
> Log for metacity is at:
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_metacity/main.log
> Error: The following dependencies failed to build:
> gnome-control-center metacity xorg-libXScrnSaver xorg-scrnsaverproto
> gnome-games guile gnome-mag gnome-media gnome-python-desktop
> gtksourceview libgnomeprint libgnomecups libgnomeprintui
> totem-pl-parser gmime gnome-speech gnome-terminal vte gnome-user-docs
> gnome-utils gst-plugins-good flac libcaca libcdio libcddb libdv
> libshout2 taglib wavpack gvfs libarchive libgail-gnome libgtkhtml3
> liboobs system-tools-backends p5-net-dbus p5-xml-twig seahorse gpgme
> gnupg pth openssh xauth seahorse-plugins totem gst-ffmpeg
> gst-plugins-bad jack libsamplerate libsndfile libdca libmms libmodplug
> libmpcdec neon soundtouch gst-plugins-ugly a52dec libdvdread libdvdcss
> libid3tag libmad libmpeg2 xorg-libXv xorg-videoproto twolame libgdata
> xorg-libXxf86vm xorg-xf86vidmodeproto vino zenity
> Error: Status 1 encountered during processing.
> To report a bug, see 
> bash-3.2$ 
>
>
>
>  
>
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Thanks for the report and your patience.  Metacity is, indeed missing a
dependency on zenity.

Fixed in r72537.

sudo port selfupdate

to pick up the fix (as soon as the rsync server updates itself ~1 hr)

then try again.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Error installing policykit-gnome due to gconf schema issue

[David Evans]

On 10/22/10 10:22 AM, Drake, Richard R wrote:
> Hello,
>
> I've been trying to install policykit-gnome from scratch for a while now and
> for the last few weeks, get an error.  I wonder if someone knows a fix. Here
> is what I do:
>
>  % sudo port -f uninstall installed
>  % sudo port selfupdate
>  % sudo port install policykit-gnome
>
> It gets all through the dependencies but fails activating policykit-gnome.
> Here is the error:
>
> ...
> --->  Building gconf
> --->  Staging gconf into destroot
> --->  Installing gconf @2.28.1_0
> --->  Activating gconf @2.28.1_0
> --->  Cleaning gconf
> --->  Installing policykit-gnome @0.96_0
> --->  Activating policykit-gnome @0.96_0
> Error: Target org.macports.activate returned: shell command failed
> Log for policykit-gnome is at:
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.
> org_release_ports_gnome_policykit-gnome/main.log
> Error: Status 1 encountered during processing.
> To report a bug, see 
>
>
> The end of the log file shows
>
> :debug:activate activating directory:
> /opt/local/share/locale/zh_TW/LC_MESSAGES
> :debug:activate activating file:
> /opt/local/share/locale/zh_TW/LC_MESSAGES/polkit-gnome-1.mo
> :debug:activate Executing
> proc-post-org.macports.activate-activate-0:info:activate I/O warning :
> failed to load external entity
> "/opt/local/etc/gconf/schemas/*.schemas":info:activate Failed to open
> `/opt/local/etc/gconf/schemas/*.schemas': No such file or directory
> :info:activate shell command "export GCONF_CONFIG_SOURCE=`gconftool-2
> --get-default-source` &&  gconftool-2 --makefile-install-rule
> /opt/local/etc/gconf/schemas/*.schemas" returned error 1
> :error:activate Target org.macports.activate returned: shell command failed
> :debug:activate Backtrace: shell command failed
> while executing
> "$post $targetname"
> :info:activate Warning: the following items did not execute (for
> policykit-gnome): org.macports.activate
> :notice:activate Log for policykit-gnome is at:
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.
> org_release_ports_gnome_policykit-gnome/main.log
>
>
> Anybody have ideas?  It seems like the trac ticket system requires an
> account now, so I don't know how to inform the package maintainers of a
> problem.
>
> Thanks,
>
> -rich
>
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
Looks like there are no schema files to install.  Will take a look at
the port and see what's going on.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Error installing policykit-gnome due to gconf schema issue

[David Evans]

On 10/22/10 10:22 AM, Drake, Richard R wrote:
> Hello,
>
> I've been trying to install policykit-gnome from scratch for a while now and
> for the last few weeks, get an error.  I wonder if someone knows a fix. Here
> is what I do:
>
>  % sudo port -f uninstall installed
>  % sudo port selfupdate
>  % sudo port install policykit-gnome
>
> It gets all through the dependencies but fails activating policykit-gnome.
> Here is the error:
Ok, Rich, apparently policykit-gnome no longer installs any GConf schema
files which is
the souce of your error.

Post activate schema installation removed in r72660.

Try the selfupdate again when the rsync server is updated (~ 1 hour) and
it should work for you.

Thanks for the report.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: yelp will not install

[David Evans]

On 12/11/10 2:57 PM, Keith J. Schultz wrote:
> Hi All,
>
> Something strange happened.
>
> I had gnome installed via macports.
>
> I wanted to look at the docs for gnome. They are in docbook format. So I 
> decided to install yelp!
>
> When I executed sudo port install yelp
> port started installing a lot of port that where already installed as 
> universals. Then it first computed the dependancies for
> yelp and said it can not install yelp because there is no i386 version of nss!
>
> 1) I did not ask for a yelp+universal in the first place!
> 2) yelps port file must be hosed! 
>
>
> question does it hurt to have the universals installed. if so what is the 
> best method to get rid of them?
>
> regards
>   Keith
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
Note that yelp will build in 32 bit mode on a 64 bit machine if you
install xulrunner +internal_dependencies.
This works around the problem with nss (which will build either 32 bit
or 64 bit but not universal).


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: yelp will not install

[David Evans]

On 12/11/10 6:20 PM, Ryan Schmidt wrote:
> On Dec 11, 2010, at 20:12, David Evans wrote:
>
>> Note that yelp will build in 32 bit mode on a 64 bit machine if you
>> install xulrunner +internal_dependencies.
>> This works around the problem with nss (which will build either 32 bit
>> or 64 bit but not universal).
> It appears that nss will build 64-bit on 64-bit-capable machines with Snow 
> Leopard, and will build 32-bit on 32-bit-only machines, but will not for 
> example build 32-bit on 64-bit-capable machines with Snow Leopard with 
> build_arch set to i386, which is what I filed #27644 about.
>
>
>
>
Well, in any case, the problem here is that nss is not universal and
builds 64 bit by default on x86_64
platforms.  Since xulrunner is restricted to 32 bit builds, the default
version of xulrunner fails to
build with an arch mis-match error as stated by the OP.  However, using
the +internal_dependencies
variant allows xulrunner to build 32 bit without reference to the
external nss port and yelp builds
(and runs) using that variant.  Perhaps using xulrunner-devel is a
possibility too as Jeremy says but
I haven't tried that.

Perhaps it would make sense to have +internal_dependencies be the
default variant on x86_64 platforms.

This problem with yelp is really a pretty big deal because just about
every gnome related app tries to
launch yelp (via gnome-help) from its Help menu.  If yelp would build
reliably it really should be a run
time dependency for all these apps.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: ffmpeg video filters missing

[David Evans]

On 4/19/11 1:20 PM, David Liontooth wrote:
>
> I'd like to use the vf blackframe filter in ffmpeg, but the current
> available version does not include any filters (ffmpeg -filters shows
> no filters). In the ffmpeg documentation, it looks like filters are
> built unless they're explicitly disabled (--disable-filters), which is
> not done in the port file. Why are all the filters missing?
>
> Cheers,
> David
David --

Yes,  it looks like a problem.  It says that libavfilter is included but
ffmpeg itself doesn't list any.  Please file a ticket and I'll look at
it later tonight or tomorrow.  Thanks for the report.

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: open source (and in MacPorts) video cut with Flash video support

[David Evans]

On 10/18/11 11:57 AM, Fyodor Vassiley wrote:
> Hi
>
> I search for an open source (and in MacPorts) video cut with Flash
> video and MP4 support. Any recommendations? I have basically just cut
> out a section of the clip.
> I did it with MPEG Streamclip in the past, but users complaining that
> on some M$ players audio is out of sync (with VLC no problem).
>
> Fyodor
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>
transcode ?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: open source (and in MacPorts) video cut with Flash video support

[David Evans]

On 10/18/11 12:36 PM, Fyodor Vassiley wrote:
> On Tue, Oct 18, 2011 at 9:21 PM, David Evans  wrote:
>> transcode ?
> Do you have an example for my taks? Start and stop time? I searched
> for "cut" on the site
> http://www.transcoding.org/transcode?Transcode_Command_Line_Options
> which didn't got me results.
>
> Fyodor
>
Most of the interesting stuff is done with filters.  Try this one

http://www.transcoding.org/transcode?Filter_Plugins/Filter_Cut

Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: kde4-kile installation problems on Lion: okular - poppler dependencies

[David Evans]

On 11/15/11 3:10 PM, stef wrote:
> I've done an (from scratch) installation of macport (2.0.3) trying to
> install kde4-kile
> port but the installation fails.
>
> 1) The installation stops when trying to install okular with the
> following message
>
> "Error: Target org.macports.configure returned: Poppler must be
> installed with +qt4 and +quartz variants
>  Error: Failed to install okular"
>
> 2) Tried to install Poppler with +qt4 option give the following error
>
> "Error: Unable to execute port: Can't install unixODBC because
> conflicting ports are installed: libiodbc virtuoso"
>
>So I've tried to force the installation of unixODBC instead of
> libiodbc but the procedure fails when trying to
>install okular
>
> 3) Tried to install Poppler with +quartz option but useless as it
> continues to give Error message 1)
>
> How I can go around this problem (by the way I don't think I really
> need okular for kde4-kile as I
> can use Preview instead)
>
> Does anyone has any suggestions ?
>
> Thanks
>
> Stefano
>
You need to install poppler with both +qt4 and +quartz variants

sudo port install poppler +qt4 +quartz

unixODBC is a dependency of qt4-x11




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: kde4-kile installation problems on Lion: okular - poppler dependencies

[David Evans]

On 11/15/11 5:35 PM, Ryan Schmidt wrote:
> On Nov 15, 2011, at 18:49, David Evans wrote:
>
>> unixODBC is a dependency of qt4-x11
> qt4-x11 is way old, and I had hoped obsolete. I believe the plan had been to 
> make an +x11 variant of qt4-mac, but it's currently commented out.
>
Agreed, but the point here is that qt4-mac is what is required not
qt4-x11 hence the need for the
+quartz variant.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: PHP upgrade to v5.2.10

[David Evans]

Peter Oakley wrote:

Here is an example usage of the date() and time() functions:

snippetStart - - - - - -

$timestamp = time();
//echo $timestamp;
$thisYear = date('Y', $timestamp);
echo $thisYear;

- - - - - - snippetEnd

After the PHP upgrade to v5.2.10, this yields "" for $thisYear. 
Prior to the upgrade, $thisYear would be set to "2009". I also tried 
using the time function directly within the date function: $thisYear = 
date('Y', time()); Same result.


One other possibly important detail: I've installed a variant: php5 
+apache +macosx +mysql5 +t1lib


   - Pete O



On Jun 25, 2009, at 10:12 AM, Bradley Giesbrecht wrote:



On Jun 25, 2009, at 7:09 AM, Peter Oakley wrote:

Last night I was upgrading my web server to PHP v5.2.10 (from 
v5.2.8) and everything seemed to go ok, no warnings or major 
gotchas. But once I began using it, I could see there were some real 
problems with the time() and date() functions. It's possible that 
I'm just using these two functions in ways that are either wrong 
(but have up to now served to accomplish the task I was seeking to 
do) or are no longer allowed, for security reasons, in which case I 
will need to develop a work-around. Or something is going wrong with 
the update. I'm writing to this list to see if anyone else has 
experienced this same problem, or if you all might have some ideas 
as to what's going on here.


Give an example of your usage of time() and date(), what you expect 
and what you are getting.


// Brad


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


You should not specify +macosx on the command line.  It is selected
automatically based on your current platform.

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Error for installation glade in Tiger

[David Evans]

nuvolare wrote:
Hello, I'm writing becuase I need to have glade on my macbook pro and 
I've a week that I'm tring to install it, but I find lot's of error, 
and now 
I don't know how to resolve it, could you tell me what I've to do?

This is the error:

--->  Configuring gst-plugins-base
--->  Building gst-plugins-base
Error: Target org.macports.build returned: shell command " cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gst-plugins-base/work/gst-plugins-base-0.10.23" 
&& make all " returned error 2

Command output:   CCvs_4tap.o
  LINK  libgstvideoscale.la
warning: no debug map in executable (-arch i386)
Making all in volume
  CCgstvolume.o
  LINK  libgstvolume.la
warning: no debug map in executable (-arch i386)
Making all in sys
Making all in ximage
  CCximagesink.o
  CCximage.o
  LINK  libgstximagesink.la
warning: no debug map in executable (-arch i386)
Making all in xvimage
  CCxvimagesink.o
  LINK  libgstxvimagesink.la
warning: no debug map in executable (-arch i386)
Making all in ext
Making all in cdparanoia
  CCgstcdparanoiasrc.o
/opt/local/include/cdda_interface.h:175: warning: 'strerror_tr' 
defined but not used

  LINK  libgstcdparanoia.la
/usr/libexec/gcc/i686-apple-darwin8/4.0.1/ld: Undefined symbols:
_cdda_identify
_cdda_identify_scsi
collect2: ld returned 1 exit status
make[3]: *** [libgstcdparanoia.la] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Error: The following dependencies failed to build: devhelp webkit-gtk 
gst-plugins-base icu libsoup gnutls libgcrypt libgpg-error libtasn1 
lzo opencdk libproxy xorg-libXmu xorg-libXt xorg-util-macros 
hicolor-icon-theme libgnomeui gnome-icon-theme icon-naming-utils 
p5-xml-simple p5-xml-namespacesupport p5-xml-sax gnome-keyring 
libbonoboui libbonobo libgnome esound audiofile py25-gtk py25-cairo 
py25-numpy fftw-3 py25-nose py25-setuptools py25-gobject

Error: Status 1 encountered during processing.
MacbookPro:~ nuvolare$

This appears to be the problem reported in

http://trac.macports.org/ticket/19843

The problem is not with glade but with its dependency gst-plugins-base.

The cdparanoia plugin in that port is not compatible with
the latest version of cdparanoia provided by MacPorts.

The problem was fixed by disabling the build of this plugin by default.

http://trac.macports.org/changeset/52743

The fact that you are seeing this error indicates that you do not have
the latest version of port gst-plugins-base.

Please update your ports by doing the following

sudo port clean gst-plugins-base
sudo port selfupdate
sudo port upgrade outdated

then try installing glade again.

By the way, the port glade is an obsolete version (2.12.2) which is not
currently recommended nor maintained by the upstream developers.  Port 
glade3 (version 3.6.6) is the current stable release and is to be preferred.


sudo port install glade3




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Error for installation glade in Tiger

[David Evans]

nuvolare wrote:
Hello, I did what you told me and it installed succecfully, but now 
how I've to run gale3?

I tryed by Terminal e by X11 but with out resul
What I've to do?
Thank you


Assuming that the port is installed in the default prefix path 
(/opt/local), the glade executable is installed as


/opt/local/bin/glade-3

To confirm on your system try

devans% port contents glade3
Port glade3 contains:
 /opt/local/bin/glade-3
 /opt/local/include/libgladeui-1.0/gladeui/glade-accels.h
 /opt/local/include/libgladeui-1.0/gladeui/glade-activatable-editor.h
 /opt/local/include/libgladeui-1.0/gladeui/glade-app.h
 /opt/local/include/libgladeui-1.0/gladeui/glade-attributes.h
...

make sure that this is in your path by typing

devans% which glade-3
/opt/local/bin/glade-3

if not edit your path to include /opt/local/bin

Since this is an X11 application, be sure your X11 server is running and 
type


glade-3

from xterm or

open-x11 glade-3

from the Terminal which will start X11 for you if necessary


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Building vte fails

[David Evans]

Janosch Peters wrote:

Hi list,

I'd like to install gtk-sharp which depends on vte. Unfortunately, vte 
fails to build. Because I found nothing on the net, I assume that it 
has sth to do with my configuration, but I dont know what it could be.


Any ideas are highly appreciated.

cheers,
Janosch

--->  Building vte
Error: Target org.macports.build returned: shell command " cd "/opt/
local/var/macports/build/
_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_
vte/work/vte-0.20.5" && make all " returned error 2
Command output: vtebg.c: At top level:
vtebg.c:107: warning: declaration of 'atom' shadows a global 
declaration

vtebg.c:83: warning: shadowed declaration is here
vtebg.c:109: error: syntax error before 'XID'
vtebg.c:110: warning: function declaration isn't a prototype
vtebg.c: In function '_vte_property_get_pixmaps':
vtebg.c:110: warning: old-style function definition
vtebg.c:111: error: 'window' undeclared (first use in this function)
vtebg.c:111: error: (Each undeclared identifier is reported only once
vtebg.c:111: error: for each function it appears in.)
vtebg.c:114: error: 'type' undeclared (first use in this function)
vtebg.c:114: error: 'size' undeclared (first use in this function)
vtebg.c:115: error: 'pixmaps' undeclared (first use in this function)
vtebg.c: In function 'vte_bg_root_pixmap':
vtebg.c:124: error: 'XID' undeclared (first use in this function)
vtebg.c:124: error: 'pixmaps' undeclared (first use in this function)
vtebg.c:129: error: dereferencing pointer to incomplete type
vtebg.c:129: error: dereferencing pointer to incomplete type
vtebg.c:135: error: dereferencing pointer to incomplete type
vtebg.c: In function 'vte_bg_root_filter':
vtebg.c:166: error: 'XEvent' undeclared (first use in this function)
vtebg.c:166: error: 'xevent' undeclared (first use in this function)
vtebg.c:166: error: syntax error before ')' token
vtebg.c:171: error: 'PropertyNotify' undeclared (first use in this 
function)

vtebg.c:173: error: dereferencing pointer to incomplete type
vtebg.c:174: error: dereferencing pointer to incomplete type
make[3]: *** [libvte_la-vtebg.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

  

Janosch --

After seeing your email, I rebuilt vte here and did not encounter any 
problems so I need more information to diagnose what the

problem is.

First of all, make doubly certain that your ports are up to date by 
doing the following:


sudo port clean vte
sudo port selfupdate
sudo port upgrade outdated

then try and build vte again using debug mode

sudo port -d build vte

and if it fails again open a ticket against vte on track 
(http://trac.macports.org) including the full debug output

and specifying the following information about your system

Mac OS X version
Hardware (intel/ppc)
XCode Version installed

and we can go from there

at first glimpse it looks like an X11 related problem but need the 
detail to tell for sure


Dave
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Building vte fails

[David Evans]

Janosch Peters wrote:

On 07-02-2009, David Evans  wrote:
  

and if it fails again open a ticket against vte on track
(http://trac.macports.org) including the full debug output
and specifying the following information about your system



Done. Ticket is #20139. Its looking for a file called gdkx.h, which is 
not on my disk. Im pretty sure that it is the cause.


cheers,
Janosch

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

  
Yes,  you trying to build with gtk2 +no_x11 +quartz and vte does not 
support this.  To build vte you need to use
gtk2 without these variants.  Of course, this will conflict with other 
ports that you have built using gtk2 +no_x11 +quartz.


It's really not practical to try and mix x11 and quartz ports in the 
same build environment because of this. 

I recommend installing a second instance of macports so that you have 
one build environment for the default x11 ports

and a second for the +no_x11 +quartz variety.

See the MacPorts quide for instructions on how to do this.

 http://guide.macports.org/#installing.macports.source.multiple
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users