On Jun 11, 2009, at 06:54, Thomas De Contes wrote:
Le 11 juin 09 à 06:51, Ryan Schmidt a écrit :
Well, a user who types sudo port selfupdate causes MacPorts to
build itself from source...
yes but in a closed environement (for example i suppose that PATH
is replaced by binpath), like for
Le 30 mai 09 à 17:40, Rainer Müller a écrit :
On 2009-05-30 17:12, Thomas De Contes wrote:
[...]
... i don't understand why you prefer (1) for MacPorts itself
since Ryan Schmidt uses (2) for ports, i don't see what kind of
avantage you get using (1) for MacPorts itself
It allows to build
On Jun 10, 2009, at 18:49, Thomas De Contes wrote:
basic users are expected to compile ports but not MacPorts itself,
they are expected to install binaries of MacPorts itself :-)
sorry, i forgot it :-)
Well, a user who types sudo port selfupdate causes MacPorts to
build itself from
Le 3 mai 09 à 00:32, Rainer Müller a écrit :
On 2009-05-02 17:01, Thomas De Contes wrote:
Le 2 mai 09 à 16:09, Rainer Müller a écrit :
but when i put an other compiler which knows ada in my path, i get
configure: error: Could not locate a working Objective-C runtime.
so it would be nice to
On 2009-05-30 17:12, Thomas De Contes wrote:
[...]
... i don't understand why you prefer (1) for MacPorts itself
since Ryan Schmidt uses (2) for ports, i don't see what kind of
avantage you get using (1) for MacPorts itself
It allows to build base with another compiler and it makes it
wrote:
i updade MacPorts, and at the step port upgrade outdated it
always sets
checking for gcc... /usr/bin/gcc-4.0
whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc
points on gcc-3.3
what is the problem ?
/usr/bin/gcc-4.0 should exist, and /usr/bin/gcc should point
try to
compile Ports without /usr/bin/gcc-4.0 :-)
This is what the configure macro AC_PROG_CC does. So this is rather an
issue to be addressed in autoconf (from which also other software
would
benefit).
Ryan Schmidt wrote :
But as I understand it, checking for gcc does not mean checking
On 2009-05-02 17:01, Thomas De Contes wrote:
Le 2 mai 09 à 16:09, Rainer Müller a écrit :
but when i put an other compiler which knows ada in my path, i get
configure: error: Could not locate a working Objective-C runtime.
so it would be nice to do it, so i won't have to change my path every
Le 21 mars 09 à 00:52, Ryan Schmidt a écrit :
On Mar 20, 2009, at 17:53, Thomas De Contes wrote:
Le 16 mars 09 à 00:05, Ryan Schmidt a écrit :
On Mar 15, 2009, at 17:36, Thomas De Contes wrote:
i updade MacPorts, and at the step port upgrade outdated it
always sets
checking for gcc
upgrade outdated it
always sets
checking for gcc... /usr/bin/gcc-4.0
whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc points
on gcc-3.3
what is the problem ?
/usr/bin/gcc-4.0 should exist, and /usr/bin/gcc should point to
it, on Tiger and later.
ok
if /usr/bin/gcc-4.0 exists
Le 16 mars 09 à 00:05, Ryan Schmidt a écrit :
On Mar 15, 2009, at 17:36, Thomas De Contes wrote:
i updade MacPorts, and at the step port upgrade outdated it
always sets
checking for gcc... /usr/bin/gcc-4.0
whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc points on
gcc-3.3
On Mar 20, 2009, at 17:53, Thomas De Contes wrote:
Le 16 mars 09 à 00:05, Ryan Schmidt a écrit :
On Mar 15, 2009, at 17:36, Thomas De Contes wrote:
i updade MacPorts, and at the step port upgrade outdated it
always sets
checking for gcc... /usr/bin/gcc-4.0
whereas /usr/bin/gcc-4.0 does
hi :-)
i updade MacPorts, and at the step port upgrade outdated it always
sets
checking for gcc... /usr/bin/gcc-4.0
whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc points on
gcc-3.3
what is the problem ?
--
Téléassistance / Télémaintenance
http://www.portparallele.com
On Mar 15, 2009, at 17:36, Thomas De Contes wrote:
i updade MacPorts, and at the step port upgrade outdated it
always sets
checking for gcc... /usr/bin/gcc-4.0
whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc points on
gcc-3.3
what is the problem ?
/usr/bin/gcc-4.0 should
14 matches
Mail list logo
