January 2008 - macports-users - lists.macosforge.org

Fwd: Re: [MacPorts] #14062: Website does not render properly in IE7
by Mark Hattam 24 Jan '08

24 Jan '08

>Subject: Re: [MacPorts] #14062: Website does not render properly in IE7 >From: macports-tickets-owner(a)lists.macosforge.org >To: mark(a)dxradio.demon.co.uk >Date: Thu, 24 Jan 2008 12:45:51 -0800 >X-BeenThere: macports-tickets(a)lists.macosforge.org >List-Id: MacPorts Project Trac ticket activity > <macports-tickets.lists.macosforge.org> >Sender: macports-tickets-bounces(a)lists.macosforge.org > >You are not allowed to post to this mailing list, and your message has >been automatically rejected. If you think that your messages are >being rejected in error, contact the mailing list owner at >macports-tickets-owner(a)lists.macosforge.org. > >Message-Id: <p06240802c3bea86aa9d2(a)[192.168.0.2]> >In-Reply-To: <058.977d62ed010cdb6ccaabac37a683bb9c(a)macosforge.org> >References: <049.7f44c0301c5a6af4ee58eab943976560(a)macosforge.org> > <058.977d62ed010cdb6ccaabac37a683bb9c(a)macosforge.org> >Date: Thu, 24 Jan 2008 20:45:55 +0000 >To: wsiegrist(a)apple.com, jmpp(a)macports.org >From: Mark Hattam <mark(a)dxradio.demon.co.uk> >Subject: Re: [MacPorts] #14062: Website does not render properly in IE7 >Cc: macports-tickets(a)lists.macosforge.org >Content-Type: text/plain; charset="us-ascii" ; format="flowed" >X-Brightmail-Tracker: AAAAAgirT1UIq5+s > >If I save the "offered" downloaded file to disk ... change the .php >into .htm (or .html) ... the file then opens up in IE7 and renders >everything. > >Changing the relative links for the .css etc to absolute links, >makes it look good too. > >In doing so, I haven't changed the <xml .... at the top of the file. >That's still there and IE7 doesn't appear to mind. > >So the difference is that IE7 doesn't understand or mis-interprets >the type of file being sent from the server, and thinks that it >can't render it. Other php pages (on other sites) work fine (usually >:-) ), but the server is sending something "different" here. > >Mark > >-- > > > >At 19:47 +0000 24/1/08, MacPorts wrote: >>#14062: Website does not render properly in IE7 >>----------------------------------+----------------------------------------- >> Reporter: wsiegrist(a)apple.com | Owner: jmpp(a)macports.org >> Type: defect | Status: new >> Priority: Normal | Milestone: Website & Documentation >> Component: website | Version: >>Resolution: | Keywords: ie7 windows content-type >>----------------------------------+----------------------------------------- >>Changes (by jmpp(a)macports.org) >> >> * cc: jmpp(a)macports.org (added) >> * owner: wsiegrist(a)apple.com => jmpp(a)macports.org >> * component: server/hosting => website >> >>Comment: >> >> I'm sure that's because of the `echo "<?xml version=\"1.0\" >> encoding=\"$encoding\"?>\n";` declaration at the top of each of our pages, >> which I crafted to strictly adhere to the XHTML standard, not caring too >> much about how bad IE handles that particular line, I admit. I don't think >> it's a server level PHP issue or anything of the sort. >> >> Personally I have no feeling about catering to such a broken browser as IE >> (there's always Firefox for Windows ;-), but I guess we could remove that >> line even if only for the purpose of giving MacPorts a wider net-surfing >> audience... >> >> -jmpp >> >>-- >>Ticket URL: >><http://trac.macosforge.org/projects/macports/ticket/14062#comment:1> >>MacPorts </projects/macports> >>Ports system for Mac OS

1 0

Re: [macports] Building in a jail?
by James Sumners 24 Jan '08

24 Jan '08

