This is the mail archive of the mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ct-ng] mingw32 sysroot

Arnaud, Esben, All,

On Wednesday 11 August 2010 23:58:59 Arnaud Lacombe wrote:
> On Wed, Aug 11, 2010 at 5:22 PM, Yann E. MORIN
> <> wrote:
> > OK. Patch queued for later inspection.
> if you apply that patch, can you include the exact error triggered by
> the (gcc) build ? That would be better than "fix $foo on $bar" which
> does not carry much information about why the change was needed to fix
> what wrong behavior, and eventually what made it the proper change.

That'd be Esben to describe it better. :-)

But what really is of interest to us is that it does "fix building a
toolchain targeting mingw32". Really, what I want to know while I read
a code is to know what the kludge is _for_, not what the actual error

The error snippet should be attached to the commit message, of course.
Thus, we can 'blame' the file and see what rev it is, and see the log
for that rev.

> This should be the job of a bugtracker, but I'm afaid that would be
> too much :)

FYI, I'm looking at bugzilla. I'd like to have a BT for such things, but
a BT is a lot of work, as well. One has to do bug triage, de-duplication,
and all the stuff. Plus, it means we _have_ to remember to include bug ids
in commit messages, so we keep track btw BT <-> VCS.

Yann E. MORIN.

|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |

For unsubscribe information see

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]