From ludwig at fh-worms.de Mon Oct 1 00:17:16 2007 From: ludwig at fh-worms.de (Christoph Ludwig) Date: Tue Oct 9 16:43:40 2007 Subject: port sqlite3 broken In-Reply-To: <4A2A6096-39F7-4B4F-B53E-887F8C7DA7BB@macports.org> References: <20070930092404.GC7387@castellio.local> <4A2A6096-39F7-4B4F-B53E-887F8C7DA7BB@macports.org> Message-ID: <20071001071716.GA16983@castellio.ztt.fh-worms.de> On Mon, Oct 01, 2007 at 01:46:05AM -0500, Ryan Schmidt wrote: > On Sep 30, 2007, at 04:24, Christoph Ludwig wrote: > > >my attempts to upgrade sqlite3 on a MacBook Pro (Intel, Mac OS X > >10.4.10) > >failed with the error message below. Is this a known problem? Does > >anyone have > >a fix for it? [...] > > That would be this bug: > > http://trac.macports.org/projects/macports/ticket/12790 > > You can add yourself to the bug's Cc list if you would like to be > informed of the bug's progress. thanks. Unfortunately, I cannot figure out how to do that: I followed the link you provided. There, I logged into my account (using the "Login" link on the top right.) I am then presented with an editor field that allows me to add an additional comment to the report - but I cannot find a field to add myself to the CC list. The only comment I could add was a "me too", which I do not consider helpful information that needs to be added to the bug database. I may miss the obvious, but this interface does not seem very intuitive to me. Regards Christoph -- FH Worms - University of Applied Sciences Fachbereich Informatik / Telekommunikation Erenburgerstr. 19, 67549 Worms, Germany From boeyms at macports.org Mon Oct 1 00:39:14 2007 From: boeyms at macports.org (Boey Maun Suang) Date: Tue Oct 9 16:43:40 2007 Subject: Can't install seahorse (was: can't install gnome) In-Reply-To: References: Message-ID: <533184B0-8494-40FC-AFED-ABC17CE7816D@macports.org> Hi Matthias, I've seen errors like this with ports that I maintain, and a page on the GMP website says that it is a bug with the Apple linker provided in XCode [1]: "The linker has a long-standing and serious bug that causes references from one file to common data in another file to give spurious error messages about undefined symbols, unless there are also references to the text segment between the same files." (Note that the GMP page suggests that it affects the 32-bit Intel version but not others; I've only tested this on my MacBook Pro, so I can't say for sure that you're experiencing the same problem on your PowerBook, but it looks exactly the same.) The only way to work around this is for the Seahorse source code to be patched, but I'm afraid I don't really understand the error and how to fix it (I either had upstream developers fix them for me, or took inspired guesses from commented patches that I saw in other people's source). I've CC'ed this message to the maintainer also, so he can hopefully pass it on to the upstream developers for them to fix. Kind regards, Maun Suang -- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org From ryandesign at macports.org Mon Oct 1 01:18:25 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: port sqlite3 broken In-Reply-To: <20071001071716.GA16983@castellio.ztt.fh-worms.de> References: <20070930092404.GC7387@castellio.local> <4A2A6096-39F7-4B4F-B53E-887F8C7DA7BB@macports.org> <20071001071716.GA16983@castellio.ztt.fh-worms.de> Message-ID: <991119D1-DBB9-4DE3-8589-BAA92F6C7299@macports.org> On Oct 1, 2007, at 02:17, Christoph Ludwig wrote: > On Mon, Oct 01, 2007 at 01:46:05AM -0500, Ryan Schmidt wrote: >> On Sep 30, 2007, at 04:24, Christoph Ludwig wrote: >> >>> my attempts to upgrade sqlite3 on a MacBook Pro (Intel, Mac OS X >>> 10.4.10) >>> failed with the error message below. Is this a known problem? Does >>> anyone have >>> a fix for it? > [...] >> >> That would be this bug: >> >> http://trac.macports.org/projects/macports/ticket/12790 >> >> You can add yourself to the bug's Cc list if you would like to be >> informed of the bug's progress. > > thanks. Unfortunately, I cannot figure out how to do that: > > I followed the link you provided. There, I logged into my account > (using the > "Login" link on the top right.) I am then presented with an editor > field that > allows me to add an additional comment to the report - but I cannot > find a > field to add myself to the CC list. The only comment I could add > was a "me > too", which I do not consider helpful information that needs to be > added to > the bug database. > > I may miss the obvious, but this interface does not seem very > intuitive to me. Sorry, I keep assuming everyone can edit every bug's Cc list, but there appear to be different levels of privileges in Trac, and the basic one appears not to let you do that. I'll bring it up on the macports-dev list and see if we can change that. In the mean time I added your address to the Cc list. From D.S.Murray-Rust at sms.ed.ac.uk Mon Oct 1 02:48:18 2007 From: D.S.Murray-Rust at sms.ed.ac.uk (Dave Murray-Rust) Date: Tue Oct 9 16:43:41 2007 Subject: Segfaults when staging into destroot In-Reply-To: References: Message-ID: <9C7B27D4-C218-4BD9-B696-4D1709140D3F@sms.ed.ac.uk> On 30 Sep 2007, at 19:18, William Davis wrote: > > On Sep 22, 2007, at 2:59 PM, Dave Murray-Rust wrote: > >> Hi All, >> >> I'm having real hassles with port - most packages fail to install, >> with a segfault, e.g.: > > did you do all the folowing when removing macports? > > MacPorts can be removed by issuing the following command from > within Terminal: > > sudo rm -rf \ > /opt/local \ > /Applications/MacPorts \ > /Library/Tcl/macports1.0 \ > /Library/LaunchDaemons/org.macports.* \ > /Library/StartupItems/DarwinPortsStartup > Yup - I did copy/paste from the macports wiki > > and btw you know your PATH has to include /opt/local/bin and /opt/ > local/sbin do you not? Yup. Cheers, dave From D.S.Murray-Rust at sms.ed.ac.uk Mon Oct 1 02:45:06 2007 From: D.S.Murray-Rust at sms.ed.ac.uk (Dave Murray-Rust) Date: Tue Oct 9 16:43:41 2007 Subject: Segfaults when staging into destroot Message-ID: <71CCE4A3-7988-4A98-9CE9-5E29A48FA522@sms.ed.ac.uk> On 1 Oct 2007, at 07:28, Ryan Schmidt wrote: > On Sep 22, 2007, at 13:59, Dave Murray-Rust wrote: > >> I'm having real hassles with port - most packages fail to install, >> with a segfault, e.g.: >> >> groke:503:dave>port install tiff >> ---> Fetching zlib >> ---> Verifying checksum(s) for zlib >> ---> Extracting zlib >> ---> Applying patches to zlib >> ---> Configuring zlib >> ---> Building zlib with target all >> ---> Staging zlib into destroot >> tclsh(394) malloc: *** error for object 0x312770: double free >> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >> tclsh(394) malloc: *** error for object 0x312770: double free >> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >> tclsh(394) malloc: *** error for object 0x312770: double free >> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >> ---> Installing zlib 1.2.3_1 >> tclsh(394) malloc: *** error for object 0x313760: double free >> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >> tclsh(394) malloc: *** error for object 0x313790: double free >> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >> tclsh(394) malloc: *** error for object 0x3137f0: double free >> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >> Segmentation fault > > That should not happen (obviously). Never seen this problem before. > >> I've tried using a different tclsh, but the same problem persists. >> I'm not certain whether port is using the new one... I've exported >> PATH=/usr/local/bin, and which tclsh points to the newly installed >> ActiveState tclsh, but I don't know if port uses its own internal >> version or something? >> >> Any suggestions on where to start debugging this? >> >> So far I've tried uninstalling and reinstalling, selfupgrade, >> moving fink (/sw) out of the way in case it was causing a >> conflict, but with no luck. I get this problem on almost all >> packages. Interestingly, it was not there originally - at least, >> there are some packages which I had installed before I removed and >> reinstalled port, which now fail to install. > > Make sure you have the latest OS and all updates (10.4.10 or > 10.3.9). Make sure you have the latest Xcode (2.4.1 for 10.4.10; > 1.5 for 10.3.9). Make sure you have the latest MacPorts (1.5.2). > Make sure you do NOT have anything at all installed in /sw, /usr/ > local or any other place referenced in your PATH. Just have > MacPorts, which is usually in /opt/local. It works great by itself, > but other software installed in other locations can cause > unpredictable problems. > OSX == 10.4.10, Xcode == 2.4.1 OK, I've moved everything which was installed (temporarily): dhcp-2-178:508:dave>echo $PATH /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/ local/bin:/usr/texbin dhcp-2-178:509:dave>ls /sw ls: /sw: No such file or directory dhcp-2-178:510:dave>ls /usr/local/bin ls: /usr/local/bin: No such file or directory dhcp-2-178:511:dave>port --version MacPorts 1.520 Entering interactive mode... ("help" for help, "quit" to quit) [Users/dave] > ^D Goodbye dhcp-2-178:512:dave>sudo port install tiff ---> Installing zlib 1.2.3_1 tclsh(8332) malloc: *** error for object 0x311fc0: double free tclsh(8332) malloc: *** set a breakpoint in szone_error to debug tclsh(8332) malloc: *** error for object 0x312020: double free tclsh(8332) malloc: *** set a breakpoint in szone_error to debug tclsh(8332) malloc: *** error for object 0x311e20: double free tclsh(8332) malloc: *** set a breakpoint in szone_error to debug tclsh(8332) malloc: *** error for object 0x312020: double free tclsh(8332) malloc: *** set a breakpoint in szone_error to debug Segmentation fault Cheers, dave From ryandesign at macports.org Mon Oct 1 02:51:46 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: Segfaults when staging into destroot In-Reply-To: References: <79A46490-8C98-4760-A75F-D4006EE00153@macports.org> Message-ID: <10DA705D-F154-411D-87C9-560BAECC2E6D@macports.org> On Oct 1, 2007, at 04:45, Dave Murray-Rust wrote: > On 1 Oct 2007, at 07:28, Ryan Schmidt wrote: > >> On Sep 22, 2007, at 13:59, Dave Murray-Rust wrote: >> >>> I'm having real hassles with port - most packages fail to >>> install, with a segfault, e.g.: >>> >>> groke:503:dave>port install tiff >>> ---> Fetching zlib >>> ---> Verifying checksum(s) for zlib >>> ---> Extracting zlib >>> ---> Applying patches to zlib >>> ---> Configuring zlib >>> ---> Building zlib with target all >>> ---> Staging zlib into destroot >>> tclsh(394) malloc: *** error for object 0x312770: double free >>> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >>> tclsh(394) malloc: *** error for object 0x312770: double free >>> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >>> tclsh(394) malloc: *** error for object 0x312770: double free >>> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >>> ---> Installing zlib 1.2.3_1 >>> tclsh(394) malloc: *** error for object 0x313760: double free >>> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >>> tclsh(394) malloc: *** error for object 0x313790: double free >>> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >>> tclsh(394) malloc: *** error for object 0x3137f0: double free >>> tclsh(394) malloc: *** set a breakpoint in szone_error to debug >>> Segmentation fault >> >> That should not happen (obviously). Never seen this problem before. >> >>> I've tried using a different tclsh, but the same problem >>> persists. I'm not certain whether port is using the new one... >>> I've exported PATH=/usr/local/bin, and which tclsh points to the >>> newly installed ActiveState tclsh, but I don't know if port uses >>> its own internal version or something? >>> >>> Any suggestions on where to start debugging this? >>> >>> So far I've tried uninstalling and reinstalling, selfupgrade, >>> moving fink (/sw) out of the way in case it was causing a >>> conflict, but with no luck. I get this problem on almost all >>> packages. Interestingly, it was not there originally - at least, >>> there are some packages which I had installed before I removed >>> and reinstalled port, which now fail to install. >> >> Make sure you have the latest OS and all updates (10.4.10 or >> 10.3.9). Make sure you have the latest Xcode (2.4.1 for 10.4.10; >> 1.5 for 10.3.9). Make sure you have the latest MacPorts (1.5.2). >> Make sure you do NOT have anything at all installed in /sw, /usr/ >> local or any other place referenced in your PATH. Just have >> MacPorts, which is usually in /opt/local. It works great by >> itself, but other software installed in other locations can cause >> unpredictable problems. >> > > OSX == 10.4.10, Xcode == 2.4.1 > OK, I've moved everything which was installed (temporarily): > > dhcp-2-178:508:dave>echo $PATH > /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/ > local/bin:/usr/texbin > dhcp-2-178:509:dave>ls /sw > ls: /sw: No such file or directory > dhcp-2-178:510:dave>ls /usr/local/bin > ls: /usr/local/bin: No such file or directory > dhcp-2-178:511:dave>port --version > MacPorts 1.520 > Entering interactive mode... ("help" for help, "quit" to quit) > [Users/dave] > ^D > Goodbye > dhcp-2-178:512:dave>sudo port install tiff > ---> Installing zlib 1.2.3_1 > tclsh(8332) malloc: *** error for object 0x311fc0: double free > tclsh(8332) malloc: *** set a breakpoint in szone_error to debug > tclsh(8332) malloc: *** error for object 0x312020: double free > tclsh(8332) malloc: *** set a breakpoint in szone_error to debug > tclsh(8332) malloc: *** error for object 0x311e20: double free > tclsh(8332) malloc: *** set a breakpoint in szone_error to debug > tclsh(8332) malloc: *** error for object 0x312020: double free > tclsh(8332) malloc: *** set a breakpoint in szone_error to debug > Segmentation fault Don't know what's going on. I agree with Paul -- can we see some debug output please? sudo port clean --work zlib sudo port -dv install zlib Don't forget to Reply To All so that everyone gets the reply, not just me. From D.S.Murray-Rust at sms.ed.ac.uk Mon Oct 1 03:41:04 2007 From: D.S.Murray-Rust at sms.ed.ac.uk (Dave Murray-Rust) Date: Tue Oct 9 16:43:41 2007 Subject: Segfaults when staging into destroot In-Reply-To: <10DA705D-F154-411D-87C9-560BAECC2E6D@macports.org> References: <79A46490-8C98-4760-A75F-D4006EE00153@macports.org> <10DA705D-F154-411D-87C9-560BAECC2E6D@macports.org> Message-ID: On 1 Oct 2007, at 10:51, Ryan Schmidt wrote: > > On Oct 1, 2007, at 04:45, Dave Murray-Rust wrote: > >> On 1 Oct 2007, at 07:28, Ryan Schmidt wrote: >> >>> On Sep 22, 2007, at 13:59, Dave Murray-Rust wrote: >>> >>>> I'm having real hassles with port - most packages fail to >>>> install, with a segfault, e.g.: >>> Make sure you have the latest OS and all updates (10.4.10 or >>> 10.3.9). Make sure you have the latest Xcode (2.4.1 for 10.4.10; >>> 1.5 for 10.3.9). Make sure you have the latest MacPorts (1.5.2). >>> Make sure you do NOT have anything at all installed in /sw, /usr/ >>> local or any other place referenced in your PATH. Just have >>> MacPorts, which is usually in /opt/local. It works great by >>> itself, but other software installed in other locations can cause >>> unpredictable problems. >>> >> >> OSX == 10.4.10, Xcode == 2.4.1 >> OK, I've moved everything which was installed (temporarily): > > Don't know what's going on. I agree with Paul -- can we see some > debug output please? > > sudo port clean --work zlib > sudo port -dv install zlib dhcp-2-178:513:dave>sudo port clean --work zlib Password: ---> Cleaning zlib dhcp-2-178:514:dave>sudo port -dv install zlib DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/archivers/zlib DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/archivers/zlib DEBUG: Requested variant powerpc is not provided by port zlib. DEBUG: Requested variant darwin is not provided by port zlib. DEBUG: Requested variant macosx is not provided by port zlib. DEBUG: Executing org.macports.main (zlib) ---> Fetching zlib DEBUG: Executing org.macports.fetch (zlib) ---> Verifying checksum(s) for zlib DEBUG: Executing org.macports.checksum (zlib) ---> Checksumming zlib-1.2.3.tar.bz2 DEBUG: Correct (md5) checksum for zlib-1.2.3.tar.bz2 DEBUG: Correct (sha1) checksum for zlib-1.2.3.tar.bz2 DEBUG: Correct (rmd160) checksum for zlib-1.2.3.tar.bz2 DEBUG: setting option extract.cmd to /usr/bin/bzip2 ---> Extracting zlib DEBUG: Executing org.macports.extract (zlib) ---> Extracting zlib-1.2.3.tar.bz2 DEBUG: setting option extract.args to /opt/local/var/macports/ distfiles/zlib/zlib-1.2.3.tar.bz2 DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work" && /usr/bin/bzip2 -dc /opt/local/var/macports/distfiles/ zlib/zlib-1.2.3.tar.bz2 | /usr/bin/gnutar --no-same-owner -xf -' DEBUG: Executing org.macports.patch (zlib) ---> Applying patches to zlib ---> Applying /opt/local/var/macports/sources/rsync.macports.org/ release/ports/archivers/zlib/files/patch-Makefile-static DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/zlib-1.2.3" && patch -p0' patching file Makefile.in ---> Configuring zlib DEBUG: Executing org.macports.configure (zlib) DEBUG: No compiler collection selected explicitly DEBUG: Environment: CXXFLAGS='-O2' CPPFLAGS='-I/opt/local/include' CFLAGS='-O2' LDFLAGS='-L/opt/local/lib' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/zlib-1.2.3" && ./configure --prefix=/opt/local --shared' Checking for gcc... Checking for shared library support... Building shared library libz.1.2.3.dylib with gcc. Checking for unistd.h... Yes. Checking whether to use vs[n]printf() or s[n]printf()... using vs[n] printf() Checking for vsnprintf() in stdio.h... Yes. Checking for return value of vsnprintf()... Yes. Checking for errno.h... Yes. Checking for mmap support... Yes. ---> Building zlib with target all DEBUG: Executing org.macports.build (zlib) DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/zlib-1.2.3" && make all' gcc -O2 -DUSE_MMAP -c -o example.o example.c gcc -O2 -DUSE_MMAP -c -o adler32.o adler32.c gcc -O2 -DUSE_MMAP -c -o compress.o compress.c gcc -O2 -DUSE_MMAP -c -o crc32.o crc32.c gcc -O2 -DUSE_MMAP -c -o gzio.o gzio.c gcc -O2 -DUSE_MMAP -c -o uncompr.o uncompr.c gcc -O2 -DUSE_MMAP -c -o deflate.o deflate.c gcc -O2 -DUSE_MMAP -c -o trees.o trees.c gcc -O2 -DUSE_MMAP -c -o zutil.o zutil.c gcc -O2 -DUSE_MMAP -c -o inflate.o inflate.c gcc -O2 -DUSE_MMAP -c -o infback.o infback.c gcc -O2 -DUSE_MMAP -c -o inftrees.o inftrees.c gcc -O2 -DUSE_MMAP -c -o inffast.o inffast.c ar rc libz.a adler32.o compress.o crc32.o gzio.o uncompr.o deflate.o trees.o zutil.o inflate.o infback.o inftrees.o inffast.o gcc -dynamiclib -install_name /opt/local/lib/libz.1.dylib - compatibility_version 1 -current_version 1.2.3 -o libz.1.2.3.dylib adler32.o compress.o crc32.o gzio.o uncompr.o deflate.o trees.o zutil.o inflate.o infback.o inftrees.o inffast.o rm -f libz.dylib libz.1.dylib ln -s libz.1.2.3.dylib libz.dylib ln -s libz.1.2.3.dylib libz.1.dylib gcc -O2 -DUSE_MMAP -o example example.o -L. libz.1.2.3.dylib gcc -O2 -DUSE_MMAP -c -o minigzip.o minigzip.c gcc -O2 -DUSE_MMAP -o minigzip minigzip.o -L. libz.1.2.3.dylib ---> Staging zlib into destroot . changed gid expected 0 found 80 modified permissions expected 0775 found 0755 modified ./usr missing (created) . missing (directory not created: File exists) ./Applications missing (created) ./Developer missing (created) ./Library missing (created) . changed gid expected 80 found 0 modified permissions expected 0775 found 0755 modified ./bin missing (created) ./etc missing (created) ./include missing (created) ./lib missing (created) ./libexec missing (created) ./sbin missing (created) ./share missing (created) ./share/info missing (created) ./share/man missing (created) ./share/man/cat1 missing (created) ./share/man/cat2 missing (created) ./share/man/cat3 missing (created) ./share/man/cat4 missing (created) ./share/man/cat5 missing (created) ./share/man/cat6 missing (created) ./share/man/cat7 missing (created) ./share/man/cat8 missing (created) ./share/man/cat9 missing (created) ./share/man/catl missing (created) ./share/man/catn missing (created) ./share/man/man1 missing (created) ./share/man/man2 missing (created) ./share/man/man3 missing (created) ./share/man/man4 missing (created) ./share/man/man5 missing (created) ./share/man/man6 missing (created) ./share/man/man7 missing (created) ./share/man/man8 missing (created) ./share/man/man9 missing (created) ./share/man/manl missing (created) ./share/man/mann missing (created) ./share/nls missing (created) ./share/nls/C missing (created) ./share/nls/af_ZA.ISO8859-1 missing (created) ./share/nls/af_ZA.ISO8859-15 missing (created) ./share/nls/bg_BG.CP1251 missing (created) ./share/nls/cs_CZ.ISO8859-2 missing (created) ./share/nls/da_DK.ISO8859-1 missing (created) ./share/nls/da_DK.ISO8859-15 missing (created) ./share/nls/de_AT.ISO8859-1 missing (created) ./share/nls/de_AT.ISO8859-15 missing (created) ./share/nls/de_CH.ISO8859-1 missing (created) ./share/nls/de_CH.ISO8859-15 missing (created) ./share/nls/de_DE.ISO8859-1 missing (created) ./share/nls/de_DE.ISO8859-15 missing (created) ./share/nls/el_GR.ISO8859-7 missing (created) ./share/nls/en_AU.ISO8859-1 missing (created) ./share/nls/en_AU.ISO8859-15 missing (created) ./share/nls/en_AU.US-ASCII missing (created) ./share/nls/en_CA.ISO8859-1 missing (created) ./share/nls/en_CA.ISO8859-15 missing (created) ./share/nls/en_CA.US-ASCII missing (created) ./share/nls/en_GB.ISO8859-1 missing (created) ./share/nls/en_GB.ISO8859-15 missing (created) ./share/nls/en_GB.US-ASCII missing (created) ./share/nls/en_NZ.ISO8859-1 missing (created) ./share/nls/en_NZ.ISO8859-15 missing (created) ./share/nls/en_NZ.US-ASCII missing (created) ./share/nls/en_US.ISO8859-1 missing (created) ./share/nls/en_US.ISO8859-15 missing (created) ./share/nls/es_ES.ISO8859-1 missing (created) ./share/nls/es_ES.ISO8859-15 missing (created) ./share/nls/et_EE.ISO8859-15 missing (created) ./share/nls/fi_FI.ISO8859-1 missing (created) ./share/nls/fi_FI.ISO8859-15 missing (created) ./share/nls/fr_BE.ISO8859-1 missing (created) ./share/nls/fr_BE.ISO8859-15 missing (created) ./share/nls/fr_CA.ISO8859-1 missing (created) ./share/nls/fr_CA.ISO8859-15 missing (created) ./share/nls/fr_CH.ISO8859-1 missing (created) ./share/nls/fr_CH.ISO8859-15 missing (created) ./share/nls/fr_FR.ISO8859-1 missing (created) ./share/nls/fr_FR.ISO8859-15 missing (created) ./share/nls/hi_IN.ISCII-DEV missing (created) ./share/nls/hr_HR.ISO8859-2 missing (created) ./share/nls/hu_HU.ISO8859-2 missing (created) ./share/nls/is_IS.ISO8859-1 missing (created) ./share/nls/is_IS.ISO8859-15 missing (created) ./share/nls/it_CH.ISO8859-1 missing (created) ./share/nls/it_CH.ISO8859-15 missing (created) ./share/nls/it_IT.ISO8859-1 missing (created) ./share/nls/it_IT.ISO8859-15 missing (created) ./share/nls/ja_JP.SJIS missing (created) ./share/nls/ja_JP.eucJP missing (created) ./share/nls/ko_KR.eucKR missing (created) ./share/nls/la_LN.ISO8859-1 missing (created) ./share/nls/la_LN.ISO8859-15 missing (created) ./share/nls/la_LN.ISO8859-2 missing (created) ./share/nls/la_LN.ISO8859-4 missing (created) ./share/nls/la_LN.US-ASCII missing (created) ./share/nls/lt_LT.ISO8859-4 missing (created) ./share/nls/nl_BE.ISO8859-1 missing (created) ./share/nls/nl_BE.ISO8859-15 missing (created) ./share/nls/nl_NL.ISO8859-1 missing (created) ./share/nls/nl_NL.ISO8859-15 missing (created) ./share/nls/no_NO.ISO8859-1 missing (created) ./share/nls/no_NO.ISO8859-15 missing (created) ./share/nls/pl_PL.ISO8859-2 missing (created) ./share/nls/pt_BR.ISO8859-1 missing (created) ./share/nls/pt_PT.ISO8859-1 missing (created) ./share/nls/pt_PT.ISO8859-15 missing (created) ./share/nls/ro_RO.ISO8859-2 missing (created) ./share/nls/ru_RU.CP866 missing (created) ./share/nls/ru_RU.ISO8859-5 missing (created) ./share/nls/ru_RU.KOI8-R missing (created) ./share/nls/sk_SK.ISO8859-2 missing (created) ./share/nls/sl_SI.ISO8859-2 missing (created) ./share/nls/sv_SE.ISO8859-1 missing (created) ./share/nls/sv_SE.ISO8859-15 missing (created) ./share/nls/tr_TR.ISO8859-9 missing (created) ./share/nls/uk_UA.ISO8859-5 missing (created) ./share/nls/uk_UA.KOI8-U missing (created) ./share/nls/zh_CN.eucCN missing (created) ./share/nls/zh_TW.Big5 missing (created) ./share/skel missing (created) ./src missing (created) ./var missing (created) ./var/macports missing (created) ./var/macports/distfiles missing (created) ./var/macports/receipts missing (created) ./www missing (created) DEBUG: Executing org.macports.destroot (zlib) DEBUG: Environment: DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/zlib-1.2.3" && make install prefix=/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local' cp zlib.h zconf.h /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/include chmod 644 /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/include/zlib.h /opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/include/zconf.h cp libz.1.2.3.dylib /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/lib cp libz.a /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/lib cd /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/lib; chmod 755 libz.1.2.3.dylib cd /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/lib; if test -f libz.1.2.3.dylib; then \ rm -f libz.dylib libz.1.dylib; \ ln -s libz.1.2.3.dylib libz.dylib; \ ln -s libz.1.2.3.dylib libz.1.dylib; \ (ldconfig || true) >/dev/null 2>&1; \ fi cp zlib.3 /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/share/man/man3 chmod 644 /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/share/man/man3/zlib.3 DEBUG: Executing proc-post-org.macports.destroot-destroot-0 xinstall: mkdir /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/share/doc xinstall: mkdir /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/share/doc/zlib-1.2.3 xinstall: chdir(/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/zlib-1.2.3) xinstall: ChangeLog -> /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/share/doc/zlib-1.2.3/ChangeLog tclsh(8352) malloc: *** error for object 0x313390: double free tclsh(8352) malloc: *** set a breakpoint in szone_error to debug xinstall: FAQ -> /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_archive rs_zlib/work/destroot/opt/local/share/doc/zlib-1.2.3/FAQ Segmentation fault From bruda at cs.ubishops.ca Mon Oct 1 05:40:37 2007 From: bruda at cs.ubishops.ca (Stefan Bruda) Date: Tue Oct 9 16:43:41 2007 Subject: poppler and xpdf Message-ID: <18176.60101.66461.585221@gargle.gargle.HOWL> Hi, Poppler and xpdf conflict with each other in some executable names. < godel:~ > port activate poppler @0.6_0 ---> Activating poppler 0.6_0 Error: port activate failed: Image error: /opt/local/bin/pdffonts is being used by the active xpdf port. Please deactivate this port first, or use the -f flag to force the activation. However, evince and gimp2 depend on poppler (so it needs to be there) and I use xpdf all the time (so I need it). How does one get around this problem? Many thanks in advance, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass From yves at macports.org Mon Oct 1 08:56:32 2007 From: yves at macports.org (Yves de Champlain) Date: Tue Oct 9 16:43:41 2007 Subject: poppler and xpdf In-Reply-To: <18176.60101.66461.585221@gargle.gargle.HOWL> References: <18176.60101.66461.585221@gargle.gargle.HOWL> Message-ID: Le 07-10-01 ? 08:40, Stefan Bruda a ?crit : > Hi, > > Poppler and xpdf conflict with each other in some executable names. > > < godel:~ > port activate poppler @0.6_0 > ---> Activating poppler 0.6_0 > Error: port activate failed: Image error: /opt/local/bin/pdffonts > is being used by the active xpdf port. Please deactivate this > port first, or use the -f flag to force the activation. > > However, evince and gimp2 depend on poppler (so it needs to be there) > and I use xpdf all the time (so I need it). How does one get around > this problem? xpdf has a variant for this case port install xpdf +with_poppler yves From bruda at cs.ubishops.ca Mon Oct 1 09:46:40 2007 From: bruda at cs.ubishops.ca (Stefan Bruda) Date: Tue Oct 9 16:43:41 2007 Subject: poppler and xpdf In-Reply-To: References: <18176.60101.66461.585221@gargle.gargle.HOWL> Message-ID: <52347.206.167.192.34.1191257200.squirrel@turing.ubishops.ca> Yves de Champlain wrote: > >> Poppler and xpdf conflict with each other in some executable names. >> >> < godel:~ > port activate poppler @0.6_0 >> ---> Activating poppler 0.6_0 >> Error: port activate failed: Image error: /opt/local/bin/pdffonts >> is being used by the active xpdf port. Please deactivate this >> port first, or use the -f flag to force the activation. >> >> However, evince and gimp2 depend on poppler (so it needs to be there) >> and I use xpdf all the time (so I need it). How does one get around >> this problem? > > xpdf has a variant for this case > > port install xpdf +with_poppler Thank you very much, that does it nicely. Stefan From paulbeard at gmail.com Mon Oct 1 10:57:17 2007 From: paulbeard at gmail.com (paul beard) Date: Tue Oct 9 16:43:41 2007 Subject: MySQL5, OS X 10.4.10, startups, etc. In-Reply-To: References: <31A8D5F4-32F0-4EB1-97CA-8B1AACA1762A@centosprime.com> Message-ID: On 9/30/07, Ryan Schmidt wrote: > > > Feel free to make a proposal to the macports-dev list if you feel > strongly about this. The current approach works, so you should > explain why your approach is better (and if there are any reasons why > it might be worse). I don't know that I feel strongly about it. I think it preserves the integrity of the host file system by editing an existing file rather than writing files to places outside of /opt/local. I realize that rule is bent and in some cases broken[*] but I think adhering to the infrastructure where possible makes sense. Adding and removing those startup items is centralized in the one file that is easily found, rather than looking in the active system hierarchy and risking mucking something up (imagine the consequence of a poorly-formed rm command in /Library/LaunchDaemons?) * see /Library/Tcl/macports-1.0/ -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20071001/9075a223/attachment.html From ryandesign at macports.org Mon Oct 1 14:20:20 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: MySQL5, OS X 10.4.10, startups, etc. In-Reply-To: <9B700D0A-D912-4DDE-8186-54F3DA4BBD0D@CentosPrime.COM> References: <31A8D5F4-32F0-4EB1-97CA-8B1AACA1762A@centosprime.com> <08D1D069-8554-44B0-AEE4-69F29F783716@macports.org> <9B700D0A-D912-4DDE-8186-54F3DA4BBD0D@CentosPrime.COM> Message-ID: <12BA87B6-F42E-4846-A1BB-B702923B00F5@macports.org> On Oct 1, 2007, at 08:39, Chris Janton wrote: > On 2007-09-30 , at 23:41 , Ryan Schmidt wrote: > >> That's odd. I only get the message "nothing found to load" when a >> plist file does not exist. Does it exist? Here's how it is on my >> system: >> >> $ ls -l /Library/LaunchDaemons/org.macports.mysql5.plist >> lrwxr-xr-x 1 root wheel 74 Sep 10 21:49 /Library/LaunchDaemons/ >> org.macports.mysql5.plist -> /opt/local/etc/LaunchDaemons/ >> org.macports.mysql5/org.macports.mysql5.plist >> >> $ ls -l /opt/local/etc/LaunchDaemons/org.macports.mysql5/ >> org.macports.mysql5.plist >> -rw-r--r-- 2 root wheel 981 Oct 1 01:29 /opt/local/etc/ >> LaunchDaemons/org.macports.mysql5/org.macports.mysql5.plist >> >> If you do not have these items, what does "port contents mysql5" >> tell you? Is the plist shown there? >> >> $ port contents mysql5 | grep plist >> /Library/LaunchDaemons/org.macports.mysql5.plist >> /opt/local/etc/LaunchDaemons/org.macports.mysql5/ >> org.macports.mysql5.plist >> >> Do you have the latest MacPorts and port definitions? "sudo port >> selfupdate" > > The symbolic link to the .plist file was missing from /Library/ > LaunchDaemons > I created the symbolic link by hand. Now things are working as > expected. > > mac 2 # sudo port selfupdate > MacPorts base version 1.520 installed > Downloaded MacPorts base version 1.520 > The MacPorts installation is not outdated and so was not updated > selfupdate done! > mac 3 # sudo port sync > mac 4 # sudo port outdated > No installed ports are outdated. I wonder why the symlink isn't there. Is it listed in the port's contents? (port contents mysql5) By the way, "selfupdate" already includes "sync" so you do not need to "sync" manually if you already used "selfupdate". Please remember to Reply To All so that your response goes to the list too, not just to me. From ryandesign at macports.org Mon Oct 1 14:40:10 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: MySQL5, OS X 10.4.10, startups, etc. In-Reply-To: References: <31A8D5F4-32F0-4EB1-97CA-8B1AACA1762A@centosprime.com> Message-ID: On Oct 1, 2007, at 12:57, paul beard wrote: > On 9/30/07, Ryan Schmidt wrote: > >> On Sep 30, 2007, at 12:18, paul beard wrote: >> >>> Conversely, you can add the appropriate lines to launchd.conf and >>> get things going. >>> >>> more /etc/launchd.conf >>> launchctl load /opt/local/etc/LaunchDaemons/org.macports.dbus/ >>> org.macports.dbus.p >>> list >>> launchctl load /opt/local/etc/LaunchDaemons/org.macports.apache2/ >>> org.macports.apa >>> che2.plist >>> launchctl load /opt/local/etc/LaunchDaemons/org.macports.mysql5/ >>> org.macports.mysq >>> l5.plist >>> >>> I would vote for MacPorts to take the latter approach, with the >>> post-install message explaining that >>> >>> ######## >>> ## To get the application to run at boot time, >>> ## echo launchctl load /opt/local/etc/LaunchDaemons/ >>> org.macports.mysql5/org.macports.mysql5.plist >> /etc/launchd.conf >>> ## >>> ########## >> >> Feel free to make a proposal to the macports-dev list if you feel >> strongly about this. The current approach works, so you should >> explain why your approach is better (and if there are any reasons why >> it might be worse). > > I don't know that I feel strongly about it. I think it preserves > the integrity of the host file system by editing an existing file > rather than writing files to places outside of /opt/local. I > realize that rule is bent and in some cases broken[*] but I think > adhering to the infrastructure where possible makes sense. Adding > and removing those startup items is centralized in the one file > that is easily found, rather than looking in the active system > hierarchy and risking mucking something up (imagine the consequence > of a poorly-formed rm command in /Library/LaunchDaemons?) > > * see /Library/Tcl/macports-1.0/ In the current way, the symlink is made in the destroot and handled just like any other file in the port's manifest. On activate, it is installed to the right place. On deactivate, it is removed. To start the service, you "launchctl load" it and to stop it, you "launchctl unload" it. This is all fairly easy and works. Your way would require someone to manually edit the file /etc/ launchd.conf, at least to remove a line from it. That's more complicated than the current way, where a single launchctl line starts or stops the service. Also, with your way, the service wouldn't start or stop until the next startup. That's worse than what we have now, where the service starts or stops immediately. Running a single launchctl command to start or stop a service is easy. Conversely, adding a line to a file is easy, as you showed, but removing a line from a file requires a more elaborate script. So why change it to make it more difficult? There's a slight problem with the current way. If the service is running at the time that you uninstall the port, the software stays running. And if the service is running at the time that you upgrade the port, the old version stays running and the new version's plist says the software isn't running and it's inconvenient to fix that (manually edit the plist to show that the software is running, launchctl unload the software, launchctl load it again). Would your new way solve either of these problems? (I haven't tried so I don't know.) From joe.uelk at gmail.com Mon Oct 1 14:57:11 2007 From: joe.uelk at gmail.com (Joe) Date: Tue Oct 9 16:43:41 2007 Subject: ffmpeg - unable to install Message-ID: <9d6632e0710011457j5a3ae14ai272a096fe004d848@mail.gmail.com> Hello all, I can't get ffmpeg to install. Has anyone else had a similar problem? See below. Thanks! sudo port install ffmpeg ---> Fetching ffmpeg ---> Verifying checksum(s) for ffmpeg ---> Extracting ffmpeg ---> Configuring ffmpeg ---> Building ffmpeg 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_multimedia_ffmpeg/work/trunk" && make all " returned error 2 Command output: gcc -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign-compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign -O3 -c -o i386/motion_est_mmx.o i386/motion_est_mmx.c In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/dsputil.h:33, from i386/motion_est_mmx.c:24: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: 'ImgReSampleContext' is deprecated /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: 'ImgReSampleContext' is deprecated gcc -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign-compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign -O3 -c -o i386/simple_idct_mmx.o i386/simple_idct_mmx.c In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/dsputil.h:33, from i386/simple_idct_mmx.c:22: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: 'ImgReSampleContext' is deprecated /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: 'ImgReSampleContext' is deprecated gcc -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign-compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign -O3 -c -o i386/idct_mmx_xvid.o i386/idct_mmx_xvid.c In file included from i386/idct_mmx_xvid.c:53: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: 'ImgReSampleContext' is deprecated /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: 'ImgReSampleContext' is deprecated gcc -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign-compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign -O3 -c -o i386/fft_sse.o i386/fft_sse.c In file included from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/dsputil.h:33, from i386/fft_sse.c:21: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: 'ImgReSampleContext' is deprecated /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: 'ImgReSampleContext' is deprecated {standard input}:259:Missing operand value assumed absolute 0. {standard input}:260:Missing operand value assumed absolute 0. {standard input}:263:Missing operand value assumed absolute 0. {standard input}:264:Missing operand value assumed absolute 0. {standard input}:431:Missing operand value assumed absolute 0. {standard input}:433:Missing operand value assumed absolute 0. {standard input}:437:Missing operand value assumed absolute 0. {standard input}:457:Missing operand value assumed absolute 0. make[1]: *** [i386/fft_sse.o] Error 1 make: *** [lib] Error 2 rm doc/ffserver.pod doc/ffmpeg.pod doc/ffplay.pod -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20071001/510d4c59/attachment.html From paulbeard at gmail.com Mon Oct 1 15:52:46 2007 From: paulbeard at gmail.com (paul beard) Date: Tue Oct 9 16:43:41 2007 Subject: MySQL5, OS X 10.4.10, startups, etc. In-Reply-To: References: <31A8D5F4-32F0-4EB1-97CA-8B1AACA1762A@centosprime.com> Message-ID: On 10/1/07, Ryan Schmidt wrote: > > > In the current way, the symlink is made in the destroot and handled > just like any other file in the port's manifest. On activate, it is > installed to the right place. On deactivate, it is removed. To start > the service, you "launchctl load" it and to stop it, you "launchctl > unload" it. This is all fairly easy and works. This assumes that people deactivate or otherwise that allow MacPorts to clean up after itself. rm -rf /opt/local would leave those broken symlinks. They don't really matter but as I said earlier, the "nothing outside /opt/local" rule is bent in some cases, this being one. And as for invoking launchct load statements, how is this different? launchctl load /opt/local/etc/LaunchDaemons/org.macports.dbus/org.macports.dbus.plist launchctl load /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist launchctl load /opt/local/etc/LaunchDaemons/org.macports.mysql5/org.macports.mysql5.plist from putting the plists in launchd's default search path? As configured, launchctl looks in two places for plists: in /System/Library/LaunchDaemons, for Apple-owned stuff, in /Library/LaunchDaemons for user-installed/third-party stuff. I don't see a big deal about another repository for plists. Maybe in future releases launchd will allow additional directories to be added instead of individual lines. Your way would require someone to manually edit the file /etc/ > launchd.conf, at least to remove a line from it. That's more > complicated than the current way, where a single launchctl line > starts or stops the service. Also, with your way, the service > wouldn't start or stop until the next startup. That's worse than what > we have now, where the service starts or stops immediately. see above: if launchctl works as it says on the tin, there is not different between symlinks that point to /Library/LaunchDaemons and the lines I have in /etc/launchd.conf. Running a single launchctl command to start or stop a service is > easy. Conversely, adding a line to a file is easy, as you showed, but > removing a line from a file requires a more elaborate script. So why > change it to make it more difficult? I'm not arguing in favor of it. I'm just explaining it. I have a hard time believing that, given the power on tap, that there is no way to add a commented line to /etc/launchd.conf launchctl load /opt/local/etc/LaunchDaemons/org.macports.dbus/org.macports.dbus.plist # installed by macports and add a # character to the beginning of the line containing the comment: sed -e s/^launchctl/#&/g <- yes, I know that won't work, but you get the idea: sed is not my native language. There's a slight problem with the current way. If the service is > running at the time that you uninstall the port, the software stays > running. And if the service is running at the time that you upgrade > the port, the old version stays running and the new version's plist > says the software isn't running and it's inconvenient to fix that > (manually edit the plist to show that the software is running, > launchctl unload the software, launchctl load it again). Would your > new way solve either of these problems? (I haven't tried so I don't > know.) Is there no pre-install step that could stop the service with the existing plist, install, restart? Again, I'm not arguing in favor of doing it this way, I'm just explaining it. Perhaps if it's more clearly understood, a comparison can be made. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20071001/6fedd1fd/attachment.html From ryandesign at macports.org Mon Oct 1 16:14:27 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: ffmpeg - unable to install In-Reply-To: <9d6632e0710011457j5a3ae14ai272a096fe004d848@mail.gmail.com> References: <9d6632e0710011457j5a3ae14ai272a096fe004d848@mail.gmail.com> Message-ID: <05D51E30-6997-4448-9EE9-5D8F5270F9E7@macports.org> On Oct 1, 2007, at 16:57, Joe wrote: > I can't get ffmpeg to install. Has anyone else had a similar > problem? See below. I see this message with that error (but no response): http://lists.mplayerhq.hu/pipermail/ffmpeg-user/2007-July/010101.html I also see this MacPorts bug filed (but no resolution): http://trac.macports.org/projects/macports/ticket/12191 It works fine for me on Mac OS X 10.4.10, Xcode 2.4.1, MacPorts 1.5.2: $ sudo port install ffmpeg Password: ---> Fetching ffmpeg ---> Verifying checksum(s) for ffmpeg ---> Extracting ffmpeg ---> Configuring ffmpeg ---> Building ffmpeg with target all ---> Staging ffmpeg into destroot ---> Installing ffmpeg 0.4.9-pre1_2 ---> Activating ffmpeg 0.4.9-pre1_2 ---> Cleaning ffmpeg $ Perhaps you can provide more information about your setup. > sudo port install ffmpeg > ---> Fetching ffmpeg > ---> Verifying checksum(s) for ffmpeg > ---> Extracting ffmpeg > ---> Configuring ffmpeg > ---> Building ffmpeg 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_multi > media_ffmpeg/work/trunk" && make all " returned error 2 > Command output: gcc -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H - > D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/ > include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign- > compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall > -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant- > decls -Wno-pointer-sign -O3 -c -o i386/motion_est_mmx.o i386/ > motion_est_mmx.c > In file included from /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/dsputil.h:33, > from i386/motion_est_mmx.c:24: > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: > 'ImgReSampleContext' is deprecated > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: > 'ImgReSampleContext' is deprecated > gcc -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H - > D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/ > include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign- > compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall > -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant- > decls -Wno-pointer-sign -O3 -c -o i386/simple_idct_mmx.o i386/ > simple_idct_mmx.c > In file included from /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/dsputil.h:33, > from i386/simple_idct_mmx.c:22: > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: > 'ImgReSampleContext' is deprecated > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: > 'ImgReSampleContext' is deprecated > gcc -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H - > D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/ > include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign- > compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall > -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant- > decls -Wno-pointer-sign -O3 -c -o i386/idct_mmx_xvid.o i386/ > idct_mmx_xvid.c > In file included from i386/idct_mmx_xvid.c:53: > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: > 'ImgReSampleContext' is deprecated > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: > 'ImgReSampleContext' is deprecated > gcc -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H - > D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/ > include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign- > compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall > -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant- > decls -Wno-pointer-sign -O3 -c -o i386/fft_sse.o i386/fft_sse.c > In file included from /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/dsputil.h:33, > from i386/fft_sse.c:21: > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: > 'ImgReSampleContext' is deprecated > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: > 'ImgReSampleContext' is deprecated > {standard input}:259:Missing operand value assumed absolute 0. > {standard input}:260:Missing operand value assumed absolute 0. > {standard input}:263:Missing operand value assumed absolute 0. > {standard input}:264:Missing operand value assumed absolute 0. > {standard input}:431:Missing operand value assumed absolute 0. > {standard input}:433:Missing operand value assumed absolute 0. > {standard input}:437:Missing operand value assumed absolute 0. > {standard input}:457:Missing operand value assumed absolute 0. > make[1]: *** [i386/fft_sse.o] Error 1 > make: *** [lib] Error 2 > rm doc/ffserver.pod doc/ffmpeg.pod doc/ffplay.pod From paulbeard at gmail.com Mon Oct 1 16:23:21 2007 From: paulbeard at gmail.com (paul beard) Date: Tue Oct 9 16:43:41 2007 Subject: how to mark a port as installed In-Reply-To: <4CEBD848-130B-42E4-A127-A458A9D6CC7A@macports.org> References: <4CEBD848-130B-42E4-A127-A458A9D6CC7A@macports.org> Message-ID: On 9/30/07, Ryan Schmidt wrote: > > > On Sep 30, 2007, at 19:40, Aaron Voisine wrote: > > > Is there any good way to mark a port as already having been installed > > if you've built and installed it manually? I don't want the version I > > built with special configure options to get overwritten when I install > > another port that depends on it. > > By design, MacPorts only depends on other software installed using > MacPorts, and not on any software you've installed manually. > > http://trac.macosforge.org/projects/macports/wiki/ > FAQ#WhyisMacPortsusingitsownlibraries > > If you need options for a software package that are not in the > MacPorts port for that software, perhaps the options can be added to > the port. Consult the port maintainer, or if there is none, this list. > A specific example would have been helpful but it sounds like the need is for something MacPorts would install as a dependency and overwrite the OP's hand-crafted configuration. I guess one option would be to let MacPorts install it, backup the installation receipt, remove it, install the custom version, and put the receipt back in place. MacPorts thinks the dependency is satisfied and barring upgrades, all is well. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20071001/1ea256e9/attachment.html From jberry at macports.org Mon Oct 1 17:12:09 2007 From: jberry at macports.org (James Berry) Date: Tue Oct 9 16:43:41 2007 Subject: Heads up: MacOSForge machine reorganizations Message-ID: <4B29E0CD-5F93-476E-95E6-B094F2E280EF@macports.org> This is just a general heads up that the wonderful folks at macosforge are doing some machine migrations (more power for the masses...) in the coming days and weeks. They, and we, will try to minimize any service interruptions for MacPorts, but please be aware that this is afoot, and that there may be some temporary interrupts to mail, web, trac, svn, etc... If critical services are down, and you're not sure what's going on, you might try our irc channel, where up to date information (or perhaps flat-out speculation) will be available ;) James From gelfmuse at gmail.com Mon Oct 1 17:35:27 2007 From: gelfmuse at gmail.com (mike clemow) Date: Tue Oct 9 16:43:41 2007 Subject: Problems installing Oregano. Message-ID: Hello, I'm new to macports from Debian. I'm trying to install oregano, and all the dependencies have downloaded and installed, but when port gets the oregano source, this happens: ------------ ---> Fetching oregano ---> oregano-0.3.2.tar.bz2 doesn't seem to exist in /opt/local/var/macports/distfiles/oregano ---> Attempting to fetch oregano-0.3.2.tar.bz2 from http://opendarwin.org/~olegb/ ---> Attempting to fetch oregano-0.3.2.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/oregano % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 ---> Attempting to fetch oregano-0.3.2.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/general/ % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 ---> Attempting to fetch oregano-0.3.2.tar.bz2 from http://svn.macports.org/repository/macports/downloads/oregano - Ignored: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 Error: Target org.macports.fetch returned: fetch failed Warning: the following items did not execute (for oregano): org.macports.activate org.macports.fetch org.macports.extract org.macports.checksum org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. ------------- What exactly does this mean? Does this mean that the file just isn't there? Or should I be asking this on another list? Any help would be great. Cheers, Mike From ryandesign at macports.org Mon Oct 1 18:01:05 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: Problems installing Oregano. In-Reply-To: References: Message-ID: <25554896-3AAF-4356-B069-7658D2C8F783@macports.org> On Oct 1, 2007, at 19:35, mike clemow wrote: > I'm new to macports from Debian. I'm trying to install oregano, and > all the dependencies have downloaded and installed, but when > port gets > the oregano source, this happens: > ------------ > ---> Fetching oregano > ---> oregano-0.3.2.tar.bz2 doesn't seem to exist in > /opt/local/var/macports/distfiles/oregano > ---> Attempting to fetch oregano-0.3.2.tar.bz2 from > http://opendarwin.org/~olegb/ > ---> Attempting to fetch oregano-0.3.2.tar.bz2 from > http://svn.macports.org/repository/macports/distfiles/oregano > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total > Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > --:--:-- 0 > ---> Attempting to fetch oregano-0.3.2.tar.bz2 from > http://svn.macports.org/repository/macports/distfiles/general/ > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total > Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > --:--:-- 0 > ---> Attempting to fetch oregano-0.3.2.tar.bz2 from > http://svn.macports.org/repository/macports/downloads/oregano > > - Ignored: > % Total % Received % Xferd Average Speed Time Time > Time Current > Dload Upload Total > Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > --:--:-- 0 > Error: Target org.macports.fetch returned: fetch failed > Warning: the following items did not execute (for oregano): > org.macports.activate org.macports.fetch org.macports.extract > org.macports.checksum org.macports.patch org.macports.configure > org.macports.build org.macports.destroot org.macports.install > Error: Status 1 encountered during processing. > ------------- > > What exactly does this mean? Does this mean that the file just > isn't > there? Or should I be asking this on another list? This is the right list. I see the oregano port still tries to fetch from opendarwin. opendarwin died quite awhile ago. Also it looks like the port hasn't been substantially updated since being initially added on 2004-11-16. The port is for oregano 0.3.2 but the current version is 0.69.0. It looks like maybe the reason the distfile was stored on opendarwin is that the project does not release source tarballs; currently they tell you to pull the source via darcs. Someone who knows about this software should fetch the 0.69.0 source, put the tarball up in the macports repository, and update the port to 0.69.0. Probably best to just totally rewrite the portfile. From ryandesign at macports.org Mon Oct 1 18:22:50 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: MySQL5, OS X 10.4.10, startups, etc. In-Reply-To: References: <31A8D5F4-32F0-4EB1-97CA-8B1AACA1762A@centosprime.com> Message-ID: <614AE1EC-2C14-42FC-A641-2A063BBA2E0C@macports.org> On Oct 1, 2007, at 17:52, paul beard wrote: > On 10/1/07, Ryan Schmidt wrote: > >> In the current way, the symlink is made in the destroot and handled >> just like any other file in the port's manifest. On activate, it is >> installed to the right place. On deactivate, it is removed. To start >> the service, you "launchctl load" it and to stop it, you "launchctl >> unload" it. This is all fairly easy and works. > > This assumes that people deactivate or otherwise that allow > MacPorts to clean up after itself. rm -rf /opt/local would leave > those broken symlinks. They don't really matter but as I said > earlier, the "nothing outside /opt/local" rule is bent in some > cases, this being one. Yes, we do want MacPorts to install as much as possible inside $ {prefix}. But currently some things do get installed outside of the prefix. But IMHO the current uninstall instructions adequately address this issue. BTW, "rm -rf /opt/local" is not the extent of the uninstall instructions: http://trac.macosforge.org/projects/macports/wiki/ FAQ#HowdoIremoveoruninstallMacPorts > And as for invoking launchct load statements, how is this different? > > launchctl load /opt/local/etc/LaunchDaemons/org.macports.dbus/ > org.macports.dbus.plist > launchctl load /opt/local/etc/LaunchDaemons/org.macports.apache2/ > org.macports.apache2.plist > launchctl load /opt/local/etc/LaunchDaemons/org.macports.mysql5/ > org.macports.mysql5.plist > > from putting the plists in launchd's default search path? As > configured, launchctl looks in two places for plists: in /System/ > Library/LaunchDaemons, for Apple-owned stuff, in /Library/ > LaunchDaemons for user-installed/third-party stuff. I don't see a > big deal about another repository for plists. Maybe in future > releases launchd will allow additional directories to be added > instead of individual lines. > >> Your way would require someone to manually edit the file /etc/ >> launchd.conf, at least to remove a line from it. That's more >> complicated than the current way, where a single launchctl line >> starts or stops the service. Also, with your way, the service >> wouldn't start or stop until the next startup. That's worse than what >> we have now, where the service starts or stops immediately. > > see above: if launchctl works as it says on the tin, there is not > different between symlinks that point to /Library/LaunchDaemons and > the lines I have in /etc/launchd.conf. Wait. Currently, MacPorts automatically puts the symlinks in /Library/ LaunchDaemons, then instructs you how to load (start) and unload (stop) as needed. Your proposition as I understood it was that the user would manually add and remove lines in /etc/launchd.conf. Are you now suggesting instead that MacPorts would automatically put the lines in /etc/launchd.conf? If so, why is that preferable to the current way? Currently, we add symlinks in /Library/LaunchDaemons, which is outside of ${prefix}. You propose modifying /etc/ launchd.conf, which is also outside of ${prefix}. At least the symlinks in /Library/LaunchDaemons have "macports" in the filenames so they're easier to find, and getting rid of them is as simple as a single "rm" command. Getting rid of a line in a conf file is more involved. Also, since I'm not familiar with /etc/launchd.conf, I assume that the file is only scanned at system startup. Is that the case? If so, then adding to that file is worse than what we have now, where "launchctl load" will load the service immediately, and cause it to start at every subsequent system startup. Unless you're suggesting that the user should modify /etc/launchd.conf, and then also use the launchctl command to start the service now. If so, you've just added an extra step for the user, again for no apparent benefit. >> Running a single launchctl command to start or stop a service is >> easy. Conversely, adding a line to a file is easy, as you showed, but >> removing a line from a file requires a more elaborate script. So why >> change it to make it more difficult? > > I'm not arguing in favor of it. I'm just explaining it. I have a > hard time believing that, given the power on tap, that there is no > way to add a commented line to /etc/launchd.conf > > launchctl load /opt/local/etc/LaunchDaemons/org.macports.dbus/ > org.macports.dbus.plist # installed by macports > > > and add a # character to the beginning of the line containing the > comment: > > sed -e s/^launchctl/#&/g <- yes, I know that won't work, but you > get the idea: sed is not my native language. Yes, of course it's possible to write something with sed or similar that adds or removes a specific line from a file. My point is that it's more difficult than executing a single launchctl statement. And since the current way works, I didn't understand why you think it's better to complicate things. >> There's a slight problem with the current way. If the service is >> running at the time that you uninstall the port, the software stays >> running. And if the service is running at the time that you upgrade >> the port, the old version stays running and the new version's plist >> says the software isn't running and it's inconvenient to fix that >> (manually edit the plist to show that the software is running, >> launchctl unload the software, launchctl load it again). Would your >> new way solve either of these problems? (I haven't tried so I don't >> know.) > > Is there no pre-install step that could stop the service with the > existing plist, install, restart? I don't think MacPorts should be stopping or starting any services automatically. That could be unexpected and bad. I've been meaning to submit bug reports about these situations but hadn't gotten around to it yet. > Again, I'm not arguing in favor of doing it this way, I'm just > explaining it. Perhaps if it's more clearly understood, a > comparison can be made. Ok. Then I'll say that I acknowledge that MacPorts could do it your way instead of how it does it now, but I don't see any advantage to making that change at this point, rather I currently see disadvantages, so I don't think MacPorts should change this right now, until someone shows why it's better. From d.l.tDeContes at free.fr Mon Oct 1 18:26:04 2007 From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=) Date: Tue Oct 9 16:43:41 2007 Subject: problem when installing macports In-Reply-To: <0D85D1B8-6AB8-4CC8-9733-49C372783206@macports.org> References: <588e6e973aecd31994d173f9afad2d26@macports.org> <0D85D1B8-6AB8-4CC8-9733-49C372783206@macports.org> Message-ID: <3ED684B6-5AA9-4E95-82C1-C98A782E74BA@free.fr> Le 21 sept. 07 ? 20:05, Ryan Schmidt a ?crit : > > On Sep 20, 2007, at 05:02, Anders F Bj?rklund wrote: > >> Thomas De Contes wrote: >> >>> on both, i have installed the last version of xcode (2.4.1), but >>> only devtools software, gcc 3.3, and software dev kits >>> oh yes, i just remember, on the computer where it works, i have >>> installed gcc 4.0 instead of gcc 3.3 >>> so, is it required to have gcc 4.0 to compile macports ?? why ? >> >> You need the Universal system compiler (gcc-4.0) for Mac OS X >> 10.4 / Xcode, >> not the gcc-3.3 cross-compiler - that's only for building for Mac >> OS X 10.3 >> >> Trying to reproduce the issue with CC="gcc-3.3 -arch ppc" >> LDFLAGS="-arch ppc", >> but that seemed to have work... (i.e. it didn't give any snprintf >> errors) > > Anders, he didn't say what OS version he was using. Also, he's on > G4, so gcc 3.3 is a native compiler, not a cross-compiler. > > But, Thomas, if you're running Mac OS X 10.3.9, then you need Xcode > 1.5, which installs gcc 3.3 and that's supposed to be fine for > MacPorts. If you're on Mac OS X 10.4.10, then you need Xcode 2.4.1 > which installs gcc 4.0, and your gcc_select should be set to use > gcc 4.0, which is the default. Using gcc 3.3 as your system > compiler on Mac OS X 10.4 is not supported by MacPorts, and I don't > recommend it for any reason. thank you very much for all the details :-) i have 10.4, two remote computers with ppc, and my local computer with intel but, if on 10.4 the "core" is gcc 4.0, why is there "This package contains the Apple version of the gcc 4.0 compiler." and "This package contains the Apple version of the gcc 3.3 compiler, and is required to use the Developer Tools on Mac OS X." even on intel, which let us suppose that the "core" is gcc 3.3 ? -- j'agis contre l'assistanat, je travaille dans une SCOP ! From ryandesign at macports.org Mon Oct 1 18:54:28 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: problem when installing macports In-Reply-To: <3ED684B6-5AA9-4E95-82C1-C98A782E74BA@free.fr> References: <588e6e973aecd31994d173f9afad2d26@macports.org> <0D85D1B8-6AB8-4CC8-9733-49C372783206@macports.org> <3ED684B6-5AA9-4E95-82C1-C98A782E74BA@free.fr> Message-ID: <81C36CC5-9F1A-448D-9C73-E105486A039E@macports.org> On Oct 1, 2007, at 20:26, Thomas De Contes wrote: > Le 21 sept. 07 ? 20:05, Ryan Schmidt a ?crit : > >> On Sep 20, 2007, at 05:02, Anders F Bj?rklund wrote: >> >>> Thomas De Contes wrote: >>> >>>> on both, i have installed the last version of xcode (2.4.1), but >>>> only devtools software, gcc 3.3, and software dev kits >>>> oh yes, i just remember, on the computer where it works, i have >>>> installed gcc 4.0 instead of gcc 3.3 >>>> so, is it required to have gcc 4.0 to compile macports ?? why ? >>> >>> You need the Universal system compiler (gcc-4.0) for Mac OS X >>> 10.4 / Xcode, >>> not the gcc-3.3 cross-compiler - that's only for building for Mac >>> OS X 10.3 >>> >>> Trying to reproduce the issue with CC="gcc-3.3 -arch ppc" >>> LDFLAGS="-arch ppc", >>> but that seemed to have work... (i.e. it didn't give any snprintf >>> errors) >> >> Anders, he didn't say what OS version he was using. Also, he's on >> G4, so gcc 3.3 is a native compiler, not a cross-compiler. >> >> But, Thomas, if you're running Mac OS X 10.3.9, then you need >> Xcode 1.5, which installs gcc 3.3 and that's supposed to be fine >> for MacPorts. If you're on Mac OS X 10.4.10, then you need Xcode >> 2.4.1 which installs gcc 4.0, and your gcc_select should be set to >> use gcc 4.0, which is the default. Using gcc 3.3 as your system >> compiler on Mac OS X 10.4 is not supported by MacPorts, and I >> don't recommend it for any reason. > > thank you very much for all the details :-) > > i have 10.4, two remote computers with ppc, and my local computer > with intel > > > but, if on 10.4 the "core" is gcc 4.0, > why is there > "This package contains the Apple version of the gcc 4.0 compiler." > and > "This package contains the Apple version of the gcc 3.3 compiler, > and is required to use the Developer Tools on Mac OS X." > even on intel, which let us suppose that the "core" is gcc 3.3 ? Regardless of whether you have an Intel or PowerPC Mac, Apple's gcc 3.3 makes only PowerPC binaries, and Apple's gcc 4.0 can make either Intel or PowerPC or universal binaries. It is useful for developers who wish to create universal binaries of their programs to use gcc 3.3 for the PowerPC parts and gcc 4.0 for the Intel parts and to later combine them using lipo. This ensures that the software works with earlier Mac OS X releases on PowerPC. From paulbeard at gmail.com Mon Oct 1 19:53:52 2007 From: paulbeard at gmail.com (paul beard) Date: Tue Oct 9 16:43:41 2007 Subject: MySQL5, OS X 10.4.10, startups, etc. In-Reply-To: <614AE1EC-2C14-42FC-A641-2A063BBA2E0C@macports.org> References: <31A8D5F4-32F0-4EB1-97CA-8B1AACA1762A@centosprime.com> <614AE1EC-2C14-42FC-A641-2A063BBA2E0C@macports.org> Message-ID: On 10/1/07, Ryan Schmidt wrote: > > On Oct 1, 2007, at 17:52, paul beard wrote: > > > On 10/1/07, Ryan Schmidt wrote: > > > > Yes, we do want MacPorts to install as much as possible inside $ > {prefix}. But currently some things do get installed outside of the > prefix. But IMHO the current uninstall instructions adequately > address this issue. BTW, "rm -rf /opt/local" is not the extent of the > uninstall instructions: Um, yes, I realize that. Allow the possibility that someone will just do rm -rf /opt/local when they get stuck without realizing that they are leaving some cruft behind. > And as for invoking launchct load statements, how is this different? > > > > launchctl load /opt/local/etc/LaunchDaemons/org.macports.dbus/ > > org.macports.dbus.plist > > launchctl load /opt/local/etc/LaunchDaemons/org.macports.apache2/ > > org.macports.apache2.plist > > launchctl load /opt/local/etc/LaunchDaemons/org.macports.mysql5/ > > org.macports.mysql5.plist > > > > from putting the plists in launchd's default search path? As > > configured, launchctl looks in two places for plists: in /System/ > > Library/LaunchDaemons, for Apple-owned stuff, in /Library/ > > LaunchDaemons for user-installed/third-party stuff. I don't see a > > big deal about another repository for plists. Maybe in future > > releases launchd will allow additional directories to be added > > instead of individual lines. > > > >> Your way would require someone to manually edit the file /etc/ > >> launchd.conf, at least to remove a line from it. That's more > >> complicated than the current way, where a single launchctl line > >> starts or stops the service. Also, with your way, the service > >> wouldn't start or stop until the next startup. That's worse than what > >> we have now, where the service starts or stops immediately. > > > > see above: if launchctl works as it says on the tin, there is not > > different between symlinks that point to /Library/LaunchDaemons and > > the lines I have in /etc/launchd.conf. > > Wait. Currently, MacPorts automatically puts the symlinks in /Library/ > LaunchDaemons, then instructs you how to load (start) and unload > (stop) as needed. Your proposition as I understood it was that the > user would manually add and remove lines in /etc/launchd.conf. Are > you now suggesting instead that MacPorts would automatically put the > lines in /etc/launchd.conf? If so, why is that preferable to the > current way? Currently, we add symlinks in /Library/LaunchDaemons, > which is outside of ${prefix}. You propose modifying /etc/ > launchd.conf, which is also outside of ${prefix}. At least the > symlinks in /Library/LaunchDaemons have "macports" in the filenames > so they're easier to find, and getting rid of them is as simple as a > single "rm" command. Getting rid of a line in a conf file is more > involved. Easy to find if someone knows to look for them. Also, since I'm not familiar with /etc/launchd.conf, I assume that > the file is only scanned at system startup. Is that the case? If so, > then adding to that file is worse than what we have now, where > "launchctl load" will load the service immediately, and cause it to > start at every subsequent system startup. Unless you're suggesting > that the user should modify /etc/launchd.conf, and then also use the > launchctl command to start the service now. If so, you've just added > an extra step for the user, again for no apparent benefit. man launchd.conf? if you understand how launchd/launchctl works, you would know that a launchctl load statement means "load this plist file and do what it says until instructed otherwise." It doesn't matter if it's loaded on the command line or at boot time: once the instructions are loaded, they stay there. >> Running a single launchctl command to start or stop a service is > >> easy. Conversely, adding a line to a file is easy, as you showed, but > >> removing a line from a file requires a more elaborate script. So why > >> change it to make it more difficult? > > > > I'm not arguing in favor of it. I'm just explaining it. I have a > > hard time believing that, given the power on tap, that there is no > > way to add a commented line to /etc/launchd.conf > > > > launchctl load /opt/local/etc/LaunchDaemons/org.macports.dbus/ > > org.macports.dbus.plist # installed by macports > > > > > > and add a # character to the beginning of the line containing the > > comment: > > > > sed -e s/^launchctl/#&/g <- yes, I know that won't work, but you > > get the idea: sed is not my native language. > > Yes, of course it's possible to write something with sed or similar > that adds or removes a specific line from a file. My point is that > it's more difficult than executing a single launchctl statement. And > since the current way works, I didn't understand why you think it's > better to complicate things. Perhaps I don't think it's complicated. It's not clear that the other way works optimally. The process of starting up daemons since Tiger is a departure and for a lot of people it doesn't always work properly (check the subject line of this thread and see if there are any others similarly named in the archives). What I'm hearing is "this way works because I understand it, and I don't understand your way. Different == bad." I really don't care what anyone uses. I found a way that works for me, even if it repeats steps that MacPorts already does. >> There's a slight problem with the current way. If the service is > >> running at the time that you uninstall the port, the software stays > >> running. And if the service is running at the time that you upgrade > >> the port, the old version stays running and the new version's plist > >> says the software isn't running and it's inconvenient to fix that > >> (manually edit the plist to show that the software is running, > >> launchctl unload the software, launchctl load it again). Would your > >> new way solve either of these problems? (I haven't tried so I don't > >> know.) > > > > Is there no pre-install step that could stop the service with the > > existing plist, install, restart? > > I don't think MacPorts should be stopping or starting any services > automatically. That could be unexpected and bad. Hmm. Sounds like that was what you were asking for. I think upgrading a process and having it stopped and *not* restarted is worse. I have my FreeBSD installation set to restart any process for which an rc script is installed. So at upgrade time, stop the process with its plist file, do the upgrade, then let the administrator know that the port is upgraded and not running, with the requisite launchctl instruction to start it. Conversely, I would make automatically starting upgraded daemons an option for people in high-availability environments. I've been meaning to submit bug reports about these situations but > hadn't gotten around to it yet. > > > Again, I'm not arguing in favor of doing it this way, I'm just > > explaining it. Perhaps if it's more clearly understood, a > > comparison can be made. > > Ok. Then I'll say that I acknowledge that MacPorts could do it your > way instead of how it does it now, but I don't see any advantage to > making that change at this point, rather I currently see > disadvantages, so I don't think MacPorts should change this right > now, until someone shows why it's better. Again, I simply offer this an alternative way that leverages the launchd/launchctl infrastructure. I'm done with this thread. It's diverged quite a bit and not very productively. -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20071001/136f63f0/attachment.html From joe.uelk at gmail.com Mon Oct 1 21:42:22 2007 From: joe.uelk at gmail.com (Joe) Date: Tue Oct 9 16:43:41 2007 Subject: ffmpeg - unable to install In-Reply-To: <05D51E30-6997-4448-9EE9-5D8F5270F9E7@macports.org> References: <9d6632e0710011457j5a3ae14ai272a096fe004d848@mail.gmail.com> <05D51E30-6997-4448-9EE9-5D8F5270F9E7@macports.org> Message-ID: <9d6632e0710012142t3a7072edv6b0cb3f8e6d21d64@mail.gmail.com> I tried ffmpeg on another machine and it works... so apparently I have something messed up somewhere... both machines are 10.4.10 Intel. Thanks! On 10/1/07, Ryan Schmidt wrote: > > > On Oct 1, 2007, at 16:57, Joe wrote: > > > I can't get ffmpeg to install. Has anyone else had a similar > > problem? See below. > > I see this message with that error (but no response): > > http://lists.mplayerhq.hu/pipermail/ffmpeg-user/2007-July/010101.html > > I also see this MacPorts bug filed (but no resolution): > > http://trac.macports.org/projects/macports/ticket/12191 > > It works fine for me on Mac OS X 10.4.10, Xcode 2.4.1, MacPorts 1.5.2: > > $ sudo port install ffmpeg > Password: > ---> Fetching ffmpeg > ---> Verifying checksum(s) for ffmpeg > ---> Extracting ffmpeg > ---> Configuring ffmpeg > ---> Building ffmpeg with target all > ---> Staging ffmpeg into destroot > ---> Installing ffmpeg 0.4.9-pre1_2 > ---> Activating ffmpeg 0.4.9-pre1_2 > ---> Cleaning ffmpeg > $ > > Perhaps you can provide more information about your setup. > > > sudo port install ffmpeg > > ---> Fetching ffmpeg > > ---> Verifying checksum(s) for ffmpeg > > ---> Extracting ffmpeg > > ---> Configuring ffmpeg > > ---> Building ffmpeg 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_multi > > media_ffmpeg/work/trunk" && make all " returned error 2 > > Command output: gcc -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/ > > build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H - > > D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/ > > local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/ > > include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign- > > compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall > > -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant- > > decls -Wno-pointer-sign -O3 -c -o i386/motion_est_mmx.o i386/ > > motion_est_mmx.c > > In file included from /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/dsputil.h:33, > > from i386/motion_est_mmx.c:24: > > /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: > > 'ImgReSampleContext' is deprecated > > /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: > > 'ImgReSampleContext' is deprecated > > gcc -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/ > > build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H - > > D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/ > > local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/ > > include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign- > > compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall > > -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant- > > decls -Wno-pointer-sign -O3 -c -o i386/simple_idct_mmx.o i386/ > > simple_idct_mmx.c > > In file included from /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/dsputil.h:33, > > from i386/simple_idct_mmx.c:22: > > /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: > > 'ImgReSampleContext' is deprecated > > /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: > > 'ImgReSampleContext' is deprecated > > gcc -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/ > > build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H - > > D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/ > > local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/ > > include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign- > > compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall > > -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant- > > decls -Wno-pointer-sign -O3 -c -o i386/idct_mmx_xvid.o i386/ > > idct_mmx_xvid.c > > In file included from i386/idct_mmx_xvid.c:53: > > /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: > > 'ImgReSampleContext' is deprecated > > /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: > > 'ImgReSampleContext' is deprecated > > gcc -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libswscale -I"/opt/local/var/macports/ > > build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libavcodec -DHAVE_AV_CONFIG_H - > > D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I"/opt/ > > local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk" -I"/opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk"/libavutil -O2 -DHAVE_LRINTF -I/opt/local/ > > include -no-cpp-precomp -pipe -force_cpusubtype_ALL -Wno-sign- > > compare -fomit-frame-pointer -g -Wdeclaration-after-statement -Wall > > -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant- > > decls -Wno-pointer-sign -O3 -c -o i386/fft_sse.o i386/fft_sse.c > > In file included from /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/dsputil.h:33, > > from i386/fft_sse.c:21: > > /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2501: warning: > > 'ImgReSampleContext' is deprecated > > /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_multi > > media_ffmpeg/work/trunk/libavcodec/avcodec.h:2507: warning: > > 'ImgReSampleContext' is deprecated > > {standard input}:259:Missing operand value assumed absolute 0. > > {standard input}:260:Missing operand value assumed absolute 0. > > {standard input}:263:Missing operand value assumed absolute 0. > > {standard input}:264:Missing operand value assumed absolute 0. > > {standard input}:431:Missing operand value assumed absolute 0. > > {standard input}:433:Missing operand value assumed absolute 0. > > {standard input}:437:Missing operand value assumed absolute 0. > > {standard input}:457:Missing operand value assumed absolute 0. > > make[1]: *** [i386/fft_sse.o] Error 1 > > make: *** [lib] Error 2 > > rm doc/ffserver.pod doc/ffmpeg.pod doc/ffplay.pod > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20071001/3cd4bf91/attachment.html From ryandesign at macports.org Mon Oct 1 22:37:01 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: ffmpeg - unable to install In-Reply-To: <9d6632e0710012142t3a7072edv6b0cb3f8e6d21d64@mail.gmail.com> References: <9d6632e0710011457j5a3ae14ai272a096fe004d848@mail.gmail.com> <05D51E30-6997-4448-9EE9-5D8F5270F9E7@macports.org> <9d6632e0710012142t3a7072edv6b0cb3f8e6d21d64@mail.gmail.com> Message-ID: <58AC3FEC-C754-4382-92C2-903BDAA317D4@macports.org> On Oct 1, 2007, at 23:42, Joe wrote: > On 10/1/07, Ryan Schmidt wrote: > >> On Oct 1, 2007, at 16:57, Joe wrote: >> >> > I can't get ffmpeg to install. Has anyone else had a similar >> > problem? See below. >> >> I see this message with that error (but no response): >> >> http://lists.mplayerhq.hu/pipermail/ffmpeg-user/2007-July/010101.html >> >> I also see this MacPorts bug filed (but no resolution): >> >> http://trac.macports.org/projects/macports/ticket/12191 >> >> It works fine for me on Mac OS X 10.4.10, Xcode 2.4.1, MacPorts >> 1.5.2: >> >> $ sudo port install ffmpeg >> Password: >> ---> Fetching ffmpeg >> ---> Verifying checksum(s) for ffmpeg >> ---> Extracting ffmpeg >> ---> Configuring ffmpeg >> ---> Building ffmpeg with target all >> ---> Staging ffmpeg into destroot >> ---> Installing ffmpeg 0.4.9-pre1_2 >> ---> Activating ffmpeg 0.4.9-pre1_2 >> ---> Cleaning ffmpeg >> $ >> >> Perhaps you can provide more information about your setup. > > I tried ffmpeg on another machine and it works... so apparently I > have something messed up somewhere... > > both machines are 10.4.10 Intel. Version of MacPorts? Version of Xcode? Anything in /usr/local? (Can be problematic.) Is Fink also installed (in /sw? Can be problematic). Since at least 2 others have also encountered this error it would be good to know what causes it. From afb at macports.org Mon Oct 1 23:51:27 2007 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Tue Oct 9 16:43:41 2007 Subject: problem when installing macports In-Reply-To: <3ED684B6-5AA9-4E95-82C1-C98A782E74BA@free.fr> References: <588e6e973aecd31994d173f9afad2d26@macports.org> <0D85D1B8-6AB8-4CC8-9733-49C372783206@macports.org> <3ED684B6-5AA9-4E95-82C1-C98A782E74BA@free.fr> Message-ID: <4f7708f9028320d50e73ea954879c3c9@macports.org> Thomas De?Contes: >> Anders, he didn't say what OS version he was using. Also, he's on G4, >> so gcc 3.3 is a native compiler, not a cross-compiler. Actually I meant platform cross-compiler rather than architecture cross-compiler, but it doesn't matter much... >> But, Thomas, if you're running Mac OS X 10.3.9, then you need Xcode >> 1.5, which installs gcc 3.3 and that's supposed to be fine for >> MacPorts. If you're on Mac OS X 10.4.10, then you need Xcode 2.4.1 >> which installs gcc 4.0, and your gcc_select should be set to use gcc >> 4.0, which is the default. Using gcc 3.3 as your system compiler on >> Mac OS X 10.4 is not supported by MacPorts, and I don't recommend it >> for any reason. > > thank you very much for all the details :-) > > i have 10.4, two remote computers with ppc, and my local computer with > intel > > but, if on 10.4 the "core" is gcc 4.0, > why is there > "This package contains the Apple version of the gcc 4.0 compiler." > and > "This package contains the Apple version of the gcc 3.3 compiler, and > is required to use the Developer Tools on Mac OS X." > even on intel, which let us suppose that the "core" is gcc 3.3 ? It probably just wasn't updated since it really was the required one... Like Ryan says, Mac OS X 10.3.9 (with Xcode 1.5) is also still OK to use. Mac OS X 10.4.10 (actually Xcode 2.4.1) comes with *four* compilers, one for each version of Mac OS X: gcc2, gcc3, gcc-3.3 and gcc-4.0 The recommended one is gcc-4.0, since it can't build Universal binaries with the gcc-3.3 (and since GCC 4 is much better than GCC 3 anyway, but) Usually you just install the "XcodeTools.mpkg", instead of individual pkg ? And that will install *both* of gcc4.0.pkg and gcc3.3.pkg, by default... --anders From gelfmuse at gmail.com Tue Oct 2 00:12:32 2007 From: gelfmuse at gmail.com (mike clemow) Date: Tue Oct 9 16:43:41 2007 Subject: Problems installing Oregano. In-Reply-To: <25554896-3AAF-4356-B069-7658D2C8F783@macports.org> References: <25554896-3AAF-4356-B069-7658D2C8F783@macports.org> Message-ID: I noticed that it was an old version too. I've already downloaded the oregano-0.69.0 source, but I'm not sure how to compile it against what macports has installed. I would actually be glad to update the package, but I'm not sure how to go about doing that (e.g. rewriting the portfile, etc.). What section of the wiki should I read? I'd be fine just getting it to run on my machine, but it's a shame it's not available to everyone. Cheers, Mike On 10/1/07, Ryan Schmidt wrote: > On Oct 1, 2007, at 19:35, mike clemow wrote: > > > I'm new to macports from Debian. I'm trying to install oregano, and > > all the dependencies have downloaded and installed, but when > > port gets > > the oregano source, this happens: > > ------------ > > ---> Fetching oregano > > ---> oregano-0.3.2.tar.bz2 doesn't seem to exist in > > /opt/local/var/macports/distfiles/oregano > > ---> Attempting to fetch oregano-0.3.2.tar.bz2 from > > http://opendarwin.org/~olegb/ > > ---> Attempting to fetch oregano-0.3.2.tar.bz2 from > > http://svn.macports.org/repository/macports/distfiles/oregano > > % Total % Received % Xferd Average Speed Time Time > > Time Current > > Dload Upload Total > > Spent Left Speed > > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > > --:--:-- 0 > > ---> Attempting to fetch oregano-0.3.2.tar.bz2 from > > http://svn.macports.org/repository/macports/distfiles/general/ > > % Total % Received % Xferd Average Speed Time Time > > Time Current > > Dload Upload Total > > Spent Left Speed > > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > > --:--:-- 0 > > ---> Attempting to fetch oregano-0.3.2.tar.bz2 from > > http://svn.macports.org/repository/macports/downloads/oregano > > > > - Ignored: > > % Total % Received % Xferd Average Speed Time Time > > Time Current > > Dload Upload Total > > Spent Left Speed > > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- > > --:--:-- 0 > > Error: Target org.macports.fetch returned: fetch failed > > Warning: the following items did not execute (for oregano): > > org.macports.activate org.macports.fetch org.macports.extract > > org.macports.checksum org.macports.patch org.macports.configure > > org.macports.build org.macports.destroot org.macports.install > > Error: Status 1 encountered during processing. > > ------------- > > > > What exactly does this mean? Does this mean that the file just > > isn't > > there? Or should I be asking this on another list? > > This is the right list. I see the oregano port still tries to fetch > from opendarwin. opendarwin died quite awhile ago. Also it looks like > the port hasn't been substantially updated since being initially > added on 2004-11-16. The port is for oregano 0.3.2 but the current > version is 0.69.0. It looks like maybe the reason the distfile was > stored on opendarwin is that the project does not release source > tarballs; currently they tell you to pull the source via darcs. > Someone who knows about this software should fetch the 0.69.0 source, > put the tarball up in the macports repository, and update the port to > 0.69.0. Probably best to just totally rewrite the portfile. > > -- http://shadowofaculture.blogspot.com From ryandesign at macports.org Tue Oct 2 00:20:45 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: Problems installing Oregano. In-Reply-To: References: <25554896-3AAF-4356-B069-7658D2C8F783@macports.org> Message-ID: On Oct 2, 2007, at 02:12, mike clemow wrote: > On 10/1/07, Ryan Schmidt wrote: > >> On Oct 1, 2007, at 19:35, mike clemow wrote: >> >>> I'm new to macports from Debian. I'm trying to install oregano, and >>> all the dependencies have downloaded and installed, but when >>> port gets the oregano source, this happens: [snip fetch failure] >>> What exactly does this mean? Does this mean that the file just >>> isn't there? Or should I be asking this on another list? >> >> This is the right list. I see the oregano port still tries to fetch >> from opendarwin. opendarwin died quite awhile ago. Also it looks like >> the port hasn't been substantially updated since being initially >> added on 2004-11-16. The port is for oregano 0.3.2 but the current >> version is 0.69.0. It looks like maybe the reason the distfile was >> stored on opendarwin is that the project does not release source >> tarballs; currently they tell you to pull the source via darcs. >> Someone who knows about this software should fetch the 0.69.0 source, >> put the tarball up in the macports repository, and update the port to >> 0.69.0. Probably best to just totally rewrite the portfile. > > I noticed that it was an old version too. I've already downloaded the > oregano-0.69.0 source, but I'm not sure how to compile it against what > macports has installed. I would actually be glad to update the > package, but I'm not sure how to go about doing that (e.g. rewriting > the portfile, etc.). What section of the wiki should I read? > > I'd be fine just getting it to run on my machine, but it's a shame > it's not available to everyone. We would certainly appreciate it if you would update the port. The wiki is not useful for learning that, but the new guide, which is in the process of being written, should be. While it is being developed, it is available at this temporary URL: http://geeklair.net/new_macports_guide/ From gelfmuse at gmail.com Tue Oct 2 00:44:56 2007 From: gelfmuse at gmail.com (mike clemow) Date: Tue Oct 9 16:43:41 2007 Subject: Problems installing Oregano. In-Reply-To: References: <25554896-3AAF-4356-B069-7658D2C8F783@macports.org> Message-ID: Alright - That's a lot to absorb. I'm going to have questions. ;-) I really want this app to work, though, so I'll get back to you folks. Cheers, Mike On 10/2/07, Ryan Schmidt wrote: > > On Oct 2, 2007, at 02:12, mike clemow wrote: > > > On 10/1/07, Ryan Schmidt wrote: > > > >> On Oct 1, 2007, at 19:35, mike clemow wrote: > >> > >>> I'm new to macports from Debian. I'm trying to install oregano, and > >>> all the dependencies have downloaded and installed, but when > >>> port gets the oregano source, this happens: > > [snip fetch failure] > > >>> What exactly does this mean? Does this mean that the file just > >>> isn't there? Or should I be asking this on another list? > >> > >> This is the right list. I see the oregano port still tries to fetch > >> from opendarwin. opendarwin died quite awhile ago. Also it looks like > >> the port hasn't been substantially updated since being initially > >> added on 2004-11-16. The port is for oregano 0.3.2 but the current > >> version is 0.69.0. It looks like maybe the reason the distfile was > >> stored on opendarwin is that the project does not release source > >> tarballs; currently they tell you to pull the source via darcs. > >> Someone who knows about this software should fetch the 0.69.0 source, > >> put the tarball up in the macports repository, and update the port to > >> 0.69.0. Probably best to just totally rewrite the portfile. > > > > I noticed that it was an old version too. I've already downloaded the > > oregano-0.69.0 source, but I'm not sure how to compile it against what > > macports has installed. I would actually be glad to update the > > package, but I'm not sure how to go about doing that (e.g. rewriting > > the portfile, etc.). What section of the wiki should I read? > > > > I'd be fine just getting it to run on my machine, but it's a shame > > it's not available to everyone. > > We would certainly appreciate it if you would update the port. The > wiki is not useful for learning that, but the new guide, which is in > the process of being written, should be. While it is being developed, > it is available at this temporary URL: > > http://geeklair.net/new_macports_guide/ > > > > -- http://shadowofaculture.blogspot.com From ryandesign at macports.org Tue Oct 2 01:31:35 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: Problems installing Oregano. In-Reply-To: References: <25554896-3AAF-4356-B069-7658D2C8F783@macports.org> Message-ID: <5552F7D2-3E94-4B92-957C-953F72A665C4@macports.org> On Oct 2, 2007, at 02:44, mike clemow wrote: > On 10/2/07, Ryan Schmidt wrote: > >> On Oct 2, 2007, at 02:12, mike clemow wrote: >> >>> On 10/1/07, Ryan Schmidt wrote: >>> >>>> On Oct 1, 2007, at 19:35, mike clemow wrote: >>>> >>>>> I'm new to macports from Debian. I'm trying to install >>>>> oregano, and >>>>> all the dependencies have downloaded and installed, but when >>>>> port gets the oregano source, this happens: >> >> [snip fetch failure] >> >>>>> What exactly does this mean? Does this mean that the file just >>>>> isn't there? Or should I be asking this on another list? >>>> >>>> This is the right list. I see the oregano port still tries to fetch >>>> from opendarwin. opendarwin died quite awhile ago. Also it looks >>>> like >>>> the port hasn't been substantially updated since being initially >>>> added on 2004-11-16. The port is for oregano 0.3.2 but the current >>>> version is 0.69.0. It looks like maybe the reason the distfile was >>>> stored on opendarwin is that the project does not release source >>>> tarballs; currently they tell you to pull the source via darcs. >>>> Someone who knows about this software should fetch the 0.69.0 >>>> source, >>>> put the tarball up in the macports repository, and update the >>>> port to >>>> 0.69.0. Probably best to just totally rewrite the portfile. >>> >>> I noticed that it was an old version too. I've already >>> downloaded the >>> oregano-0.69.0 source, but I'm not sure how to compile it against >>> what >>> macports has installed. I would actually be glad to update the >>> package, but I'm not sure how to go about doing that (e.g. rewriting >>> the portfile, etc.). What section of the wiki should I read? >>> >>> I'd be fine just getting it to run on my machine, but it's a shame >>> it's not available to everyone. >> >> We would certainly appreciate it if you would update the port. The >> wiki is not useful for learning that, but the new guide, which is in >> the process of being written, should be. While it is being developed, >> it is available at this temporary URL: >> >> http://geeklair.net/new_macports_guide/ > > Alright - That's a lot to absorb. I'm going to have questions. ;-) > I really want this app to work, though, so I'll get back to you folks. The current oregano port looks relatively straightforward so hopefully the software will not have become more difficult to build since 0.3.2. You will want to change the depends_lib items from lib:X:X form to port:X form (lib:X:X form is deprecated in most cases). You may need to add new dependencies if the software has grown any new dependencies since 0.3.2. otool -L on the installed products can tell you. You should also check whether the cflags and cppflags are still necessary; try without them. You should look through oregano's ./configure --help to see if any new configure arguments should be used. From gelfmuse at gmail.com Tue Oct 2 05:21:11 2007 From: gelfmuse at gmail.com (mike clemow) Date: Tue Oct 9 16:43:41 2007 Subject: Problems installing Oregano. In-Reply-To: <5552F7D2-3E94-4B92-957C-953F72A665C4@macports.org> References: <25554896-3AAF-4356-B069-7658D2C8F783@macports.org> <5552F7D2-3E94-4B92-957C-953F72A665C4@macports.org> Message-ID: Okay, this is all in the portfile, I assume? Out of curiosity, why TCL? I know that there is at least one new dependency. The problem I'm having at the moment is that the new package uses scons to build and I can't get it to run. I installed the new dependency with port and also scons, but when I go to run scons in the src directory, it doesn't run. Upon investigation I found that scons is trying to run with /opt/local/bin/python and it's not there because the install was differentiated from the default Mac OS X installation of python. The port version is /opt/ocal/bin/python2.4. I'm sure scons has some kind of config file somewhere, but I'll have to dig for it. There will be a sconsscript rather than a configure file, but the idea is the same. Is there anything special I have to do with the portfile to build the package with scons, or is that basically the same deal too? Cheers, mike On 10/2/07, Ryan Schmidt wrote: > On Oct 2, 2007, at 02:44, mike clemow wrote: > > > On 10/2/07, Ryan Schmidt wrote: > > > >> On Oct 2, 2007, at 02:12, mike clemow wrote: > >> > >>> On 10/1/07, Ryan Schmidt wrote: > >>> > >>>> On Oct 1, 2007, at 19:35, mike clemow wrote: > >>>> > >>>>> I'm new to macports from Debian. I'm trying to install > >>>>> oregano, and > >>>>> all the dependencies have downloaded and installed, but when > >>>>> port gets the oregano source, this happens: > >> > >> [snip fetch failure] > >> > >>>>> What exactly does this mean? Does this mean that the file just > >>>>> isn't there? Or should I be asking this on another list? > >>>> > >>>> This is the right list. I see the oregano port still tries to fetch > >>>> from opendarwin. opendarwin died quite awhile ago. Also it looks > >>>> like > >>>> the port hasn't been substantially updated since being initially > >>>> added on 2004-11-16. The port is for oregano 0.3.2 but the current > >>>> version is 0.69.0. It looks like maybe the reason the distfile was > >>>> stored on opendarwin is that the project does not release source > >>>> tarballs; currently they tell you to pull the source via darcs. > >>>> Someone who knows about this software should fetch the 0.69.0 > >>>> source, > >>>> put the tarball up in the macports repository, and update the > >>>> port to > >>>> 0.69.0. Probably best to just totally rewrite the portfile. > >>> > >>> I noticed that it was an old version too. I've already > >>> downloaded the > >>> oregano-0.69.0 source, but I'm not sure how to compile it against > >>> what > >>> macports has installed. I would actually be glad to update the > >>> package, but I'm not sure how to go about doing that (e.g. rewriting > >>> the portfile, etc.). What section of the wiki should I read? > >>> > >>> I'd be fine just getting it to run on my machine, but it's a shame > >>> it's not available to everyone. > >> > >> We would certainly appreciate it if you would update the port. The > >> wiki is not useful for learning that, but the new guide, which is in > >> the process of being written, should be. While it is being developed, > >> it is available at this temporary URL: > >> > >> http://geeklair.net/new_macports_guide/ > > > > Alright - That's a lot to absorb. I'm going to have questions. ;-) > > I really want this app to work, though, so I'll get back to you folks. > > The current oregano port looks relatively straightforward so > hopefully the software will not have become more difficult to build > since 0.3.2. You will want to change the depends_lib items from > lib:X:X form to port:X form (lib:X:X form is deprecated in most > cases). You may need to add new dependencies if the software has > grown any new dependencies since 0.3.2. otool -L on the installed > products can tell you. You should also check whether the cflags and > cppflags are still necessary; try without them. You should look > through oregano's ./configure --help to see if any new configure > arguments should be used. > > -- http://shadowofaculture.blogspot.com From pbholmen at yahoo.com Tue Oct 2 08:34:31 2007 From: pbholmen at yahoo.com (Per Bull Holmen) Date: Tue Oct 9 16:43:41 2007 Subject: Keyboard problems (backspace, up/down etc) with command-line tools Message-ID: <81858.82172.qm@web33113.mail.mud.yahoo.com> Hey I'm totally new to MacPorts, and fairly much a rookie regarding UNIX/X-Windows. I recently installed the package ng-spice after giving up on both MacSpice and finding a Fink *spice package. This is (mostly) a command-line tool, but uses some X11 and this works great. Installation is done according to the web site, although I have made a slight maneuver to make it work with both Fink and MacPorts, changing the ~/.bash_profile to the following: ----start # source .bashrc if it's there if [ -f ~/.bashrc ]; then . ~/.bashrc fi # For darwinports export PATH=/opt/local/bin:/opt/local/sbin:$PATH export DISPLAY=:0.0 echo 'setup for darwinports' # For fink # test -r /sw/bin/init.sh && . /sw/bin/init.sh # export DISPLAY=localhost:0 # echo 'setup for fink' echo 'edit ~/.bash_profile to set up for fink/darwinports' ----end I don't know if this is necessary, but the site explains that the PATH prepend operation may override som Apple libraries, therefore I assumed I there might be some compatibility problems if Fink installed libs get overridden by MacPorts installed libs or the opposite. (.bashrc does not exist BTW). I have not made any setup changes to system/init/bash files apart from installing Fink/Darwin. ANYWAY here is my problem: Running ngpsice from Apples terminal, the program won't recognize special keys like backspace and arrows. Running from xterm it WILL recognize backspace but not the other keys. The other keys output weird codes like [^A etc. Also, it seems that emacs (run from Apples Terminal) now recognize backspace as forward delete (I haven't touched the emacs installation, it's just the standard one from MacOS DVD). Is this a port problem, or soemthing I can fix by editing the setup? I'm running MacOS X 10.4 on an Intel-mac laptop, with Norwegian keyboard-layout. Per -- Mvh Per Bull Holmen "People demand freedom of speech as a compensation for the freedom of thought which they seldom use" - S?ren Kierkegaard _________________________________________________________ Alt i ?n. F? Yahoo! Mail med adressekartotek, kalender og notisblokk. http://no.mail.yahoo.com From mjijackson at gmail.com Tue Oct 2 08:58:48 2007 From: mjijackson at gmail.com (Michael Jackson) Date: Tue Oct 9 16:43:41 2007 Subject: PHP5 activation error Message-ID: <3C45476F-1D67-408E-AE5F-CDBC60206117@gmail.com> Hello all, I tried upgrading php5 this morning, but ran into the following error: ---> Activating php5 5.2.3_0+apache2+darwin_8+macosx+mysql5+pear +postgresql+sqlite Error: Target org.macports.activate returned: Image error: /opt/local/ lib/php/.registry/structures_graph.reg already exists and does not belong to a registered port. Unable to activate port php5. Error: Status 1 encountered during processing. Any ideas what the problem is here? Obviously it has something to do with the Structures_Graph PEAR package. Should I just delete that registry file? Any help is much appreciated. Thanks, Michael From joe.uelk at gmail.com Tue Oct 2 09:06:03 2007 From: joe.uelk at gmail.com (Joe) Date: Tue Oct 9 16:43:41 2007 Subject: ffmpeg - unable to install In-Reply-To: <58AC3FEC-C754-4382-92C2-903BDAA317D4@macports.org> References: <9d6632e0710011457j5a3ae14ai272a096fe004d848@mail.gmail.com> <05D51E30-6997-4448-9EE9-5D8F5270F9E7@macports.org> <9d6632e0710012142t3a7072edv6b0cb3f8e6d21d64@mail.gmail.com> <58AC3FEC-C754-4382-92C2-903BDAA317D4@macports.org> Message-ID: <9d6632e0710020906w676bd75bi56cda4312606a993@mail.gmail.com> Ryan, Thanks for your help! Below is the info of the problematic machine: OS X 10.4.10 Intel MacPorts: 1.520 Fink is installed under /sw: 0.27.6 Xcode: 2.2 gcc --version i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5247) ls /usr/local bin mysql etc mysql-5.0.45-osx10.4-i686 include sbin lib share libexec var man And the one that works: OS X 10.4.10 Intel MacPorts: 1.520 Fink is installed under /sw: 0.24.17 Xcode: 2.4.1 gcc --version i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5367) ls /usr/local bin include lib share Looks like Fink and XCode are different as is the content of /usr/local. Let me know if you want me to modify something and try ffmpeg again. Thanks, Joe On 10/2/07, Ryan Schmidt wrote: > > > On Oct 1, 2007, at 23:42, Joe wrote: > > > On 10/1/07, Ryan Schmidt wrote: > > > >> On Oct 1, 2007, at 16:57, Joe wrote: > >> > >> > I can't get ffmpeg to install. Has anyone else had a similar > >> > problem? See below. > >> > >> I see this message with that error (but no response): > >> > >> http://lists.mplayerhq.hu/pipermail/ffmpeg-user/2007-July/010101.html > >> > >> I also see this MacPorts bug filed (but no resolution): > >> > >> http://trac.macports.org/projects/macports/ticket/12191 > >> > >> It works fine for me on Mac OS X 10.4.10, Xcode 2.4.1, MacPorts > >> 1.5.2: > >> > >> $ sudo port install ffmpeg > >> Password: > >> ---> Fetching ffmpeg > >> ---> Verifying checksum(s) for ffmpeg > >> ---> Extracting ffmpeg > >> ---> Configuring ffmpeg > >> ---> Building ffmpeg with target all > >> ---> Staging ffmpeg into destroot > >> ---> Installing ffmpeg 0.4.9-pre1_2 > >> ---> Activating ffmpeg 0.4.9-pre1_2 > >> ---> Cleaning ffmpeg > >> $ > >> > >> Perhaps you can provide more information about your setup. > > > > I tried ffmpeg on another machine and it works... so apparently I > > have something messed up somewhere... > > > > both machines are 10.4.10 Intel. > > Version of MacPorts? Version of Xcode? Anything in /usr/local? (Can > be problematic.) Is Fink also installed (in /sw? Can be problematic). > Since at least 2 others have also encountered this error it would be > good to know what causes it. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20071002/200820b8/attachment.html From ryandesign at macports.org Tue Oct 2 13:54:18 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: ffmpeg - unable to install In-Reply-To: <688A6A19-7576-48F2-9485-05C1A34626F0@bellsouth.net> References: <9d6632e0710011457j5a3ae14ai272a096fe004d848@mail.gmail.com> <05D51E30-6997-4448-9EE9-5D8F5270F9E7@macports.org> <9d6632e0710012142t3a7072edv6b0cb3f8e6d21d64@mail.gmail.com> <58AC3FEC-C754-4382-92C2-903BDAA317D4@macports.org> <9d6632e0710020906w676bd75bi56cda4312606a993@mail.gmail.com> <688A6A19-7576-48F2-9485-05C1A34626F0@bellsouth.net> Message-ID: On Oct 2, 2007, at 15:27, William Davis wrote: > On Oct 2, 2007, at 12:06 PM, Joe wrote: > >> Below is the info of the problematic machine: >> >> OS X 10.4.10 Intel >> >> MacPorts: >> 1.520 >> >> Fink is installed under /sw: >> 0.27.6 >> >> Xcode: >> 2.2 > > Im sure Ryan will answer you shortly but why not upgrade Xcode to > 2.4.1 like your other machine? > good luck :) Absolutely. Earlier versions of Xcode are known to be problematic. That's why the first step of the installation instructions says that you must install the latest Xcode, not any older Xcode: http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts I also recommend you get rid of Fink. Possibly depending on your $PATH, MacPorts ports may inadvertently link with bits that were installed by Fink, which will be confusing and probably break things later. Move /sw elsewhere. Use MacPorts to install whatever software you had installed with Fink. From ryandesign at macports.org Tue Oct 2 14:33:25 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:43:41 2007 Subject: ffmpeg - unable to install In-Reply-To: References: <9d6632e0710011457j5a3ae14ai272a096fe004d848@mail.gmail.com> <05D51E30-6997-4448-9EE9-5D8F5270F9E7@macports.org> <9d6632e0710012142t3a7072edv6b0cb3f8e6d21