James Linder wrote:
>> "In general, application bugs should be reported to the developers of the
>> app (?upstream?), not MacPorts."
>> But I think it's safe to say that no-one* is running Xfce on Darwin/XQuartz,
>> so this is Terra Incognita...
>>
>> Anyway, the bug tracker is:
Pierre Henri CHAUDOUARD wrote:
> What is the role of xfce4-session ? Because other components (xfwm4, panel,
> desktop) seem to work ...
>
>>> /opt/local/etc/xdg/xfce4/xinitrc: line 113: 13661 Segmentation fault: 11
>>> xfce4-session
>>>
>> This segfault needs to be debugged by someone.
Ryan Schmidt wrote:
>>> Now the installation fails at xfconf:
>>> :info:configure checking for XML::Parser... configure: error: XML::Parser
>>> perl module is required for intltool
>>
>> Hmm, that part should probably be removed (as per
>> https://trac.macports.org/ticket/30937)
>>
>>
Pierre Henri CHAUDOUARD:
> Ok, now I have installed xfce (not without pain ...). But it fails to launch
> ...
>
> /opt/local/bin/startxfce4: X server already running on display :0
Weird that this doesn't seem to be using launchd, but whatever. Maybe it
changed ?
>
6 jan 2016 kl. 21.03 skrev Pierre Henri CHAUDOUARD:
> Now the installation fails at xfconf:
> :info:configure checking for XML::Parser... configure: error: XML::Parser
> perl module is required for intltool
Hmm, that part should probably be removed (as per
4 jan 2016 kl. 22.21 skrev Pierre Henri CHAUDOUARD:
>
>> Anyway, now the ports *have* been updated to the latest version Xfce 4.12 so
>> "should" work.
>> This includes the desktop, with Thunar and Terminal. See screenshot from
>> XQuartz on Mavericks:
>>
> Thank you for the upgrade ! I was
3 jan 2016 kl. 01.35 skrev David Evans:
> On 1/2/16 6:25 AM, Pierre Henri CHAUDOUARD wrote:
>> OS X 10.11.2, Xcode 7.2.
>>
>> Has anyone managed to install xfce ? For me, the installation fails at the
>> package xfconf ...
The old ports for Xfce 4.6 and the (unreleased) Xfce 4.8 hadn't been
Darren Weber:
Is there a general consensus, for the majority of ports without any
specific build dependency, on which version of gcc is preferred or
recommended for MacPorts?
I'd go with /usr/bin/gcc, as a generic recommendation.
(whether using MacPorts or just general on Mac OS X...)
It
Rainer Müller wrote:
For one
thing, if you are running on Mac OS X you are not running on pure
darwin;
ah ?
i thought that pure darwin was the UNIX layer under the GUI, not
only the OS for those who don't have GUI at all
No, puredarwin is http://puredarwin.org.
The +puredarwin variant
Ryan Schmidt wrote:
Note that libGLEW.a is a static library. I'm not aware of how to
determine what architectures a static library is built for. Usually
you would be using a dynamic library, like libGLEW.dylib, for which
the file command should verify its architectures.
lipo -info
It's
Scott Haneda wrote:
http://trac.macports.org/wiki/howto/MAMP
The section where the docs state:
In /opt/local/apache2/conf/extra/httpd-userdir.conf, add the
following lines to the end of the file:
# # Include user configurations # Include /private/etc/httpd/users/
*.conf
The include path
Ryan Schmidt wrote:
Error: Target org.macports.configure returned: error copying /opt/
local/share/libtool/config.guess: no such file or directory
Fixed in r49032, thanks.
Darnit, thought that changing the /usr into ${prefix} would have been
enough to escape the Xcode 2.5 bugs...
Guess
Ryan Schmidt wrote:
Guess life isn't that simple. So, does this mean that the silly
thing works on Leopard now ? (without sound)
Works for me, on Tiger and Leopard (both on Intel, both without
sound).
Cool! That'd have to be a _really_ rainy day, completing that sound
server...
Scott Heftler wrote:
b6$ sudo port install xgalaga
--- Building xgalaga
In file included from data.c:19:
data.h:69: error: array type has incomplete element type
data.h:72: error: array type has incomplete element type
Any ideas?
That's not really bizarre, it's just missing an
Scott Heftler wrote:
Ported most of the fixes over from Fink, but it wasn't
much fun without the sound anyway so I didn't post it.
Suppose I could, if anyone would find it interesting...
So all I have to do is have MacPorts port the missing header file?
It should be working with revision
Scott Heftler wrote:
It should be working with revision 1. On Tiger's X11, anyway.
Feel free to test it on Leopard, and get the sound working
I'm running Leopard. What package do I need to port now?
I did port search data and got nothing. Do I need to go to
the Find site and look around
Darren Weber wrote:
I've been working with macports under the mis-apprehension that it
would operate along the lines of freeBSD (and some frustration may
arise mostly from that lack of understanding). I decided that it's
time for me to do some long-overdue homework. I've been working
Darren Weber wrote:
This suggestion may be too complicated, but it's a thought.
Suppose it is possible to create a virtual machine or some kind
of encapsulated clean environment (perhaps like a java sdk or
something), which can contain any of the environments for OSX
(10.x), or at least
Ryan Schmidt wrote:
* I was under the impression Mac Ports was sort of to replace
Fink, is that not the case? What are the pros and cons,
differences? Is Fink still active?
Fink and MacPorts are both package management systems for Mac OS X.
I myself switched from Fink to what is now
Emmanuel Hainry wrote:
The dependency does not need to be in the package, it is already in
the
Portfiles.
Actually, it does... But currently it just includes the
entire Portfile into the archive, which is rather hacky.
Or at least it would be nice to not require a Tcl parser
in order to
Joshua Root wrote:
One problem with the current system is that the archives
are sorted by OS and Arch, but not including OS version.
That is, the binaries for Tiger and Leopard would go to
the same file path - unless having a platform variant...
It also needs digests (e.g. SHA) and signatures
Brian Forte wrote:
At risk of igniting an argument I believe it's worth noting there
are two active RPM projects.
There are probably better places to pick RPM fights, than on MacPorts...
The [RPM 4.x project][1] is maintained by Panu Matilainen, who
works for Red Hat. The [RPM 5.x
Alexy Khrabrov wrote:
It turns out RPM works fine on Mac:
http://rpm4darwin.sourceforge.net/
There's also a couple of RPM ports in MacPorts, and a port rpm target
to package any port up as a binary package or port srpm for source
rpm.
See http://guide.macports.org/#using.binaries
The
Ryan Schmidt:
In fact I can't imagine there being another Tcl-based MacPorts
client. The port command handles most of what a user would need
in a command line client, and if someone were making a GUI for
MacPorts, I doubt they would do so in Tcl.
PortAuthority (formerly known as dpgui)
Joe VanAndel wrote:
Thanks, I was missing the install of the lzmautils package, which
installed /opt/local/bin/lzma. The 'lzma' package installs
/opt/local/bin/lzma_alone, which I had linked to /opt/local/bin/lzma,
by mistake.
That is not correct, as they (unfortunately) use different
Chris Jones wrote:
Slightly OT, but what packages can be installed on the mac using
dpkg ?
Fink ones ? MacPorts has better support for RPM than what it does for
DEB.
--anders
___
macports-users mailing list
macports-users@lists.macosforge.org
Charles Day wrote:
... it just appears that
relatively few people care about building binaries.
Maybe not too many care about building them, but a lot care about
distributing them once they are built. A distribution of GnuCash
for Mac in binary form is one of the more requested features
Joshua Root wrote:
Given that this has been around for 2 years, is this considered a
bug
or a feature?
Heh, there are bugs that have been around longer... it just appears
that
relatively few people care about building binaries.
Was referring to
Charles Day wrote:
Well I tried the following workaround for ticket 10881, but
macports started trying to include the wrong dependencies. For
example, it tried to include dependencies based on X11 when I
specified gnucash +no_x11 (see gnome-desktop at the end as an
example).
In
Joshua Root wrote:
DEBUG: Calling
/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/
PackageMaker
for gnucash pkg
Warning: Unknown argument: -AppleLanguages
Warning: Unknown argument: (English)
It is the same error I checked the the Apple docs on
Packagmaker.app and
they
Max Asato wrote:
This thread got a bit fragmented so I'll restate this particular
problem.
Sorry about the length of this posting.
I had created a binary archive on one system and copied the archive
to another system in the hopes that I could install the binaries
directly and avoid a second
Max Asato wrote:
Last but not least, is there any way to get MacPorts to install
packages
from a port archive file that was built on another system? I've
set the
portarchivemode parameter in macports.conf on two intel Macs (both
running 10.4.11), built a package on one and copied the
Tim Visher wrote:
I'd be interested in generating a complete list of all software I have
installed through MacPorts so that I don't have to back up my
installation in case of a hard drive failure. Basic use case would be
that if my disk fails, I just download MacPorts again, and then run
this
Braden McDaniel:
Normally this is handled by `sdl-config`, not so with Xcode.
Ah, you mean if I'm using libsdl (i.e., not the framework variant).
Yup. (gcc -o foo `sdl-config --cflags --libs` foo.c)
Using frameworks outside of Xcode.app usually lands in unsupported,
i.e. most setups are
Braden McDaniel wrote:
Is MacPorts' libsdl-framework usable directly from C and C++, or do
I need an Objective-C entry point as described here?
http://www.libsdl.org/faq.php?action=listentriescategory=7#55
For Cocoa backend with SDL 1.2 you need a SDLMain entry point.
Normally this is
Akim Demaille wrote:
Really, I just wish I had a simple means (= not by having to
specify it on each port command line) to specify CC and CXX. Or
else, I would prefer that the hard coded values be fully qualified
(/usr/bin/i686-apple-darwin9-gcc-4.0.1) instead of short (/usr/bin/
Akim Demaille wrote:
Ah, OK, didn't think about that, thanks! Then in that case I
suppose that there are means to tell /usr/bin/gcc-4.0 what arch I'm
aiming for (686, ppc, or universal). I suppose via something like -
march. In which case, it's even better than using the fully
Akim Demaille wrote:
Thank you, but there seems to be some misunderstanding here: I am
not asking for help on how I should talk to GCC, but rather how I
should tell macports to use the compiler in a more useful way. I
do think that rather than leaving gcc-4.0 what's to be done,
macports
Bryan Blackburn wrote:
Can you elaborate a little on this, I am not sure I understand
what you
mean. What would you suggest I do? I already have ASSP running
via hand
compile, but wanted to use this as a way to possibly supply a working
install back to the community. Same with mrtg as
IT wrote:
I have installed pdftk Macport in my administrator computer. Now i
want to deploy the binaries and all related files to run pdftk on
20 networked macs without copying all /opt directory. Please,
anybody can advice me about the best way to deploy a MacPort from
the administrator
Marcus Bointon wrote:
I don't see why it should be looking in the current dir to upgrade
outdated packages anyway, and it's obviously not having any trouble
finding the portfiles in the normal install location. Is it that
'outdated' resolves to ''?
Just sounds like a bug in MacPorts
Olaf Foellinger:
The package could not be created because of the following errors:
Root directory
/opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome
_gnucash/work/destroot
is not valid.
I wanted to ask what's the current status of these
David Epstein wrote:
My error message must have been dealt with somewhere in the list,
possibly
many times, but I haven't been able to find it. I was trying to
install
gimp:
sudo port install gimp
Eventually I got the error message
Target org.macports.configure returned: pango 1.22.0
Ryan Schmidt wrote:
I really don't want to have to build or use a bootstrapped GCC, X11
and all to have a self-contained MacPorts installation.
Also, don't forget that only Apple's gcc installed with Xcode can
create universal binaries in one step (with e.g. -arch i386 -arch
ppc), which
Ryan Schmidt wrote:
Well, then my next complaint would be with a bootstrapped X11.
Apple X11 seems nice enough, but when I tried XFree86 it was
totally ugly (weird non-Mac-like cursor and window behavior, etc.)
I didn't try xorg, and I don't know if sources for Apple X11 are
Ryan Schmidt wrote:
As long as MacPorts builds ports from source, then Xcode is an
absolute
requirement (for gcc etc). If the day comes that MacPorts
distributes
binary packages, then Xcode may only be needed by some ports and not
MacPorts as a whole.
As a guess, the macports
nox wrote:
One reason could be to keep MacPorts fully self-contained,
and to cut down on the amount of outside dependencies... ?
Currently there is a big grey zone of what's ok to use from
system (GCC, X11, etc) and what is not (Perl, Python, etc)
I really don't want to have to build or use
Julio Biason wrote:
Perhaps we should send out some sort of announcement calling formally
for volunteers for the position?
Oh, what the hell, I have plenty of time these days. What should a
Release Manager do?
There's a summary of some of the things that needs to be done at:
Benedick Miller wrote:
then this one looks good:
http://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail
Good luck.
Thanks for the tip, however that is where I started! Sep 1 is sudo
port install gnome.
As this doesn't work I am a bit disspaointed in macports!
GNOME isn't being maintained at
Ryan Schmidt wrote:
However, the missing _jas_whatever symbols from your second message
is a mystery to me so someone with knowledge of gtk and jasper will
have to look into that. I'm hoping Anthony will have some idea, or
know where to ask for help.
Seems to be fallout for doing the major
Normen Müller wrote:
Seems to be fallout for doing the major upgrade GTK 2.12 to 2.14
and enabling jasper (JPEG200) in the process. Trying to sort out...
http://trac.macports.org/ticket/16685 (r40275)
http://trac.macports.org/ticket/16689
I am sorry, but I am not sure if I understood you
Normen Müller wrote:
you trying to fix this?
Well, you can downgrade to 2.12 again while it is being fixed...
Either that, or take out port:jasper and add --without-libjasper
--anders
As I am still a newbie to macports, I will just wait for the fix,
cause I guess your suggested
Normen Müller wrote:
The building of GTK+ 2.14 has been fixed in revision 2.
You will still get activation problems with conflicts
against the gail port, but that is expected since
gail has now been included in gtk2. This is the same as:
http://trac.macports.org/ticket/16688 (for +quartz)
Martin Krischik wrote:
He said it was 13MB. So my guess is that some script did a
cp foo /usr/local
expected that /usr/local already existed as a directory.
This is why the --target-directory was invented (at least for gnu's
cp). Very helpful for scripts. Also very helpful is setopt
Jay Levitt wrote:
I have a developer who lives in a rural area, with no broadband
access.
(OK, stop laughing.) Worse, his 28.8K dialup ISP has an 8-hour max
session time, so anything signifcantly large just can't be downloaded,
period.
I want to send him a DVD-ROM of some large
Harry van der Wolf wrote:
I'm currently on Tiger but I'm planning to move to Leopard. I build
bundles for 2 open source projects currently by hand compiling
almost every library as universal. I'm trying to move to MacPorts
as that's much simpler and MacPorts has much improved in the
Ryan Schmidt wrote:
Theoretically +universal should be able to handle this,
but cross-compiling isn't really supported in MacPorts.
Yeah. So why did we expose the options in macports.conf again? :)
We were trying some stuff out in trunk, when somebody (ehrm) said
you can't do things in code
Ryan Schmidt wrote:
Theoretically +universal should be able to handle this,
but cross-compiling isn't really supported in MacPorts.
Yeah. So why did we expose the options in macports.conf again? :)
Note that macports.conf in trunk has some more features...
(which still isn't supported, but
Simon Wheatley wrote:
Is it possible to point MacPorts at a downloaded package of some
kind and say install that? Something similar to Debian's 'dpkg -i'?
Not at the moment... You can build a package (pkg/rpm/deb), but then
it doesn't integrate with the already installed ports and registry
Ryan Schmidt wrote:
We can't use 'array unset env' as that is documented to disconnect
Tcl from the environment, and some messing around hasn't shown a
clean way to work around this. Maybe a Tcl expert is needed, and
determining if this is Mac-specific or 8.4.7; of course, either
way,
Mikael wrote:
I'm a complete newbie to compiling binaries, and UNIX for that
matter, so please forgive me for any ignorant questions. I'm
hoping to use MacPorts to compile binary packages that can be
distributed and installed on other computers. I've been practicing
with hexedit.
Michael Franz wrote:
I am trying to use macport to build and install macports. I used
sudo port -v build macports and get build errors. I find this
strange since if I just download the source and compile with the
instructions on the website it works without a problem.
cc -dynamiclib
Emil Lundberg wrote:
Still failing to get 64-bit MacPorts to work properly, I though I'd
relay my progress so far. The short story is some ports do not
compile properly as ppc64. Others do, but don't compile properly on
x86_64. I'm prepared, of course, to notify the individual
Michael Franz:
Also, which is better to use:
lib:libX11:XFree86 or
port:xorg-libX11 ?
The first version is better (lib:), because then one can use
a system version of X11 (such as Apple's X11.app) instead of
having to install either of the XFree86 or xorg* ports...
Currently GCC and X11 are
Alejandro Aragon wrote:
I was trying to build pidgin, and when compiling gtk2 I had the
following error:
i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXrandr.2.0.0.dylib: No
such file or directory
make[4]: *** [libgdk-x11-2.0.la] Error 1
I'm new to Mac OS so I was wondering why this
kevin kempter wrote:
i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXrandr.2.0.0.dylib: No
such file or directory
make[4]: *** [libgdk-x11-2.0.la] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Error:
Ryan Schmidt wrote:
and as a hint, if you install BBedit's command line tools, you can
simply type edit filename instead of all that other stuff. Or use
TextWrangler, for those who are short of coin. It has the same
facility.
BBEdit's command line tools are called bbedit and bbdiff.
Frank Schima wrote:
I'm having a problem running livecheck without sudo:
$ port livecheck blt
Error: Unable to execute port: /opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_x11_blt/work/.macports.blt.state is not
writable - check permission
Jordan K. Hubbard wrote:
Before fetching all the files, it would probably nice to fix the
timestamps so that they correctly reflect the upstream distfile ?
I guess I'm missing something. Why is this important? Distfiles
are essentially opaque to the MacPorts user, so what would be the
Jordan K. Hubbard wrote:
I fail to understand this stubborn insistence on date stamp and group
information for files which are simply not meant to be user visible.
There is no group information you need to see on the distfile mirror
because you won't be managing the distfile mirror.
I worked
Ryan Schmidt wrote:
On Feb 23, 2008, at 03:38, Brent Austin wrote:
When I try to build apr I get the following:
In file included from misc/unix/rand.c:39:
/opt/local/include/uuid.h:94: error: conflicting types for 'uuid_t'
/usr/include/unistd.h:121: error: previous declaration of 'uuid_t'
Wes James wrote:
On Thu, Feb 21, 2008 at 7:29 PM, Rainer Müller
[EMAIL PROTECTED] wrote:
Wes James wrote:
I'm trying to find the config file in macports to change the CC and
CXX default parameters that configure uses when it is run on each
package. Can someone help me with this.
Not
Jordan K. Hubbard wrote:
On Feb 22, 2008, at 7:11 PM, Rainer Müller wrote:
One of these things would be how we would push files on the mirror?
If we keep master_sites we could use something like `port fetch all'
in a cronjob or in a post-commit hook. But that will have the
problem that it
Jordan K. Hubbard wrote:
This topic was, in any case, hashed out rather thoroughly back when
the project changed its name from DarwinPorts to MacPorts. GIven
the plethora of projects already devoted to multi-platform ports
collections (portage, pkgsrc, etc) and the relative shortage
Rainer Müller wrote:
Paths in /etc/manpaths.d and /etc/paths.d are always added at the
end of MANPATH and PATH. Therefore, installs by MacPorts will not
override the default Mac OS X installation. As it is not possible
to prepend new paths, this option is rather useless for us.
I think
Zak Mc Kracken wrote:
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
This problem is since the change to /usr/bin/gcc-4.0 for CC.
Switching compiler back to gcc (or gcc-4.0) makes it work.
Something like: port build configure.cc=gcc
Ryan Schmidt wrote:
I think the change was made for 1.5.1.
I thought the change was made for 1.6.0?
http://trac.macports.org/projects/macports/changeset/27018
Doesn't matter...
--anders
___
macports-users mailing list
paul beard wrote:
Looks like I have some problem with libtool.
libIDL and Apache2 both fail to upgrade.
...
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
This problem is since the change to /usr/bin/gcc-4.0 for CC.
Switching compiler
Ryan Schmidt wrote:
Ryan As ports are tested, use_parallel_build yes is added to
the
Ryan portfile. Then MacPorts will build those ports using -j$jobs
Ryan (where $jobs is the number of CPU cores in your computer).
This
Ryan was added for MacPorts 1.6.
Excellent, thanks.
Alistair Gallworthy wrote:
Is it possible to install both MacPorts and fink and run them
side-by-side without conflict?
Yes, but it is not the default mode of installation...
(i.e. you need to modify the default configuration)
For instance, I know that both systems install their own
Ryan Schmidt wrote:
On Jan 11, 2008, at 10:52, William Gallafent wrote:
On 11 Jan 2008, at 16:44, William Gallafent wrote:
--- Applying patches to libsdl
Error: Target org.macports.patch returned: shell command cd
/opt/local/var/macports/build/
J.D. Merrick wrote:
When installing Xcode 3.0 on Leopard, by default Unix developer
support is disabled. That is, by default the command line tools (gcc,
ld, etc.) are installed in /Developer without adding to the boot
volume symlinks to the tools in /usr/bin or to the header files in
LeAnne Lis wrote:
I am trying to install frozenbubble2, and I got additional errors
after that
with similar messages. Each time I encountered an error, I tried
uninstalling the error'd item, then reinstalling the port and its
dependencies with +universal, and then it worked, so I have
Boey Maun Suang wrote:
As for the compatibility of code built with Xcode 2.5 with that built
with
Xcode 2.2.1, I think that they should be largely compatible, as my
reading
of the release notes from 2.2.1 to 2.5 is that there have only been
bugfixes and feature enhancements to Xcode's GCC in
Also, the portfile for grace has the following dependency line:
depends_lib lib:libX11.6:XFree86 \
X11 for Leopard provide X11R7 (instead of 6) and is based on xorg, not
XFree86. But, I know that macports grace works in Leopard. So I'm
wondering, how exactly is that line parsed?
John Lauck wrote:
While I was debugging a perl script and installing various cpan
modules I noticed I had both perl5.8 and 5.9 installed. Both were
marked as active but perl5.8 was linked to /opt/local/bin/perl. I
decided to deactivate perl5.8 , deactivate perl5.9 and then reactivate
Ryan Schmidt wrote:
On Nov 19, 2007, at 14:02, Weissmann Markus wrote:
10.3 is not officially supported anymore*) and I do not even have
access to a 10.3 box.
This is the first I've heard of 10.3 not being supported anymore.
Historically MacPorts has supported the current Mac OS X release
Joel Thibault wrote:
Cool! When do you expect (or estimate) release 1.6 will be available?
Is there a roadmap or other document available showing milestones such
as these?
The milestones are in Trac, but jmpp hasn't got around to defining 1.6
yet...
Parallell builds are an optional feature, and will never be disabled
by default.
*enabled* by default, darnit.
--anders
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
David Corking wrote:
I posted a bug report about Xcode Find (in a file versus in a
project) and
the developers said it should be fixed in Xcode 3.0.
I think you will find the IDE portion of Xcode is closed source. If
the bug is in the IDE, and
Apple don't backport it themselves, you are out
I'd rather encourage a mechanism for port that provides a mechanism
for port authors to know how many processors there are and to enable
parallel builds if they know this to work.
Perhaps a switch use_parallel_build [yes|no] that will add -j
2*CPUS to build.args.
There's a bunch of other
Weissmann Markus:
Yes, but I meant this to be a per-Portfile choice so a maintainer can
mark his/her port as being able to build in parallel. Doing this with
the sledgehammer for all ports that use 'make' might be a bit too
much. ;)
It is supposed to be the default... But broken ports might
David Orriss Jr wrote:
I'm really having fights with GIMP 2.4 getting it to run... I get
errors with the tiff libraries..
See http://trac.macports.org/projects/macports/ticket/12997
--anders
___
macports-users mailing list
js wrote:
http://www.macosxhints.com/article.php?story=20070524074057479
From this article, I learned how we can easily speed up build phase
of MacPorts.
Can I make this behavior (-j) default for all ports using make?
In MacPorts 1.6, you can set the -j parameter with build.jobs.
( see
Juan Manuel Palacios wrote:
2) Once the build product, the destroot, is done and considered
reliable, packaging it into, say, an rpm and/or a deb package is a
completely different topic, with its own intricacies and integration
issues between MacPorts and the packaging format we still need to
js wrote:
Note that some ports will fail to build, when using make -j 2
What causes the build erorr? is it for bad Makefile or problem of -j
option itself?
Bad makefiles, usually missing dependencies.
--anders
___
macports-users mailing list
paul beard wrote:
Is there a status document that addresses where things stand on
efforts like this? I haven't been all that successful at building
packages within port (port pkg foo where foo is something i would
rather not build again on a second machine). I think I may have
resorted to
paul beard wrote:
I missed something in my previous post: the directory for the port had
been cleaned, and apparently the pkg command doesn't expect that, nor
does it know what to do about it. So it bails.
If you build first, than issue the pkg command, it does work, as best
I can tell.
CHENG Gao wrote:
Another example is apple-gcc. Tree has apple-gcc33 build 1819, and
apple-gcc40 build 5363, while latest Tiger 10.4.10 has build 5367.
Should they be updated? Or even apple-gcc33 be removed?
Apple has not released the source code for Mac OS X 10.4.10 or
Xcode 2.4.1 (only
Jochen Küpper wrote:
On 14.10.2007, at 10:51, Randall Wood wrote:
The Mozilla port is outdated, and the Mozilla package is no longer
(officially) maintained upstream.[1]
Maybe the port should be removed then?
I am replacing the mozilla port with a seamonkey one,
but it isn't done yet. Use
1 - 100 of 118 matches
Mail list logo