Forgot to send it to the list. Again! On Jan 23, 2008 10:17 PM, James Sumners <james.sumners(a)gmail.com> wrote: > Thanks for the suggestions. I have successfully built x86 binaries of > TeXmacs, patched to depend on texlive ;), and texlive. > > > On Jan 23, 2008 5:14 PM, Ryan Schmidt <ryandesign(a)macports.org> wrote: > > On Jan 23, 2008 4:21 PM, James Sumners wrote: > > > > > On Jan 23, 2008, at 15:06, Chris Pickel wrote: > > > > > >> On 23 Jan, 2008, at 12:34, James Sumners wrote: > > >> > > >>> I just upgraded from a PowerBook to a MacBook Pro. The migration > > >>> assistant tool kept my old macports system intact. I can still > > >>> run all > > >>> of the ports I had installed; particularly, I can still use TeXmacs > > >>> and teTeX. However, I had built all of my ports as PPC binaries, so > > >>> they are running via Rosetta. This also means I can't update any > > >>> of my > > >>> ports because port fails to recognize the architecture. Since there > > >>> have been so many posts lately about things failing to build on > > >>> 10.5, > > >>> I'm a little scared to wipe my old macports system and rebuild from > > >>> scratch. I particularly can't afford to be without a LaTeX > > >>> environment > > >>> right now. > > >>> > > >>> So, is there any way I can "jail" a new installation of macports? > > >>> If I > > >>> can build everything successfully, I want to be able to delete > > >>> the old > > >>> version and move the new one to the standard location. > > >> > > >> You can have multiple installs of MacPorts on a single system. > > >> However, some ports may not work if you change the location of the > > >> installation. So, I would recommend that you move the existing > > >> installation aside (i.e. `sudo mv /opt/local /opt/ppc`) and > > >> install a new one in its place. If you succeed at getting the new > > >> one running sufficiently, you can get rid of the old one; > > >> otherwise move the old one back in place. > > >> > > >> In order to quarantine two MacPorts installations, you should > > >> build them from source. The tarballs are available on the > > >> Downloads [1] page. You should ./configure them along the lines of > > >> the following: > > >> > > >> % ./configure --prefix=/opt/local \ > > >> --with-tclpackage=/opt/local/share/macports/Tcl > > >> > > >> You can pick something other than /opt/local if you want, but it > > >> might not work to move it back to /opt/local later, should you > > >> care. Also, it's possible that you might get conflicts for files > > >> installed in /Applications/MacPorts or /Library/Frameworks. > > > > > > I was concerned about configuration files outside of /opt/local. But > > > now that I think about it, even if there are any, the Intel port won't > > > have a different configuration than the PPC one. So that could > > > probably work. Thanks. > > > > Configuration files go in ${prefix}/etc, so there shouldn't be any > > outside of ${prefix}. However, some ports do install other things > > outside of ${prefix}. For example, into /Applications/MacPorts. You > > should also rename /Applications/MacPorts to /Applications/MacPorts- > > ppc before installing MacPorts again, and remove it later once > > everything's ok. If you had any server programs, they may also have > > installed startup items in /Library/LaunchDaemons (if you were > > running Tiger and up) or /Library/StartupItems (for Panther and before). > > > > Some ports will install other things outside the prefix, perhaps in / > > usr/X11R6. I'm guessing these items weren't migrated from the old > > system, therefore any ports that depend on this are now broken. > > > > You don't need to build MacPorts from source; you could also just > > install from the Mac Ports 1.6.0 Leopard disk image. But before you > > do, you will also need to rename /Library/Tcl/macports1.0, for > > example to /Library/Tcl/macports1.0-ppc. > > > > > > If your "port" command were working, "port contents foo" would show > > you what a port installed. You could run "port contents installed" to > > see everything installed by all ports, and filter this to see > > everything that was installed outside of the prefix, for example > > since your prefix is /opt/local you could run: > > > > port contents installed | grep -v '^Port .* contains:' | grep -v /opt/ > > local > > > > However, you said yourt "port" command isn't working, probably since > > it needs the Tcl libraries in /Library/Tcl/macports1.0, and these are > > for the wrong architecture. > > > > If you still have this ports installation on the PowerPC Mac on which > > it was originally installed, you could run the above command there, > > to discover where else outside of ${prefix} items were installed, and > > use that information to remove those files on the Intel Mac prior to > > reinstalling MacPorts. > > > > > > > > -- > > James Sumners > http://james.roomfullofmirrors.com/ > > "All governments suffer a recurring problem: Power attracts > pathological personalities. It is not that power corrupts but that it > is magnetic to the corruptible. Such people have a tendency to become > drunk on violence, a condition to which they are quickly addicted." > > Missionaria Protectiva, Text QIV (decto) > CH:D 59 > -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59

1 1

Fwd: Checksum failure with ncbi-tools, then missing getfeat.
by Matt Scilipoti 24 Jan '08

