Armin K. wrote these words on 02/11/13 20:19 CST:
> Try --includedir=/usr/include/iodbc
That would solve the problem with the overwriting of the headers (not
tested), but what about the packages that expect them to be in
/usr/include? Are we ready to modify the instructions for the couple of
packa
On 02/12/2013 02:58 AM, Randy McMurchy wrote:
> Armin K. wrote these words on 02/11/13 19:15 CST:
>> On 02/12/2013 02:12 AM, Randy McMurchy wrote:
>>> My script reports this when installing libiodbc after unixODBC is
>>> already installed:
>>>
>>> The following files will be overwritten:
>>> /usr/i
Armin K. wrote these words on 02/11/13 19:15 CST:
> On 02/12/2013 02:12 AM, Randy McMurchy wrote:
>> My script reports this when installing libiodbc after unixODBC is
>> already installed:
>>
>> The following files will be overwritten:
>> /usr/include/odbcinst.h
>> /usr/include/sql.h
>> /usr/includ
Armin K. wrote these words on 02/11/13 19:15 CST:
> On 02/12/2013 02:12 AM, Randy McMurchy wrote:
>> Here's something that doesn't come up very often. It appears that
>> the libiodbc package in BLFS overwrites files that are installed by
>> the BLFS package unixODBC (or vice-versa, depending on how
On 02/12/2013 02:12 AM, Randy McMurchy wrote:
> Hi all,
>
> Here's something that doesn't come up very often. It appears that
> the libiodbc package in BLFS overwrites files that are installed by
> the BLFS package unixODBC (or vice-versa, depending on how you view
> it).
>
> My script reports this
Hi all,
Here's something that doesn't come up very often. It appears that
the libiodbc package in BLFS overwrites files that are installed by
the BLFS package unixODBC (or vice-versa, depending on how you view
it).
My script reports this when installing libiodbc after unixODBC is
already installe
Hi all,
Grepping through the book I found about 35 files that had tabs used for
indentation instead of spaces. Please do not use tabs for indentation.
It appears most of them were from copy-and-paste operations (just because
most of them were in the same spots in the files), so it appears it is
re
Matt Burgess wrote:
> On Mon, 2013-02-11 at 21:45 +0100, Pierre Labastie wrote:
>
>> If you use quilt, it usually signals spaces at the end of lines when
>> doing 'quilt refresh'.
>
> Indeed, it does. However, that assumes that a) one is using quilt and
> b) your patch touches a file that contains
On Mon, Feb 11, 2013 at 12:55:55PM -0600, Randy McMurchy wrote:
> Hi all,
>
> I just ran my script that cleans up extraneous spaces from blank lines and
> at the end of lines in all the .xml files. The commit will probably not show
> up in -book as it is large. Editors (or anyone with a sandbox of
On Mon, 2013-02-11 at 21:45 +0100, Pierre Labastie wrote:
> If you use quilt, it usually signals spaces at the end of lines when
> doing 'quilt refresh'.
Indeed, it does. However, that assumes that a) one is using quilt and
b) your patch touches a file that contains the extra spaces.
If we wan
Le 11/02/2013 20:20, Bruce Dubbs a écrit :
> Randy McMurchy wrote:
>> Randy McMurchy wrote these words on 02/11/13 12:55 CST:
>>> I just ran my script that cleans up extraneous spaces from blank lines and
>>> at the end of lines in all the .xml files.
>> If you use Vim to edit the book's .xml, you
Le 10/02/2013 23:34, Bruce Dubbs a écrit :
> Pierre Labastie wrote:
>
>> I think the out of memory error are tcl errors, not gcc.
>>
>> Amazingly, I have less unsupported tests than you in gcc (and many less
>> XPASS or FAIL), but more unsupported tests in g++. I also have many
>> more results for
On Mon, 2013-02-11 at 12:55 -0600, Randy McMurchy wrote:
> Hi all,
>
> I just ran my script that cleans up extraneous spaces from blank lines and
> at the end of lines in all the .xml files. The commit will probably not show
> up in -book as it is large. Editors (or anyone with a sandbox of curren
Bruce Dubbs wrote these words on 02/11/13 13:14 CST:
> Yes, its almost 500K. Do you want me to release it?
Doesn't matter to me as there is really nothing to see. I can send a list
of the files, but then you'll see that when you 'svn up'. I don't think it
needs to be released, but let others have
Randy McMurchy wrote:
> Randy McMurchy wrote these words on 02/11/13 12:55 CST:
>> I just ran my script that cleans up extraneous spaces from blank lines and
>> at the end of lines in all the .xml files.
>
> If you use Vim to edit the book's .xml, you can add the following lines
> to your /etc/vimr
Randy McMurchy wrote:
> Hi all,
>
> I just ran my script that cleans up extraneous spaces from blank lines and
> at the end of lines in all the .xml files. The commit will probably not show
> up in -book as it is large. Editors (or anyone with a sandbox of current SVN
> trunk) ensure you do an 'svn
Randy McMurchy wrote these words on 02/11/13 12:55 CST:
> I just ran my script that cleans up extraneous spaces from blank lines and
> at the end of lines in all the .xml files.
If you use Vim to edit the book's .xml, you can add the following lines
to your /etc/vimrc file and it will show in red
Hi all,
I just ran my script that cleans up extraneous spaces from blank lines and
at the end of lines in all the .xml files. The commit will probably not show
up in -book as it is large. Editors (or anyone with a sandbox of current SVN
trunk) ensure you do an 'svn up' before starting any edits so
18 matches
Mail list logo
