On 15 April 2013 18:32, Yaakov (Cygwin/X) wrote:
> On 2013-04-15 07:54, Chris Sutcliffe wrote:
>>
>> On 6 March 2013 08:40, Chris Sutcliffe wrote:
>>>
>>> I noticed a problem after upgrading to the 2.23.1-1 release of
>>> binutils that cygport was no longer generating debuginfo files. After
>>> di
On 2013-04-15 07:54, Chris Sutcliffe wrote:
On 6 March 2013 08:40, Chris Sutcliffe wrote:
I noticed a problem after upgrading to the 2.23.1-1 release of
binutils that cygport was no longer generating debuginfo files. After
digging in to it a little and following up on the cygwin-ports mailing
l
On 2013-04-15 10:11, Christopher Faylor wrote:
The original thread did not have an explanation of what the actual
problem with objdump was so I don't really have any way of investigating
it. Yaakov, can you explain what you think the problem is?
All I know right now is in this thread:
http://
On Mon, Apr 15, 2013 at 06:52:45PM +0200, Corinna Vinschen wrote:
>I was just pointing out the version mismatch. The package is called
>2.23.51, while the binaries claim to be 2.23.52. I did not comment
>on the behaviour.
Yes, I got that. I was trying to move the discussion away from version
co
On Apr 15 11:11, Christopher Faylor wrote:
> On Mon, Apr 15, 2013 at 04:39:54PM +0200, Corinna Vinschen wrote:
> >On Apr 15 10:37, Christopher Faylor wrote:
> >> On Mon, Apr 15, 2013 at 03:48:09PM +0200, Corinna Vinschen wrote:
> >> >On Apr 15 15:21, Corinna Vinschen wrote:
> >> >> On Apr 15 08:54,
On Mon, Apr 15, 2013 at 04:39:54PM +0200, Corinna Vinschen wrote:
>On Apr 15 10:37, Christopher Faylor wrote:
>> On Mon, Apr 15, 2013 at 03:48:09PM +0200, Corinna Vinschen wrote:
>> >On Apr 15 15:21, Corinna Vinschen wrote:
>> >> On Apr 15 08:54, Chris Sutcliffe wrote:
>> >> > Hi All,
>> >> >
>> >
On Apr 15 10:37, Christopher Faylor wrote:
> On Mon, Apr 15, 2013 at 03:48:09PM +0200, Corinna Vinschen wrote:
> >On Apr 15 15:21, Corinna Vinschen wrote:
> >> On Apr 15 08:54, Chris Sutcliffe wrote:
> >> > Hi All,
> >> >
> >> > On 6 March 2013 08:40, Chris Sutcliffe wrote:
> >> > > I noticed a pr
On Mon, Apr 15, 2013 at 03:48:09PM +0200, Corinna Vinschen wrote:
>On Apr 15 15:21, Corinna Vinschen wrote:
>> On Apr 15 08:54, Chris Sutcliffe wrote:
>> > Hi All,
>> >
>> > On 6 March 2013 08:40, Chris Sutcliffe wrote:
>> > > I noticed a problem after upgrading to the 2.23.1-1 release of
>> > > b
On Apr 15 15:21, Corinna Vinschen wrote:
> On Apr 15 08:54, Chris Sutcliffe wrote:
> > Hi All,
> >
> > On 6 March 2013 08:40, Chris Sutcliffe wrote:
> > > I noticed a problem after upgrading to the 2.23.1-1 release of
> > > binutils that cygport was no longer generating debuginfo files. After
> >
On Apr 15 08:54, Chris Sutcliffe wrote:
> Hi All,
>
> On 6 March 2013 08:40, Chris Sutcliffe wrote:
> > I noticed a problem after upgrading to the 2.23.1-1 release of
> > binutils that cygport was no longer generating debuginfo files. After
> > digging in to it a little and following up on the cy
Hi All,
On 6 March 2013 08:40, Chris Sutcliffe wrote:
> I noticed a problem after upgrading to the 2.23.1-1 release of
> binutils that cygport was no longer generating debuginfo files. After
> digging in to it a little and following up on the cygwin-ports mailing
> list, Yaakov determined that th
Achim Gratz NexGo.DE> writes:
> Not only this, but any packages built with the rogue binutils package may
> randomly miss dependencies.
This is for dependencies auto-generated by cygport only, of course.
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Chris Sutcliffe gmail.com> writes:
> I noticed a problem after upgrading to the 2.23.1-1 release of
> binutils that cygport was no longer generating debuginfo files.
Not only this, but any packages built with the rogue binutils package may
randomly miss dependencies. So anyone who built packages
On 3/7/2013 00:53, Christopher Faylor wrote:
> On Wed, Mar 06, 2013 at 08:40:32AM -0500, Chris Sutcliffe wrote:
>> I noticed a problem after upgrading to the 2.23.1-1 release of
>> binutils that cygport was no longer generating debuginfo files. After
>> digging in to it a little and following up o
On Wed, Mar 06, 2013 at 08:40:32AM -0500, Chris Sutcliffe wrote:
>I noticed a problem after upgrading to the 2.23.1-1 release of
>binutils that cygport was no longer generating debuginfo files. After
>digging in to it a little and following up on the cygwin-ports mailing
>list, Yaakov determined t
I noticed a problem after upgrading to the 2.23.1-1 release of
binutils that cygport was no longer generating debuginfo files. After
digging in to it a little and following up on the cygwin-ports mailing
list, Yaakov determined that the objdump included in the 2.23.1
release of binutils does not h
16 matches
Mail list logo