24 Jan '08

Hello all, Thanks for providing a service like macports and going through the effort of creating ports. I hope you can help me. I'm trying to install ncbi_tools, but I get a checksum error: % sudo port install ncbi_tools ---> Fetching ncbi_tools ---> Attempting to fetch ncbi.tar.gz from ftp://ftp.ncbi.nlm.nih.gov/toolbox/ncbi_tools/ ---> Verifying checksum(s) for ncbi_tools Error: Checksum (md5) mismatch for ncbi.tar.gz Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Status 1 encountered during processing. We managed to get the file, md5 it, update the local portfile, and start the install, only to find that getfeat is missing? % sudo port install ncbi_tools Portfile changed since last build; discarding previous state. ---> Fetching ncbi_tools ---> Verifying checksum(s) for ncbi_tools ---> Extracting ncbi_tools ---> Configuring ncbi_tools ---> Building ncbi_tools ---> Staging ncbi_tools into destroot Error: Target org.macports.destroot returned: xinstall: Cannot stat: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_ncbi_tools/work/ncbi/bin/getfeat, No such file or directory Error: Status 1 encountered during processing. Any ideas? For future reference... A google search shows that the checksum error has occurred before. This is one of the reasons many libraries have started including version numbers in the file name. This practice also ensures that prior versions of the libraries remain available. Thanks for attention in this matter. -- Matt Scilipoti Port v 1.600 OSX 10.5.1

4 14

Re: [macports] Building in a jail?
by James Sumners 23 Jan '08

23 Jan '08

Forgot to include the list. *grumble* On Jan 23, 2008 4:21 PM, James Sumners <james.sumners(a)gmail.com> wrote: > I was concerned about configuration files outside of /opt/local. But > now that I think about it, even if there are any, the Intel port won't > have a different configuration than the PPC one. So that could > probably work. Thanks. > > On Jan 23, 2008 4:06 PM, Chris Pickel <sfiera(a)macports.org> wrote: > > You can have multiple installs of MacPorts on a single system. > > However, some ports may not work if you change the location of the > > installation. So, I would recommend that you move the existing > > installation aside (i.e. `sudo mv /opt/local /opt/ppc`) and install a > > new one in its place. If you succeed at getting the new one running > > sufficiently, you can get rid of the old one; otherwise move the old > > one back in place. > > > -- > James Sumners > http://james.roomfullofmirrors.com/ > > "All governments suffer a recurring problem: Power attracts > pathological personalities. It is not that power corrupts but that it > is magnetic to the corruptible. Such people have a tendency to become > drunk on violence, a condition to which they are quickly addicted." > > Missionaria Protectiva, Text QIV (decto) > CH:D 59 > -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59

3 2

[macports] Building in a jail?
by James Sumners 23 Jan '08

23 Jan '08

I just upgraded from a PowerBook to a MacBook Pro. The migration assistant tool kept my old macports system intact. I can still run all of the ports I had installed; particularly, I can still use TeXmacs and teTeX. However, I had built all of my ports as PPC binaries, so they are running via Rosetta. This also means I can't update any of my ports because port fails to recognize the architecture. Since there have been so many posts lately about things failing to build on 10.5, I'm a little scared to wipe my old macports system and rebuild from scratch. I particularly can't afford to be without a LaTeX environment right now. So, is there any way I can "jail" a new installation of macports? If I can build everything successfully, I want to be able to delete the old version and move the new one to the standard location. -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59

3 2

Re: ntop fails to build
by markd＠macports.org 23 Jan '08

23 Jan '08

