On Jun 24, 2007, at 8:37 AM, Ryan Schmidt wrote:
On Jun 23, 2007, at 18:16, Paul Guyot wrote:
On Jun 24, 2007, at 6:12 AM, Juan Manuel Palacios wrote:
About this commit though it was discussed on the this list
some time ago whether GSoC work should be committed to trunk or
to a bra
On Jun 24, 2007, at 7:00 AM, Ryan Schmidt wrote:
On Jun 23, 2007, at 16:27, Juan Manuel Palacios wrote:
I'm curious about why we provide facilities to alter the
configure environment in many ways but practically none to alter
the build environment. I know that in the ideal case (a proper
On Jun 23, 2007, at 18:16, Paul Guyot wrote:
On Jun 24, 2007, at 6:12 AM, Juan Manuel Palacios wrote:
About this commit though it was discussed on the this list
some time ago whether GSoC work should be committed to trunk or to
a branch, and the consensus was that, this being SCM and
On Jun 24, 2007, at 6:12 AM, Juan Manuel Palacios wrote:
Hey Chris!
Good to see you're making progress in your GSoC project, most
excited to see it completed!
About this commit though it was discussed on the this list
some time ago whether GSoC work should be committed to
On Jun 23, 2007, at 16:27, Juan Manuel Palacios wrote:
I'm curious about why we provide facilities to alter the configure
environment in many ways but practically none to alter the build
environment. I know that in the ideal case (a properly written
build system for any given software pac
configure.env PATH=${prefix}/lib/postgresql82/bin:$env(PATH)
Sweet!
I have to set build.env and destroot.env and then it just works!
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macport
Hello Paul!
I'm curious about why we provide facilities to alter the configure
environment in many ways but practically none to alter the build
environment. I know that in the ideal case (a properly written build
system for any given software package) the configure environment
s
Hey Chris!
Good to see you're making progress in your GSoC project, most excited
to see it completed!
About this commit though it was discussed on the this list some
time ago whether GSoC work should be committed to trunk or to a
branch, and the consensus was that, this bei
On Jun 23, 2007, at 15:38, Hagen Overdick wrote:
Postgres has it's own infrastructure for add-ons, see:
http://www.postgresql.org/docs/8.2/static/xfunc-c.html
This system relies on:
/opt/local/lib/postgresql82/bin/pg_config
Unfortunately, it's not in the $PATH, when the Makefile is called. I
Hello all,
just getting my feeds wet in writing Ports... Here is a tricky question:
Postgres has it's own infrastructure for add-ons, see:
http://www.postgresql.org/docs/8.2/static/xfunc-c.html
This system relies on:
/opt/local/lib/postgresql82/bin/pg_config
Unfortunately, it's not in the $
On 23/06/07 09:36, Ryan Schmidt wrote:
> Ok. I just tried installing the slang port (1.4.9_0) and it worked for me,
> on Intel Core 2 Duo. The slang2 port (2.1.0_0) worked, too.
Ok
> This leads me to continue to suspect a rogue readline library somewhere on
> your system. First, is your MacPort
On Jun 21, 2007, at 17:06, Sbranzo wrote:
/usr/bin/ld: warning prebinding disabled because of undefined
symbols
/usr/bin/ld: Undefined symbols:
_SLrline_init
_SLrline_open2
collect2: ld returned 1 exit status
make[1]: *** [slsh_exe] Error 1
make: *** [static] Error 2
_SLrline_* seem to be r
12 matches
Mail list logo
