To clear up any confusion for others that may pick up this thread, my
previous email stated that a patch should not be made to perl sources... I
mistook the details below as implying that each perl module (i.e.
DBD::mysql) be patched for an error in the Config.pm module. In actuality, I
believe, th
I would think this should stay out of the perl sources since it is not a bug
of perl's... Thoughts?
I also just discovered that this fixes a build problem with Data::Dumper...
Or so it would appear. It's possible this will effect several packages. The
patch should not be put in all the perl source
Edward,
I edited /System/Library/Perl/5.8.1/darwin-thread-multi-2level/Config.pm,
switched perl back to the apple install and had no problems building
DBD::mysql.
Your information is greatly appreciated!
c
On 10/15/03 5:58 PM, "Edward Moy" <[EMAIL PROTECTED]> wrote:
> We recently discovered t
In hints/darwin.sh, replace
*) ld="MACOSX_DEPLOYMENT_TARGET=10.3 ${ld}" ;;
with
*) ld="env MACOSX_DEPLOYMENT_TARGET=10.3 ${ld}" ;;
Hopefully, this will go into 5.8.2.
Ed
On Oct 15, 2003, at 5:05 PM, David Wheeler wrote:
On Wednesday, October 15, 2003, at 04:58 PM, Edward Moy wrote:
On Wednesday, October 15, 2003, at 04:58 PM, Edward Moy wrote:
We recently discovered the DBD::mysql problem as well. The patch is
to edit
/System/Library/Perl/5.8.1/darwin-thread-multi-2level/Config.pm,
replacing:
ld='MACOSX_DEPLOYMENT_TARGET=10.3 cc'
with
ld='env MACOSX_DEPLOYMENT_TARG
We recently discovered the DBD::mysql problem as well. The patch is to
edit /System/Library/Perl/5.8.1/darwin-thread-multi-2level/Config.pm,
replacing:
ld='MACOSX_DEPLOYMENT_TARGET=10.3 cc'
with
ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc'
Unfortunately, this change is too late to get into Pa
Mike,
I was encountering the same errors as you in my quest to install DBD::mysql
and discovered that under the following setup:
Custom installed Perl 5.8.1 RC3 - No multi-threading
ggc 2.95 - via /usr/sbin/gcc_select 2
Removing /sw/lib/perl5/Storable.pm & /sw/lib/perl5/auto/Storable
I was abl
On Friday, August 8, 2003, at 7:28 AM, John Delacour wrote:
At 4:09 pm -0600 7/8/03, Mike Schienle wrote:
I'm having some trouble with DBI and DBD::MysqlPP (and DBD::MySQL) on
10.3. Can I get a sanity check response that some people are able to
run one of these? 10.3 is not that important for w
Does this mean that the version of perl installed on Panther will not
support DBI and DBD::MySQL?
That would be a real pain.
On Friday, Aug 8, 2003, at 15:28 Europe/Madrid, John Delacour wrote:
At 4:09 pm -0600 7/8/03, Mike Schienle wrote:
I'm having some trouble with DBI and DBD::MysqlPP (an
On Friday, August 8, 2003, at 8:35 AM, Mike Schienle wrote:
On Friday, August 8, 2003, at 7:28 AM, John Delacour wrote:
At 4:09 pm -0600 7/8/03, Mike Schienle wrote:
I'm having some trouble with DBI and DBD::MysqlPP (and DBD::MySQL)
on 10.3. Can I get a sanity check response that some people ar
On Friday, August 8, 2003, at 10:07 AM, Robert Whittle wrote:
Does this mean that the version of perl installed on Panther will not
support DBI and DBD::MySQL?
I wouldn't try to read into my situation too much. I'm also using MySQL
Alpha release 4.1.x. So, an alpha DB on a beta OS. I think I ju
Hi all -
I'm having some trouble with DBI and DBD::MysqlPP (and DBD::MySQL) on
10.3. Can I get a sanity check response that some people are able to
run one of these? 10.3 is not that important for what I'm working on,
but MySQL is, so I can roll back to older versions of MacOS X, MySQL,
etc.,
At 4:09 pm -0600 7/8/03, Mike Schienle wrote:
I'm having some trouble with DBI and DBD::MysqlPP (and DBD::MySQL)
on 10.3. Can I get a sanity check response that some people are able
to run one of these? 10.3 is not that important for what I'm working
on, but MySQL is, so I can roll back to olde
13 matches
Mail list logo