>On Jan 7, 2008, at 12:49, Jay Chandler wrote: > >> jay@Singularity~$ sudo port install ntop >> ---> Building ntop 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_net_n >> top/work/ntop-3.3" && gnumake all " returned error 2 >> Command output: gnumake all-recursive >> Making all in . >> /bin/sh ./libtool --tag=CC --mode=compile /usr/bin/gcc-4.0 - >> DHAVE_CONFIG_H -I. -I. -g -Os -DBUILD=112 - >> DMACOSX_DEPLOYMENT_TARGET=10.5 -F/System/Library/PrivateFrameworks/ >> -F/System/Library/Frameworks/ -pipe -Udarwin9 -Ddarwin9=darwin9 -I. >> -I/usr/local/include -I/opt/local/include -DDARWIN -I/usr/local/ >> include -g -no-cpp-precomp -O2 -I/opt/local/include -I/usr/local/ >> include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing- >> declarations -Wnested-externs -fno-common -DPIC -MT address.lo -MD >> -MP -MF .deps/address.Tpo -c -o address.lo address.c >> /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -g -Os -DBUILD=112 - >> DMACOSX_DEPLOYMENT_TARGET=10.5 -F/System/Library/PrivateFrameworks/ >> -F/System/Library/Frameworks/ -pipe -Udarwin9 -Ddarwin9=darwin9 -I. >> -I/usr/local/include -I/opt/local/include -DDARWIN -I/usr/local/ >> include -g -no-cpp-precomp -O2 -I/opt/local/include -I/usr/local/ >> include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing- >> declarations -Wnested-externs -fno-common -DPIC -MT address.lo -MD - >> MP -MF .deps/address.Tpo -c address.c -fno-common -DPIC -o .libs/ >> address.o >> In file included from ntop.h:484, >> from address.c:21: >> globals-structtypes.h:103: error: two or more data types in >> declaration specifiers >> globals-structtypes.h:103: warning: useless type name in empty >> declaration >> gnumake[2]: *** [address.lo] Error 1 >> gnumake[1]: *** [all-recursive] Error 1 >> gnumake: *** [all] Error 2 >> >> Error: Status 1 encountered during processing. > >I see this problem was reported 3 weeks ago but the maintainer hasn't >commented on it yet. > >[ >https://owa016.msoutlookonline.net/owa/redir.aspx?URL=http%3a%2f%2ftrac.mac… >]http://trac.macosforge.org/projects/macports/ticket/13610 > >I'll add you to the Cc list of that ticket so you're informed of its >progress. > >I see you're running Mac OS X 10.5. Looks like the reporter of that >ticket was too. And do you have Xcode 3? What version of MacPorts do >you have, and what architecture is your processor? > >I note occurrences of /usr/local in your output above, and also in >the filed ticket. What do you have in /usr/local? It can conflict >with MacPorts ports, so we recommend not having anything in /usr/ >local. Try renaming /usr/local to /usr/local-off and cleaning (sudo >port clean --work ntop) and building (sudo port install ntop) ntop >again. If it works, you'll know something in /usr/local conflicted, >and you should install whatever you need using MacPorts instead of >manually installing in /usr/local. Ntop started failing to build on leopard, and I don't know yet what the solution is. I tried renaming /usr/local just to be sure and it didn't help. I'll ask the ntop support list shortly and leave comments in the ticket later at least to show I've seen it. Mark

1 0

py-PyX package update?
by Brian Barnes 23 Jan '08

23 Jan '08

Package PyX is at version 0.9: http://trac.macports.org/projects/macports/browser/trunk/dports/ python/py-pyx/Portfile Version 0.10 has been available since last fall: http://news.gmane.org/gmane.comp.python.pyx.users/cutoff=744 http://pyx.sourceforge.net/ ...and a portfile ticket has been submitted which includes pyx 0.10 with a python 2.5 dependency (it is not clear to me if this dependency is truly required by pyx): http://trac.macosforge.org/projects/macports/attachment/ticket/13277/ Portfile This portfile also has a tetex dependency, but perhaps texlive would also work for it? Anyway, it would be nice to have the newer one. :) I was going to open a trac ticket until I did a search and saw this ticket was submitted two months ago. If anyone gets around to updating the port, thank you! -Brian cc: to jmpp as last committer to the py-pyx portfile, which has nomaintainer. my apology if this is considered spam!

2 1

xfig patch
by Patrick González 22 Jan '08

22 Jan '08

Hi, I have installed MacPorts in the intend of using xfig. Unfortunatly, the port of xfig does not work. Apparently, someone posted a patch file to address this issue but I have no idea how to use this patch file. I have looked the user guide but it was of little help since it explains more how to create such patch file than how to use it. Can someone explain me how to fix the xfig port step by step ? Many thanks. Patrick González, Directeur des programmes de 2e et 3e cycles Département d'économique, Université Laval, Québec, G1K 7P4 (418) 656-2131 poste 7735 pgon(a)ecn.ulaval.ca *** http://132.203.59.99

2 1

Re: xsane build errors
by Ryan Schmidt 21 Jan '08

21 Jan '08

