Re: [INTERNALS-WIN] Re: ext/odbc no longer builds under VC6

[email protected] ("Steph Fox")
Newsgroups php.internals.win
Message-ID <009101c95d90$7cd61b10$3ffc1f3e@foxbox>
> Sorry, this comment was for this thing:
>
>> Which nobody else has access to, so you could be using Linux on there for
>> all I know. (This is why transparency is a Good Thing.)
>
> I'm not sure either what you are talking about.

I'm just pointing out that we don't have any way to take a look and go, 'Oh, 
Pierre has libs dating from 2004 - wonder where they came from'. Or 2003, or 
1998. Ours date from 1998, despite the fact that most of the other libs and 
headers are dated 2003 following the upgrade. If you wanted to be helpful, 
you could simply report the creation date of your copy. You could explain to 
us what's different enough that your setup works and our allegedly identical 
setups do not. Or you could just make it possible for everyone to see 
exactly what you're using on the snaps box, which would be equally helpful 
and far less time-consuming.

> About odbc, it works here and on the snaps, both being fresh install
> of VC6 Enterprise + PSDK 2003/02.

VC6 Enterprise, hm? Is that in any way different from the MSVC6++ that Zend 
had, and Edin had, and Liz had?

See, Pierre, I've been building PHP under Windows quite happily for the last 
7 years until you put the crypt stuff in and broke the build. Then I got to 
hear all about how I should've upgraded (even though there hadn't been any 
upgrades to make that I was aware of because the compiler was no longer 
supported by MS anyway.) Now I've upgraded, and I'm _still_ seeing major 
problems.

The mysqlnd code makes directly the opposite assumption about the nature of 
u_char to the crypt code. So do a lot of other bits and pieces of PHP, and 
so does the relevant MSVC header, come to that... and everything but crypt 
throws warnings because of it.

The odbc extension, which is enabled by default under Windows and has been 
part of the core forever, nobody but you can apparently build under VC6 now.

It's not good enough to intervene every time I try to talk with someone 
other than yourself about the Windows build. There are other people than you 
affected by what happens to it, and we need to be able to talk to one 
another.

Two of us with more than the average amount of PHP/Win32 internals 
experience believe that Patrick's 64-bit commit broke the PHP build because 
it made assumptions about the underlying ODBC library that don't match our 
reality. We need to talk to Patrick about this and get it resolved quickly, 
not waste time in a fight with you about how everything's perfect on a box 
we can't see inside.

- Steph
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.