openGL update available on mac ADC site was Re: tiff doesn't build on leopard
On Oct 26, 2007, at 9:06 PM, Michael Staggs wrote: I do have the OpenGL SDK installed, and I just submitted a bug in trac. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users just as information: there is an update to openGL SDK on the mac ADC site dated 9/26/07 which is recomended for all Intel macs 10.4.9 and later. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Strange upgrade order.
I type port upgrade -R libpng
then first port tries to upgrade netpbm (and fails)
port upgrade -R libpng
--- Fetching netpbm
--- Attempting to fetch netpbm-10.26.44.tgz from
http://downloads.sourceforge.net/netpbm
--- Verifying checksum(s) for netpbm
--- Extracting netpbm
--- Applying patches to netpbm
--- Configuring netpbm
--- Building netpbm with target {}
rror: Target org.macports.build returned: shell command cd
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_netpbm/work/netpbm-10.26.44
gnumake messages=yes returned error 2
Then it upgrades libpng
Error: Unable to upgrade port: 1
--- Fetching libpng
--- Attempting to fetch libpng-1.2.22.tar.bz2 from
http://downloads.sourceforge.net/libpng
--- Verifying checksum(s) for libpng
--- Extracting libpng
--- Configuring libpng
--- Building libpng with target all
--- Staging libpng into destroot
--- Packaging tgz archive for libpng 1.2.22_0+darwin_8
--- Deactivating libpng 1.2.21_0+darwin_8
--- Installing libpng 1.2.22_0+darwin_8
--- Activating libpng 1.2.22_0+darwin_8
--- Cleaning libpng
and retries to upgrade netpbm
with same error
--- Building netpbm with target {}
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_netpbm/work/netpbm-10.26.44
gnumake messages=yes returned error 2
still tries...
Error: Unable to upgrade port: 1
--- Building netpbm with target {}
and retries...
then tries to deactivate already deactivated version of libpng !
Error: Unable to upgrade port: 1
--- Deactivating libpng 1.2.21_0+darwin_8
Error: Deactivating libpng 1.2.21_0 failed: Active version of libpng is not
1.2.21_0+darwin_8 but 1.2.22_0+darwin_8.
Why this strange behaviour ?
(PS: I keep the complete log of the session for who wants it)
--
Erwan
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Strange upgrade order.
I forgot : upgrading only netpbm gives the same error /usr/bin/ld: Undefined symbols: _pnm_xeltopixel collect2: ld returned 1 exit status gnumake[2]: *** [pnmtopng] Error 1 gnumake[1]: *** [other/all] Error 2 gnumake: *** [converter/all] Error 2 so there is certainly a problem with the netpbm port, but it does not explain why port tried foirts to upgrade the dependent package then tried to deactivate a second time libpng. -- Erwan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: mplayer and irssi +perl broken on Leopard?
Thank you. Submitted both bugs. lzo2 (for mplayer) bug: https://svn.macosforge.org/projects/macports/ticket/13003 irssi +perl bug: http://trac.macports.org/projects/macports/ticket/13004 Regards, SF On 27 Oct 2007, at 05:52, Ryan Schmidt wrote: On Oct 26, 2007, at 20:01, Steven Fauconnier wrote: First off, I'm new to the mailing list. Hope this is the correct one. I skimmed through the current threads but couldn't find anything regarding these subjects. I bought the new leopard and installed macports. Tried a sudo port install mplayer and it quited with an error on dependancy lzo2. Also tried to install irssi with perl support (sudo port install irssi +perl), also exited with an error. I've provided the logs in the attachments. Hope anyone can help out. Greetings, Steven Fauconnier mplayer_error.txt perl.txt Welcome! It's best if you submit bugs for these problems in Trac and assigned them to and Cc the ports' maintainers. Um... except that irssi has no maintainer. Well drat. It would still be good to file the two bugs. Then report back here and tell us the ticket numbers. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: openGL update available on mac ADC site was Re: tiff doesn't build on leopard
o just as information: there is an update to openGL SDK on the mac ADC site o dated 9/26/07 which is recomended for all Intel macs 10.4.9 and later. Do you have a link for this? I looked around the site and found something for CFM development, but not for any kind of general development audience. Thanks! -- Sal smile. -- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Sat, 27 Oct 2007, William Davis wrote: o o On Oct 26, 2007, at 9:06 PM, Michael Staggs wrote: o o I do have the OpenGL SDK installed, and I just submitted a bug in trac. o ___ o macports-users mailing list o macports-users@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-users o o o ___ o macports-users mailing list o macports-users@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-users o ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: openGL update available on mac ADC site was Re: tiff doesn't build on leopard
i was facing this problem earlier today - i simply downloaded the official source tarball from the libtiff website, untarred in the work dir of the package and installed away.. If you dont care about the ports registry you could compile directly; it worked fine for me (sorry if this has been discussed before but i only recently joined :-) -- Andrew On 27/10/2007, Salvatore Domenick Desiano [EMAIL PROTECTED] wrote: o just as information: there is an update to openGL SDK on the mac ADC site o dated 9/26/07 which is recomended for all Intel macs 10.4.9 and later. Do you have a link for this? I looked around the site and found something for CFM development, but not for any kind of general development audience. Thanks! -- Sal smile. -- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Sat, 27 Oct 2007, William Davis wrote: o o On Oct 26, 2007, at 9:06 PM, Michael Staggs wrote: o o I do have the OpenGL SDK installed, and I just submitted a bug in trac. o ___ o macports-users mailing list o macports-users@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-users o o o ___ o macports-users mailing list o macports-users@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-users o ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: openGL update available on mac ADC site was Re: tiff doesn't build on leopard
On Oct 27, 2007, at 10:16 AM, Salvatore Domenick Desiano wrote: o just as information: there is an update to openGL SDK on the mac ADC site o dated 9/26/07 which is recomended for all Intel macs 10.4.9 and later. Do you have a link for this? I looked around the site and found something for CFM development, but not for any kind of general development audience. Thanks! -- Sal smile. -- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University ADC is an https:// site and is dynamically generated so --no book marks. sorry. just login to ADC select: Downloads on that page look in column on right side of page: select: Open GL u r welcome :) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: openGL update available on mac ADC site was Re: tiff doesn't build on Leopard
I have Leopard. So I'd assume any updates from a month ago would already be applied to Leopard, which was released yesterday. But, I did find the error. It's been patched in the bug reports on trac.___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
wine won't build on Leopard
Ok, tiff has been fixed in the bug reports. Someone submitted a patch for the Portfile there. It has to do with the options that were supplied to Leopard at configure time. However, now I make it through all the dependencies, but when I get to wine I get the following: ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ credui.speccredui_main.o credui.res-o credui.dll.so - luser32 -lkernel32 ../../libs/port/libwine_port.a -L/opt/local/lib - framework CoreServices -lz /usr/bin/gcc-4.0 -c -I. -I. -I../../include -I../../include -I../../ include/msvcrt -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno- strict-aliasing -Wdeclaration-after-statement -Wwrite-strings - Wpointer-arith -I/opt/local/include -O2 -fno-builtin -o crtdll_main.o crtdll_main.c ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ crtdll.speccrtdll_main.o -o crtdll.dll.so -lmsvcrt - lkernel32 ../../libs/port/libwine_port.a -L/opt/local/lib -framework CoreServices -lz ./crtdll.spec:44: external symbol 'CRTDLL__basemajor_dll' is not a function ./crtdll.spec:45: external symbol 'CRTDLL__baseminor_dll' is not a function ./crtdll.spec:46: external symbol 'CRTDLL__baseversion_dll' is not a function ./crtdll.spec:66: external symbol 'CRTDLL__cpumode_dll' is not a function ./crtdll.spec:243: external symbol 'CRTDLL__osmajor_dll' is not a function ./crtdll.spec:244: external symbol 'CRTDLL__osminor_dll' is not a function ./crtdll.spec:245: external symbol 'CRTDLL__osmode_dll' is not a function ./crtdll.spec:247: external symbol 'CRTDLL__osversion_dll' is not a function winegcc: ../../tools/winebuild/winebuild failed. make[2]: *** [crtdll.dll.so] Error 2 make[1]: *** [crtdll] Error 2 make: *** [dlls] Error 2 Error: Status 1 encountered during processing. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
ErrorMacPortInstall
Hi I got this message after I installed MacPort. Fresh install on Leopard. couldn't load file /opt/local/share/macports/Tcl/pextlib1.0/ Pextlib.dylib: dlopen(/opt/local/share/macports/Tcl/pextlib1.0/ Pextlib.dylib, 10): no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture while executing load /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib (package ifneeded script) invoked from within package_native require Pextlib 1.0 (eval body line 1) invoked from within eval package_native $args (procedure package line 14) invoked from within package require Pextlib 1.0 (procedure mportinit line 365) invoked from within mportinit ui_options global_options global_variations Error: /opt/local/bin/port: Failed to initialize ports system, couldn't load file /opt/local/share/macports/Tcl/pextlib1.0/ Pextlib.dylib: dlopen(/opt/local/share/macports/Tcl/pextlib1.0/ Pextlib.dylib, 10): no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Re: ErrorMacPortInstall
On 27 Oct, 2007, at 16:50, Mack Johnson wrote: Hi I got this message after I installed MacPort. Fresh install on Leopard. couldn't load file /opt/local/share/macports/Tcl/pextlib1.0/ Pextlib.dylib: dlopen(/opt/local/share/macports/Tcl/pextlib1.0/ Pextlib.dylib, 10): no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture Mack: This is my fault. You're on powerpc, right? I built the Leopard dmg today on an Intel Mac and forgot +universal. I've heard that the 10.4 dmg will work fine on Leopard, so you can probably go ahead with that instead while I work on getting a fixed Leopard dmg up. jmpp: you might want to add +universal to the ReleaseProcess document. I completely forgot it since it wasn't necessary (or possible) when I did the Panther dmg, but it is now. Chris ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
XCode 3.0? Safe for old school Tiger users?
I see it's out, and I have downloaded it. But is there any benefit to installing it or any risk of screwing things up if I do? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: ErrorMacPortInstall
Got it, thanks I'll install 10.4. On Oct 27, 2007, at 2:02 PM, Chris Pickel wrote: On 27 Oct, 2007, at 16:50, Mack Johnson wrote: Hi I got this message after I installed MacPort. Fresh install on Leopard. couldn't load file /opt/local/share/macports/Tcl/pextlib1.0/ Pextlib.dylib: dlopen(/opt/local/share/macports/Tcl/pextlib1.0/ Pextlib.dylib, 10): no suitable image found. Did find: /opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture Mack: This is my fault. You're on powerpc, right? I built the Leopard dmg today on an Intel Mac and forgot +universal. I've heard that the 10.4 dmg will work fine on Leopard, so you can probably go ahead with that instead while I work on getting a fixed Leopard dmg up. jmpp: you might want to add +universal to the ReleaseProcess document. I completely forgot it since it wasn't necessary (or possible) when I did the Panther dmg, but it is now. Chris Mack Nez Johnson [EMAIL PROTECTED] http://macknezjohnson.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: XCode 3.0? Safe for old school Tiger users?
On 27/10/2007, paul beard [EMAIL PROTECTED] wrote: I see it's out, and I have downloaded it. But is there any benefit to installing it or any risk of screwing things up if I do? Xcode 3 will only work on Leopard, from the release notes: Supported configurations Xcode 3.0 will run on Mac OS X 10.5 (Leopard) on a Macintosh with either a PowerPC or an Intel processor. It will not install or run on earlier versions of Mac OS X. Xcode supports development for Mac OS X 10.3 (Panther) and Universal development for Mac OS X 10.4 (Tiger) and Mac OS X 10.5 (Leopard) using the Mac OS X SDK support Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: XCode 3.0? Safe for old school Tiger users?
On 10/27/07, Adam Mercer wrote: I see it's out, and I have downloaded it. But is there any benefit to installing it or any risk of screwing things up if I do? Xcode 3 will only work on Leopard, from the release notes: Does it come with a gcc tarball - including the new objective-c runtime? If so, maybe that can be tweaked and recompiled to run from the command line on Tiger. I think this is the first version of gcc that supports Objective-C 2.0 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
c3270
I've installed x3270 but it doesn't include c3270. Is there any reason why c3270 is not included in the Macports x3270 package? Thanks, --Shawn ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Is there any value to packages? [was Re: Why no binaries?]
Let me make a couple of general comments to help clear up this confusion: On Oct 26, 2007, at 1:56 PM, paul beard wrote: On 10/25/07, Daniel J. Luke [EMAIL PROTECTED] wrote: On Oct 24, 2007, at 10:11 PM, James Sumners wrote: Why doesn't MacPorts supply binary packages? No one has worked on it recently. If you're interested, I'm sure we would be interested in your help. Is there a status document that addresses where things stand on efforts like this? I haven't been all that successful at building packages within port (port pkg foo where foo is something i would rather not build again on a second machine). I think I may have resorted to taking the output of port contents and wrapping it in a tar or zip command, but that doesn't add any of the magic of receipts and the rest of the stuff that makes a ports system worth using. Building (binary) *packages* (and not archives as produced by archivemode and as explained by Anders), is one of MacPorts topmost long term goals, but trust me when I say that doing them right is by far much much more difficult than it sounds: 1) putting together a clean build environment and off it creating reliable, traceable reproducible builds of a particular port, it's destroot. A lot of work on this front has gone into MacPorts lately (mainly Eugene Epimenov's trace mode improvements) but unfortunately we're still lacking some key functionality to call our software infrastructure complete (runtime actions logging and server side processing of the build logs, among other things). I've been very busy with our new website lately but do plan to devote some energy into this in the hopefully not too distant future. 2) Once the build product, the destroot, is done and considered reliable, packaging it into, say, an rpm and/or a deb package is a completely different topic, with its own intricacies and integration issues between MacPorts and the packaging format we still need to sort out. All of this may sound a bit daunting and discouraging, but trust me that that's not my intent. Packaging is one of my personal top goals, but I need to explain that we want to do them right and that's not a simple and quick thing. Also, our our developer force is still unfortunately small and we just don't get enough leg power to move as fast as we'd like. If anyone is interested in helping to materialize this goal sooner than later please do step up, but be warned that we're not at the stage of furnishing the house, but actually looking into the design of the construction as we lay out the foundations. Regards,... -jmpp ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
ffmpeg doesn't build with leopard
I used the following command line: sudo port -v install ffmpeg +a52 +faac +faad +gpl +lame +x264 +xvid And I get this: make -C libavcodec all gcc -dynamiclib -Wl,-single_module -Wl,-install_name,/opt/local/lib/ libavcodec.dylib,-current_version,51.1.0,-compatibility_version,51.1.0 -Wl,-read_only_relocs,suppress -Wl,-dynamic,-search_paths_first -L/opt/ local/lib -o libavcodec.51.dylib bitstream.o utils.o allcodecs.o mpegvideo.o jrevdct.o jfdctfst.o jfdctint.o resample.o resample2.o dsputil.o motion_est.o imgconvert.o mpeg12.o simple_idct.o ratecontrol.o eval.o error_resilience.o raw.o faandct.o parser.o h264idct.o rangecoder.o h263.o opt.o bitstream_filter.o audioconvert.o imgresample.o i386/fdct_mmx.o i386/cputest.o i386/dsputil_mmx.o i386/ mpegvideo_mmx.o i386/motion_est_mmx.o i386/simple_idct_mmx.o i386/ idct_mmx_xvid.o i386/fft_sse.o i386/fft_3dn.o i386/fft_3dn2.o aasc.o ac3enc.o ac3tab.o ac3.o alac.o asv1.o atrac3.o mdct.o fft.o avs.o bethsoftvideo.o bmp.o bmpenc.o c93.o cavs.o cavsdsp.o golomb.o cinepak.o cljr.o cook.o cscd.o cyuv.o dca.o dnxhddec.o dsicinav.o dvbsubdec.o dvbsub.o dvdsubdec.o dvdsubenc.o dv.o dxa.o 8bps.o ffv1.o huffyuv.o flac.o flacenc.o flashsv.o flashsvenc.o flicvideo.o 4xm.o fraps.o gifdec.o lzw.o gif.o h261dec.o h261.o h261enc.o h263dec.o h264.o cabac.o idcinvideo.o imc.o indeo2.o indeo3.o interplayvideo.o dpcm.o jpeglsdec.o jpegls.o mjpegdec.o mjpeg.o jpeglsenc.o kmvc.o ljpegenc.o mjpegenc.o loco.o mace.o mjpegbdec.o mmvideo.o mpegaudiodec.o mpegaudiodecheader.o mpegaudio.o mpegaudiodata.o mpegaudioenc.o mpc.o msmpeg4.o msmpeg4data.o msrle.o msvideo1.o lcl.o nuv.o rtjpeg.o pnmenc.o pnm.o png.o ptx.o qdm2.o qdrw.o qpeg.o qtrle.o ra144.o ra288.o roqvideo.o roqaudioenc.o rpza.o rv10.o sgidec.o sgienc.o rle.o shorten.o smacker.o smc.o snow.o sonic.o sp5xdec.o svq1.o targa.o targaenc.o vp3.o xiph.o vp3dsp.o tiertexseqv.o tiff.o tiffenc.o lzwenc.o truemotion1.o truemotion2.o truespeech.o tscc.o tta.o txd.o s3tc.o ulti.o vc1.o vc1data.o vc1dsp.o vcr1.o vmdav.o vmnc.o vorbis_dec.o vorbis.o vorbis_data.o vorbis_enc.o vp5.o vp56.o vp56data.o vp6.o vqavideo.o wavpack.o wmadec.o wma.o wmaenc.o wnv1.o ws-snd1.o xan.o xl.o zmbv.o zmbvenc.o pcm.o adpcm.o adx.o g726.o a52dec.o faac.o faad.o mp3lameaudio.o x264.o xvidff.o xvid_rc.o aac_parser.o aac_ac3_parser.o ac3_parser.o cavs_parser.o dca_parser.o dvbsub_parser.o dvdsub_parser.o h261_parser.o h263_parser.o h264_parser.o mjpeg_parser.o mpeg4video_parser.o mpegaudio_parser.o mpegvideo_parser.o pnm_parser.o vc1_parser.o dump_extradata_bsf.o remove_extradata_bsf.o noise_bsf.o mp3_header_compress_bsf.o mp3_header_decompress_bsf.o mjpega_dump_header_bsf.o imx_dump_header_bsf.o pthread.o i386/idct_mmx.o i386/cavsdsp_mmx.o i386/snowdsp_mmx.o i386/vp3dsp_mmx.o i386/vp3dsp_sse2.o -L/opt/local/ var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavutil - lavutil -lz -la52 -lmp3lame -lm -lxvidcore -lx264 -lfaac -lfaad ld: warning codegen in _sad8_xy2_mmx2 (offset 0x001B) prevents image from loading in dyld shared cache ld: warning codegen in _sad16_xy2_mmx2 (offset 0x002C) prevents image from loading in dyld shared cache ld: warning codegen in _sad16_xy2_mmx2 (offset 0x0084) prevents image from loading in dyld shared cache ld: absolute addressing (perhaps -mdynamic-no-pic) used in _avg_qpel8_mc20_mmx2 from i386/dsputil_mmx.o not allowed in slidable image collect2: ld returned 1 exit status make[1]: *** [libavcodec.51.dylib] Error 1 make: *** [lib] Error 2 Warning: the following items did not execute (for ffmpeg): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Is there any value to packages? [was Re: Why no binaries?]
I forgot the icing on the cake: On Oct 27, 2007, at 6:20 PM, Juan Manuel Palacios wrote: Building (binary) *packages* (and not archives as produced by archivemode and as explained by Anders), is one of MacPorts topmost long term goals, but trust me when I say that doing them right is by far much much more difficult than it sounds: 1) putting together a clean build environment and off it creating reliable, traceable reproducible builds of a particular port, it's destroot. A lot of work on this front has gone into MacPorts lately (mainly Eugene Epimenov's trace mode improvements) but unfortunately we're still lacking some key functionality to call our software infrastructure complete (runtime actions logging and server side processing of the build logs, among other things). I've been very busy with our new website lately but do plan to devote some energy into this in the hopefully not too distant future. 2) Once the build product, the destroot, is done and considered reliable, packaging it into, say, an rpm and/or a deb package is a completely different topic, with its own intricacies and integration issues between MacPorts and the packaging format we still need to sort out. 3) Package distribution and install time dependency resolving (which is different from build time dependency resolving, what MacPorts currently has) is yet a new dimension we also need to tie into to do packages the right way. Granted that modern package managers have a sizable bit of this work covered already, but that by no means guarantees that we'll be able to drive blindfolded once we enter that terrain. Again, not-trying-to-discourage-anyone-but-actually-setting-the- record-straight-to-explain-why-we're-taking-so-long-to-deliver- packages -jmpp ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: c3270
Shawn Protsman [EMAIL PROTECTED] writes: I've installed x3270 but it doesn't include c3270. Is there any reason why c3270 is not included in the Macports x3270 package? You'll have to clue us in here. Isn't c3270 a different application, and therefore would be a separate port? If yes, the only reason we don't have a port for c3270 is that no one has yet contributed one Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: c3270
On Oct 27, 2007, at 6:15 PM, [EMAIL PROTECTED] wrote: Indeed, though it is part of x3270 it can be downloaded and built separately. The suite contains everything (http:// prdownloads.sourceforge.net/x3270/suite3270-3.3.6.tgz?download) or one could just download each implementation of the 3270 emulator separately. http://x3270.bgp.nu/download.html Shawn, I noticed that freebsd ports use separate ports for x3270 and c3270. But if the tarball contains sources for both, perhaps the portfile could be easily modified to install both. What do you think would be best, and would you be interested in patching the port? Mark Hi Mark, If that is the case with FreeBSD then I'd suggest they be kept separate. The 'suite' contains other items I don't use. It would be simpler to have x3270 and c3270 ports. I'll consider the patching and get back to you. I need to read through some patch documentation and understand how Macports handle things in more depth. If you could point me to some documentation I'd appreciate it. --Shawn ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
port -f upgrade port rebuilds already installed stuff
I recall that using port -f upgrade outdated would do this (reinstall stuff that was not outdated) but that, until today, performing the same command on an individual port would only install what was out-of-date. Today, however, when I upgrade the few ports that were outdated, lots of stuff was rebuilt, some of it for every port I upgraded. What changed to cause this? I'm pretty sure this is new. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: c3270
Shawn Protsman [EMAIL PROTECTED] writes: Hi Mark, If that is the case with FreeBSD then I'd suggest they be kept separate. The 'suite' contains other items I don't use. It would be simpler to have x3270 and c3270 ports. I'll consider the patching and get back to you. I need to read through some patch documentation and understand how Macports handle things in more depth. If you could point me to some documentation I'd appreciate it. --Shawn Shawn, It looks like there is a separate tarball. This is the download sirte for the freebsd port. http://x3270.bgp.nu/download/ It may be as simple as cloning the x3270 port and changing the port name, download file, and checksum. The documentation is kind of a mess right now because it is under development. But here it is: http://geeklair.net/new_macports_guide/ You can make a local portfile repository as shown in the docs, copy the x3270 portfile and modify it for c3270. If you can tell us how it installs manually, we can help you along if you want to try it. It is probably very easy. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
aqua/aquaterm fails to build on Leopard
Hi Aquaterm is failing to build for me on Leopard, I get the following error: [EMAIL PROTECTED] ~]$ sudo port install aquaterm --- Fetching aquaterm --- Verifying checksum(s) for aquaterm --- Extracting aquaterm --- Configuring aquaterm --- Building aquaterm with target -buildstyle Deployment -target AquaTerm Error: Target org.macports.build returned: shell command install_name_tool -id /opt/local/lib/libaquaterm.1.dylib /opt/local/var/macports/build/_Users_ram_opt_macports-10.5_mports_aqua_aquaterm/work/aquaterm/build/AquaTerm.framework/Versions/Current/AquaTerm returned error 1 Command output: install_name_tool: can't open file: /opt/local/var/macports/build/_Users_ram_opt_macports-10.5_mports_aqua_aquaterm/work/aquaterm/build/AquaTerm.framework/Versions/Current/AquaTerm (No such file or directory) Error: Status 1 encountered during processing. [EMAIL PROTECTED] ~] The AquaTerm.framework directory does not exist, there is however a directory AquaTerm.build in its place. Could this related to Xcode 3.0? Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: port -f upgrade port rebuilds already installed stuff
On Oct 27, 2007, at 11:00 PM, Lorin Rivers wrote: I recall that using port -f upgrade outdated would do this (reinstall stuff that was not outdated) but that, until today, performing the same command on an individual port would only install what was out-of-date. Today, however, when I upgrade the few ports that were outdated, lots of stuff was rebuilt, some of it for every port I upgraded. What changed to cause this? I'm pretty sure this is new. This has been the behavior for a while (since 1.3 or so, IIRC). You probably want the -n option in addition to -f. port -nf upgrade outdated -- Daniel J. Luke ++ | * [EMAIL PROTECTED] * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: openGL update available on mac ADC site was Re: tiff doesn't build on leopard
i was facing this problem earlier today - i simply downloaded the official source tarball from the libtiff website, untarred in the work dir of the package and installed away.. If you dont care about the ports registry you could compile directly; it worked fine for me Maybe a better way is download source uncompress to work dir do ./configure and make then do sudo port install libtiff thus it'll be put into registry correctly. I did this for some package (forgot its name) in this way since mysteriously it can not be installed by port install directly. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