On Jan 21, 2008, at 14:53, John Gorst wrote: > On 21 Jan 2008, at 19:19, Ryan Schmidt wrote: > >> On Jan 20, 2008, at 11:28, John Gorst wrote: >> >>> I am getting the following error messages after a lengthy build >>> process..... >>> >>> john-gorsts-macbook-pro-15:~ john$ sudo port install xsane >>> Error: The following dependencies failed to build: gettext >>> ncurses ncursesw gawk gimp2 libexif libgnomeui gnome-keyring >>> glib2 gtk2 atk gtk-doc scrollkeeper pango libgcrypt libgpg-error >>> libbonoboui dbus xmlto getopt dbus-glib gconf orbit2 libidl gnome- >>> vfs gnome-mime-data neon libbonobo popt libglade2 libgnome >>> libgnomecanvas gail libgtkhtml libmng autoconf help2man p5-locale- >>> gettext automake librsvg libcroco libgsf poppler py25-gtk py25- >>> cairo py25-numeric python25 py25-gobject >>> Error: Status 1 encountered during processing. >>> >>> Here is the debug log entry for one of the missing dependancies. >>> >>> DEBUG: Requested variant darwin is not provided by port gnome- >>> keyring. >>> DEBUG: Requested variant i386 is not provided by port gnome-keyring. >>> DEBUG: Requested variant macosx is not provided by port gnome- >>> keyring. >>> >>> Many thanks for any help! >> >> You haven't shown us the relevant information. Which of the >> dependencies failed to build, and why? I suppose maybe it was >> gnome-keyring, but the DEBUG messages you showed us from gnome- >> keyring are normal status messages, not errors. (Not all ports >> provide the variants "darwin", "i386", "macosx", and so forth, but >> if those variants exist, MacPorts uses them. MacPorts is just >> telling you that gnome-keyring doesn't have these variants. It's >> not a problem.) >> >> Show us the actual error message you get when installing xsane. Or >> is it one of the existing tickets we have for gnome-keyring? >> >> http://trac.macports.org/projects/macports/query? >> status=new&status=assigned&status=reopened&summary=%7Egnome- >> keyring&order=priority > > Thanks for your reply. > > The actual message when I type 'sudo port install xsane' is shown > above. > > I just included a few lines of 'sudo port -d install xsane' as it > was so long and the list wouldnt post it!! > > Here are another few lines I have thought to be suspicious! > > DEBUG: Found port in file:///opt/local/var/macports/sources/ > rsync.macports.org/release/ports/devel/gettext > DEBUG: Searching for dependency: gettext > DEBUG: Didn't find receipt, going to depspec regex for: gettext I think this is also normal output, saying that gettext is not installed, so it's going to install gettext. And first it's going to install any dependencies of gettext. > I will email you my -debug log off list. > > Thank you for your help I can see why you're confused. I was too! There's nothing but DEBUG output. I think that you're experiencing a circular dependency issue: gettext depends on ncurses, ncurses depends on ncursesw, ncursesw depends on gawk (on Leopard only), and gawk depends on gettext. http://trac.macosforge.org/projects/macports/ticket/13898 I resolved this problem a week ago by making ncursesw no longer depend on gawk, which means your ports tree is out of date. So you should update your ports: sudo port selfupdate Then check which ports are outdated; ncursesw should show up in the list: port outdated Then you should rebuild ncursesw so it picks up my fix from last week and no longer depends on gawk: sudo port upgrade ncursesw You should also upgrade anything else shown by "port outdated". Then you'll hopefully be able to install xsane: sudo port install xsane

1 0

gcc43 and Java/GCJ
by Michael Franz 21 Jan '08

21 Jan '08

Hi, I noticed that the gcc43 port does not have java configured. Are there issues with building the Java language in this build? The fortran language is also not configured, but it is listed as variant. If no one has already requested the java support, I would like to be the first. I have tried to compile with the java enabled but it fails on the x86_64 linking. I am building on OS X 10.4.11. Michael /usr/bin/ld: fatal error in /usr/bin/ld64 collect2: ld returned 1 exit status make[5]: *** [libgcj.la] Error 1 make[5]: *** Waiting for unfinished jobs.... make[4]: *** [all-recursive] Error 1 make[3]: *** [multi-do] Error 1 make[2]: *** [all-multi] Error 2 make[1]: *** [all-target-libjava] Error 2 make: *** [bootstrap] Error 2

1 0