Hi David,
why does libepoxy need all these xorg deps:
---
$ sudo port install libepoxy
Password:
---> Computing dependencies for libepoxy
---> Dependencies to be installed: mesa xorg-dri2proto xorg-glproto
xorg-libXfixes xorg-fixesproto xorg-xextproto xorg-libXi xorg-inputproto
xorg-libXext xo
On Jan 14, 2015, at 8:53 AM, René J.V. Bertin wrote:
>
> It's been a while since I installed MacPorts from scratch, and I don't think
> it ever actually modified my startup script, but in principle you only need
> to add /opt/local/bin (or ${prefix}/bin) to your path.
If you use the binary Mac
On Thu, Jan 15, 2015 at 12:30 AM, Lawrence Velázquez wrote:
> On Jan 14, 2015, at 5:36 AM, Mojca Miklavec wrote:
>
>> a) install binutils (easy)
>> b) install headers (easy)
>> c) build gcc ("make [install] all-gcc" from GCC sources)
>> d) build crt (requires gcc)
>> e) build libgcc from gcc source
On Jan 14, 2015, at 5:36 AM, Mojca Miklavec wrote:
> a) install binutils (easy)
> b) install headers (easy)
> c) build gcc ("make [install] all-gcc" from GCC sources)
> d) build crt (requires gcc)
> e) build libgcc from gcc sources ("make [install] all-target-libgcc"
> from GCC sources)
> f) buil
On Jan 14, 2015, at 2:47 PM, Lawrence Velázquez wrote:
> you cannot deactivate or install llvm-X.Y.
*deactivate or uninstall
vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Jan 14, 2015, at 2:30 PM, René J.V. Bertin wrote:
> Unless I misunderstand you, that doesn't make them dependent on LLVM. They
> just cannot run what's not installed :)
Are we still talking about MacPorts here? MacPorts enforces runtime
dependencies; if you have cctools +llvmXY or ld64 +llv
Is there any reason that the configure.env variables are automatically
copied to the build and destroot phases?
I ask because most python packages do not use the traditional
'./configure; make; make install' method and instead set things like the
prefix and whatnot in the build or destroot phase.
On Jan 13, 2015, at 4:33 AM, René J.V. Bertin wrote:
> IIRC they only depend on llvm for building.
No, both require LLVM at runtime (when the pertinent variants are selected).
vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://
On Jan 12, 2015, at 10:38 PM, Takeshi Enomoto wrote:
>> 7) Rebuild llvm-3.4 and clang-3.4 to use libc++, using clang-3.5:
>>sudo port -v install clang-3.5
>>sudo port -v uninstall llvm-3.4 clang-3.4
>>sudo port -v install clang-3.4 configure.compiler=macports-clang-3.5
>
On Jan 14, 2015, at 6:53 AM, René J.V. Bertin wrote:
> On Wednesday January 14 2015 14:44:12 Jeremy Whiting wrote:
>> Jeremy Whiting has posted comments on this change.
>
> Jeremy, could you summarise the changes please?
>
>>
>> Change subject: QStandardPaths: Add XDG_CONFIG_DIRS and XDG_DATA
On Wednesday January 14 2015 13:06:01 Mojca Miklavec wrote:
> There might be one, but that doesn't really help us to make the
> package(s).
To be very honest, I seem to recall that the script kind of makes packaging
unnecessary because it downloads everything required without doing (too many)
On Wednesday January 14 2015 14:44:12 Jeremy Whiting wrote:
> Jeremy Whiting has posted comments on this change.
Jeremy, could you summarise the changes please?
>
> Change subject: QStandardPaths: Add XDG_CONFIG_DIRS and XDG_DATA_DIRS paths
> on OSX.
> ..
On Wed, Jan 14, 2015 at 11:55 AM, René J.V. wrote:
> Hi,
>
> Good idea(s) ... but not easy indeed.
>
> Isn't there a script that automates the process?
There might be one, but that doesn't really help us to make the
package(s). It is helpful for the creator of the Portfile to know
which steps are
Hi,
Seeing the instructions about compiling clang-3.5 on Leopard in
several stages reminded me on another project that is lagging behind –
MinGW-w64
http://trac.macports.org/ticket/40174
http://trac.macports.org/browser/users/mojca/ports/cross
The ports for mingw that are currently in Mac
On Wed, Jan 14, 2015 at 10:00 AM, Ryan Schmidt wrote:
> On Jan 14, 2015, at 02:42, Mojca Miklavec wrote:
>>
>> I've seen the following spam being added to the trac:
>>
>> https://trac.macports.org/ticket/46455#comment:9
>> https://trac.macports.org/ticket/46315#comment:3
>> https://trac.macports.or
On Jan 14, 2015, at 02:42, Mojca Miklavec wrote:
>
> I've seen the following spam being added to the trac:
>
> https://trac.macports.org/ticket/46455#comment:9
> https://trac.macports.org/ticket/46315#comment:3
> https://trac.macports.org/ticket/43859#comment:9
>
> This was just for the tickets
Hi,
I've seen the following spam being added to the trac:
https://trac.macports.org/ticket/46455#comment:9
https://trac.macports.org/ticket/46315#comment:3
https://trac.macports.org/ticket/43859#comment:9
This was just for the tickets I was following myself; there might be
other posts of the sam
17 matches
Mail list logo
