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

Fwd: [MacPorts] #13829: sudo port -fvd install mldonkey
by Charlse Darwin 05 Jan '08

05 Jan '08

`Assign to maintainer'? You mean pguyot(a)kallisys.net? Begin forwarded message: > From: "MacPorts" <trac(a)macosforge.org> > Date: January 5, 2008 12:02:40 AM EST (CA) > To: macports.users(a)gmail.com, pguyot(a)kallisys.net > Cc: macports-tickets(a)lists.macosforge.org > Subject: Re: [MacPorts] #13829: sudo port -fvd install mldonkey > Reply-To: noreply(a)macosforge.org > > #13829: sudo port -fvd install mldonkey > --------------------------------------- > +------------------------------------ > Reporter: macports.users(a)gmail.com | Owner: > pguyot(a)kallisys.net > Type: defect | Status: new > Priority: Normal | Milestone: Port Bugs > Component: ports | Version: 1.6.0 > Resolution: | Keywords: > --------------------------------------- > +------------------------------------ > Changes (by ryandesign(a)macports.org) > > * owner: macports-tickets(a)lists.macosforge.org => > pguyot(a)kallisys.net > * milestone: => Port Bugs > > Comment: > > Assign to maintainer > > -- > Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/ > 13829#comment:1> > MacPorts </projects/macports> > Ports system for Mac OS

2 1

Can someone commit? (gtkglext, gwyddion, qucs)
by Rolf Würdemann 05 Jan '08

05 Jan '08

First: #13624 (http://trac.macosforge.org/projects/macports/ticket/13624) (Update of the Portfile for gtkglext, so it runs on Leopard also) after that: #13737 (http://trac.macosforge.org/projects/macports/ticket/13737) (Update of gwyddion, so gwyddion works on leoparf also (depend on #13624) If this both updates are commited, tickets: #13560 (http://trac.macosforge.org/projects/macports/ticket/13560) and #13517 (http://trac.macosforge.org/projects/macports/ticket/13517) can also be closed (dealing with same issues, so no commits of them please;) if you have some spare time after this, it would be fine to commit #13826 (http://trac.macosforge.org/projects/macports/ticket/13826) which is an update of qucs to 0.0.13 ;) If there is anything whch denies to Portfiles from getting committed, please let me know ;) Reg's Rolf -- Security is an illusion - Datasecurity twice Rolf Würdemann - private: rowue(a)digitalis.org - office: rowue(a)crew-gmbh.de GnuPG fingerprint: 7383 348F 67D1 CD27 C90F DDD0 86A3 31B6 67F0 D02F jabber: rowue(a)digitalis.org 2F66A061 89BCA1A0 AD654827 6FD037FF 53C3E932

2 1

g95-0.90_2 Intel Leopard build error
by Adam Mercer 05 Jan '08

05 Jan '08

Hi I'm having a problem building g95-0.90_2 on Intel Leopard, I get the following error: Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/g95-0.90" && make all " returned error 2 Command output: /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/gcc.h:45:1: warning: this is the location of the previous definition gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-gather.awk \ /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/common.opt lang.opt > options.tmp gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/optc-gen.awk options.tmp > options.c gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opth-gen.awk options.tmp > options.h /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opts.c cc1: note: obsolete option -I- used, please use -iquote instead /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl options.c cc1: note: obsolete option -I- used, please use -iquote instead /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -DTARGET_NAME=\"i386-apple-darwin9.1.0\" -DSTANDARD_EXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DTARGET_SYSTEM_ROOT=\"\" -DDEFAULT_TARGET_VERSION=\"\" -DDEFAULT_TARGET_MACHINE=\"\" -DTOOLDIR_BASE_PREFIX=\"\" -DSTANDARD_STARTFILE_PREFIX=\"\" -DSTANDARD_STARTFILE_PREFIX_2=\"/usr/lib/\" -DSTANDARD_EXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DSTANDARD_BINDIR_PREFIX=\"/opt/local/bin\" -DSTANDARD_LIBEXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DG95_SPEC=\"\" -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/gcc.c cc1: note: obsolete option -I- used, please use -iquote instead echo "const char version_string[] = \"`cat gcc_version` (g95 0.90!) \" __DATE__;" > version.c echo 'const char bug_report_url[] = "http://www.g95.org or mail andyv(a)firstinter.net";' >> version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -c version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -L/opt/local/lib -o g95 g95-g95spec.o /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc/prefix.o gcc.o version.o /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc/intl.o /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/libiberty/libiberty.a /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl/libintl.a -liconv Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 Warning: the following items did not execute (for g95): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. Any ideas? Cheers Adam

1 0

Guile 1.8 port and Gnucash
by Mike Alexander 05 Jan '08

05 Jan '08

I discovered that there is a problem with the Guile 1.8 port. It includes a patch left over from the 1.6 version which is no longer relevant (and which causes problems) in version 1.8. It also fails to add some symlinks that are needed to make it work with Gnucash. I've attached a patch that fixes this (and adds a +debug variant). With these changes the current SVN version of Gnucash works with Guile 1.8. I haven't tried it with the Macports version of Gnucash, but it might work too. After applying the Portfile patch, the file patch-slib.scm is no longer needed and could be deleted. I'm not currently getting messages from the list since I'm on the road and trying to cut down on EMail, so reply directly if you need to contact me about this. -- Mike Alexander mta(a)umich.edu Ann Arbor, MI PGP key ID: BEA343A6

1 0

Re: Qt4.3.3 crashs with -system-sqlite
by Jochen Küpper 05 Jan '08

05 Jan '08

Dear MacPort users, this is an Email to qt-interest due to problems of sqlite support in Qt4 using macPorts' sqlite3 port. See the end for macPorts-specific questions, please. On 05.01.2008, at 10:46, Dimitri wrote: >> I am the MacPorts (www.macports.org) maintainer of Qt4 for Mac OS X. > > I understand this MacPort is a binary package for MacOS made from a > vanilla Qt/Mac source package. Is that correct? Yes. However, we do (yet) not distribute binary packages but "recipes" to build them on the destination machine. When executed the qt4-mac Portfile (recipe) downloads the source from TrollTech and builds it.. > By the way, you shouldn't have to force: > -largefile > -stl > > You definitely shouldn't need: > -no-nis > -no-cups > These are Qt/X11 only. Okay, but thet should not hurd, I guess. >> We are having some problems with sqlite support when using the >> system-sqlite (sqlite 3.5.4), i.e., calls to sqlite3_set_auxdata >> fail (confirmed, for example, for sqliteman and the books demo of >> Qt4). >> [...] >> Starting the books demo gives the following backtrace: >> [...] >> Exception Type: EXC_BAD_ACCESS (SIGBUS) >> Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000003d >> Crashed Thread: 0 >> Thread 0 Crashed: >> 0 libsqlite3.0.dylib 0x95f0a56e >> sqlite3_set_auxdata + 6062 >> 1 libsqlite3.0.dylib 0x95f380b2 >> sqlite3RegisterBuiltinFunctions + 178 >> 2 libsqlite3.0.dylib 0x010d2f41 openDatabase + 961 >> 3 libsqlite3.0.dylib 0x010d3033 sqlite3_open16 + 131 >> 4 libqsqlite.dylib 0x010a6124 [...] > > This could as well be an issue with SQLite. It would be interesting > to see how the system SQLite library itself has been built. It's build using this Portfile http://trac.macports.org/projects/macports/browser/trunk/dports/databases/s… > What are the arguments passed to sqlite3_open16? It would be worth > writing a non-Qt program and passing the same arguments to > sqlite3_open16. Does it also crash? For the books example this should be the call from within Qt's bool QSQLiteDriver::open(const QString & db, const QString &, const QString &, const QString &, int, const QString &conOpts) which is this: if (sqlite3_open16(db.constData(), &d->access) == SQLITE_OK) { We get there from books.app QSqlError initDb() which contains QSqlDatabase db = QSqlDatabase::addDatabase("QSQLITE"); ... MacPorts question: Are people successfully using MacPorts' sqlite3 port? Are you using the functions in question? sqlite3_open16 sqlite3_set_auxdata Are there any known issues with these functions on Mac OS X or in MacPorts? Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll

1 0

Re: plans for 64bit support (Joshua Root)
by Emil Lundberg 05 Jan '08

05 Jan '08

>>> The default should be to build 32-bit binaries on ppc64 machines, >>> since >>> ppc64 code is generally slower. There should be a config file >>> option so >>> those on ppc64 hardware can build everything 64-bit if they want. On >>> x86_64 machines, 64-bit binaries should be the default. >>> >>> +universal should default to building for ppc32, x86, and x86_64. >>> That >>> will generally give the best performance everywhere. >> >> An interesting perspective. Is there documentation backing up the >> claim >> that 64-bit ppc code is slower on 64-bit ppc machines than 32-bit >> ppc code? > > I've seen benchmark numbers that show this. I'll see if I can dig > them up. > >> > From a theoretical perspective, it's pretty clear that a PPC chip > running in 64-bit mode must be at least a little bit slower than the > same chip running in 32-bit mode, since pointers are twice as wide. > They > take up twice as much room in the caches and in memory. They also take > twice as many instructions to load and store. > > That's only when the code doesn't take advantage of the 64-bit > architecture, of course. Going to ppc64 can be a win if you need to > use > huge amounts of RAM in a single process, if your code can be > simplified > by making use of the 64-bit address space (e.g. mmap()ing a 200 GB > file), or if you use 64-bit integer arithmetic (which is emulated by > the > compiler on 32-bit). Thought I'd chip in. We use a wide array of hardware at our site; ppc & x86, 32 and 64-bit. Some applications DO need the 64-bit binaries (need to address 6+ Gb arrays), and the major hurdle in using 64-bit is not in the apps themselves but in all the libraries that they use. From our perspective, it is more important to support building fat 32/64-bit binaries than ppc/x86, as we do not generally share or sync the macports file tree between machines (way too risky and servers tend to be out of sync library- and OS-wise anyway). Thus a particular machine does not require dual architetures but may require 32/64-bit binaries/libraries, depending on the apps that use them. Also, the rest of the OS nowadays is quad-fat, so so should MacPorts, right... :-) Regarding +universal; unless someone can prove that there is a MAJOR, real-life, performance hit when using ppc64, my vote is on building the most competent binary possible, including the ppc64, for consistency and simplicity (given that the port actually builds, of course). Either that or split it into say +univ_arch and +univ_bit, but I'm all for simplicity. Of course, as Ryan said: it's not a matter of the building itself, but tying it all together at the end. I realise this no small matter, either. Best regards, /Emil

6 9

Re: sudo port install mldonkey
by Ryan Schmidt 05 Jan '08

05 Jan '08

Please keep the discussion on the mailing list using Reply All when you reply. On Jan 4, 2008, at 15:55, Charlse Darwin wrote: > $ sudo port install mldonkey > Password: > ---> Configuring mldonkey > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_m > ldonkey/work/mldonkey-2.8.5" && ./configure --prefix=/opt/local " > returned error 1 > Command output: > -------------------------------- > Checking system tools. > -------------------------------- > checking for ranlib... ranlib > checking for gmake... gmake > checking for make... (cached) gmake > checking if gmake is GNU make ... yes > checking for bzip2... bzip2 > checking for gzip... (cached) bzip2 > checking for perl... /opt/local/bin/perl > checking for rpmbuild... no > checking for rpm... no > checking for wget... wget > ---------------------------------------- > Checking system tools finished. > ---------------------------------------- > > -------------------------------- > Checking Ocaml compiler. > -------------------------------- > checking for ocamlc.opt... /opt/local/bin/ocamlc.opt > checking for ocamlc... /opt/local/bin/ocamlc.opt > checking for camlp4... /opt/local/bin/camlp4 > Need build > ******** Objective-Caml 3.09.3 is required ********* > ******* Check http://caml.inria.fr/ ******** > Do you want this script to try to download and install ocaml > LOCALLY in mldonkey directory ? > ./configure: line 4612: read: read error: 0: Bad file descriptor > > Error: Status 1 encountered during processing. > $ port -q info --version ocaml > 3.10.0 > $ I agree. I get the same thing. Maybe mldonkey 2.8.5 just does not work with ocaml 3.10.0 (since it says it needs "3.09.3" (and not "3.09.3 or later")). You should file a ticket in our issue tracker and assign it to the maintainer of the mldonkey port. Maybe updating the port to the current version of mldonkey, 2.9.2, would help. You could edit the portfile yourself and test whether updating to 2.9.2 works; if it does, you can attach your diff to the ticket.

3 5

Re: sudo port install mldonkey
by Charlse Darwin 04 Jan '08

04 Jan '08

$ ls -l /usr/bin/sed -r-xr-xr-x 1 root wheel 38424 Dec 31 09:16 /usr/bin/sed* $ file /usr/bin/sed /usr/bin/sed: Mach-O executable ppc $ which sed /usr/bin/sed Should chmod 68388 /usr/bin/sed ? On Jan 4, 2008, at 3:23 PM, Ryan Schmidt wrote: > On Jan 4, 2008, at 13:55, Charlse Darwin wrote: > >> $ sudo port -f clean --dist --archive --work ocmal >> Error: Port ocmal not found > > It's called ocaml... > >> $ sudo port -d sync >> DEBUG: Synchronizing ports tree(s) >> Synchronizing local ports tree from rsync://rsync.macports.org/ >> release/ports/ >> DEBUG: /usr/bin/rsync -rtzv --delete-after rsync:// >> rsync.macports.org/release/ports/ /opt/local/var/macports/sources/ >> rsync.macports.org/release/ports >> receiving file list ... done >> archivers/bzip2/ >> devel/apr/ >> devel/apr-util/ >> devel/atk/ >> graphics/ImageMagick/ >> graphics/cairo/ >> net/bmon/ >> net/bwm-ng/ >> net/curl/ >> shells/bash/ >> textproc/aspell/ >> www/apache2/ >> x11/Xft2/ >> >> sent 74 bytes received 292538 bytes 16720.69 bytes/sec >> total size is 16277463 speedup is 55.63 >> $ sudo port -f install ocmal >> Error: Port ocmal not found > > Still called ocaml... > >> $ sudo port -f install ocaml >> ---> Fetching ocaml >> ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// >> caml.inria.fr/pub/distrib/ocaml-3.10/ >> ---> Verifying checksum(s) for ocaml >> ---> Extracting ocaml >> ---> Configuring ocaml >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang >> _ocaml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk >> " returned error 2 >> Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) >> not balanced >> ../gnu/config.sub: line 128: [: !=: unary operator expected >> Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not >> recognized >> Please specify the correct host type with the -host option >> >> Error: Status 1 encountered during processing. >> $ >> >> # where do I get the fixed version from? > > As you see from the output of "port sync" above, you did not > receive an updated portfile for ocaml. You need to wait 30 minutes > after a commit is made to the repository before it shows up on the > rsync server. > > However, the errors you are experiencing are different from the > errors reported in the ticket. The errors you are experiencing may > be related to your experiments in installing a new xnu kernel. You > may need to reinstall Xcode or Mac OS X to resolve those issues. > > But first, let's start with your sed. There's nothing that I can > see that's wrong with "s/-[^-]*$//"; looks perfectly balanced to > me. What can you tell me about your sed? Here's info about mine, > from my MacBook Pro running 10.4.11: > > $ ls -l /usr/bin/sed > -r-xr-xr-x 1 root wheel 68388 Dec 7 2006 /usr/bin/sed > $ file /usr/bin/sed > /usr/bin/sed: Mach-O universal binary with 2 architectures > /usr/bin/sed (for architecture i386): Mach-O executable i386 > /usr/bin/sed (for architecture ppc): Mach-O executable ppc > $ > > Your info will be different because you're on PowerPC but I'm > curious to see if it has about the same modification date > (indicating it's from Apple), or if it's newer (indicating it was > replaced with something else at some point). >

2 3

sudo port install mldonkey
by Charlse Darwin 04 Jan '08

04 Jan '08

$ sudo port -f clean --dist --archive --work ocmal Error: Port ocmal not found $ sudo port -d sync DEBUG: Synchronizing ports tree(s) Synchronizing local ports tree from rsync://rsync.macports.org/ release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/ release/ports/ /opt/local/var/macports/sources/rsync.macports.org/ release/ports receiving file list ... done archivers/bzip2/ devel/apr/ devel/apr-util/ devel/atk/ graphics/ImageMagick/ graphics/cairo/ net/bmon/ net/bwm-ng/ net/curl/ shells/bash/ textproc/aspell/ www/apache2/ x11/Xft2/ sent 74 bytes received 292538 bytes 16720.69 bytes/sec total size is 16277463 speedup is 55.63 $ sudo port -f install ocmal Error: Port ocmal not found $ sudo port -f install ocaml ---> Fetching ocaml ---> Attempting to fetch ocaml-3.10.0.tar.bz2 from http:// caml.inria.fr/pub/distrib/ocaml-3.10/ ---> Verifying checksum(s) for ocaml ---> Extracting ocaml ---> Configuring ocaml Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_oc aml/work/ocaml-3.10.0" && ./configure -prefix /opt/local -no-tk " returned error 2 Command output: sed: 1: "s/-[^-]*$//": RE error: brackets ([ ]) not balanced ../gnu/config.sub: line 128: [: !=: unary operator expected Invalid configuration `powerpc-apple-darwin8.11.0': machine `' not recognized Please specify the correct host type with the -host option Error: Status 1 encountered during processing. $ # where do I get the fixed version from? Begin forwarded message: > From: "MacPorts" <trac(a)macosforge.org> > Date: January 4, 2008 2:17:32 PM EST (CA) > To: ryandesign(a)macports.org, pguyot(a)kallisys.net > Cc: macports-tickets(a)lists.macosforge.org, bfulgham(a)macports.org, > ajmas(a)sympatico.ca, macports.users(a)gmail.com > Subject: Re: [MacPorts] #13583: ocaml 3.10.0 build failure on > Tiger: 'struct mcontext' has no member named '__ss' > Reply-To: noreply(a)macosforge.org > > #13583: ocaml 3.10.0 build failure on Tiger: 'struct mcontext' has > no member named > '__ss' > -------------------------------------- > +------------------------------------- > Reporter: ryandesign(a)macports.org | Owner: > pguyot(a)kallisys.net > Type: defect | Status: closed > Priority: Normal | Milestone: Port Bugs > Component: ports | Version: 1.7.0 > Resolution: fixed | Keywords: > -------------------------------------- > +------------------------------------- > Changes (by ryandesign(a)macports.org) > > * status: new => closed > * resolution: => fixed > > Comment: > > Since the maintainer is not responding, I'll deal with this. > > r31240 broke ocaml. When the patch was originally attached to ticket > #13308, the patchfiles were wrapped in a "`platform darwin 9`" > section, > but as committed, the patchfiles apply on all platforms. I am > changing > this in r32486 so that the patchfiles only apply on darwin 9, so > that it > builds again on earlier systems. > > -- > Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/ > 13583#comment:3> > MacPorts </projects/macports> > Ports system for Mac OS

3 2

Re: $ sudo port -f install MacPorts
by Ryan Schmidt 04 Jan '08

04 Jan '08

On Jan 4, 2008, at 08:10, Charlse Darwin wrote: > On Jan 3, 2008, at 11:41 PM, Ryan Schmidt wrote: > >> On Jan 3, 2008, at 22:26, Charlse Darwin wrote: >> >>> On Jan 3, 2008, at 11:18 PM, Ryan Schmidt wrote: >>> >>>> On Jan 3, 2008, at 22:11, Charlse Darwin wrote: >>>> >>>>> `Command output: configure: error: cannot run /bin/sh ./ >>>>> config.sub' shows up in every port that I'm trying to install, >>>>> I just though reinstalling MacPorts might help. >>>> >>>> Oh, I didn't realize that. Well that certainly shouldn't be. >>>> >>>> Reinstalling MacPorts might help. But I don't think installing >>>> the port called MacPorts is the way to do that. At least, that's >>>> not documented anywhere. >>> >>> It all happened after I started playing with xnu (darwin_9, uname >>> -r on my machine returns 8.11.0) >>> I have tried installing MacPorts from this package >>> http://svn.macports.org/repository/macports/downloads/ >>> MacPorts-1.6.0/MacPorts-1.6.0-10.4-Tiger.dmg >>> >>> but it failed. I'm thinking maybe I should reinstalling the Xcode >>> too… >> >> XNU is the Mac OS X kernel, yes? What do you mean, playing with >> it? You are running Tiger? If so, what did you mean when you said >> "darwin_9"? In what way did installing MacPorts 1.6.0 from the >> Tiger disk image fail? If you're on Tiger, reinstalling Xcode 2.5 >> couldn't hurt. > > Yes I meant XNU the kernel of Mac OS X and I am running Tiger > (darwin_8.11.0). Days ago I tried to build and install the new > version of kernel from source code <http://www.opensource.apple.com/ > darwinsource/Current/> which failed. Somewhere along I must have > messed up something because after that I kept getting this error > message: > "Command output: configure: error: cannot run /bin/sh ./config.sub" > for almost every port I'm trying to install It does sound messed up. You could try reinstalling Xcode, or you may have to reinstall Mac OS X. Unless there's a config.log file you could look at that suggests a different course of action. But you definitely need to solve this general inability to build things before we tackle any port-specific problems.

1 0