In message <[EMAIL PROTECTED]> you wrote:
>
> > Even simple tungs like a printf() require that you include the correct
> > host header files as you will link your host application against the
> > host libraries, too.
>
> That's because printf() is from the host's libraries. lib_generic/md5.c
> is
On Thu, Apr 3, 2008 at 1:36 PM, Scott Wood <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 03, 2008 at 08:26:23PM +0200, Wolfgang Denk wrote:
> > In message <[EMAIL PROTECTED]> you wrote:
> > >
> > > I think this makes sense for code that we for example link from host's
> > > standard libraries. But f
On Thu, Apr 03, 2008 at 08:26:23PM +0200, Wolfgang Denk wrote:
> In message <[EMAIL PROTECTED]> you wrote:
> >
> > I think this makes sense for code that we for example link from host's
> > standard libraries. But for code compiled from files from the U-Boot
> > tree (like lib_generic/md5.c), we sh
In message <[EMAIL PROTECTED]> you wrote:
>
> I think this makes sense for code that we for example link from host's
> standard libraries. But for code compiled from files from the U-Boot
> tree (like lib_generic/md5.c), we shouldn't include host's header files.
But you, you should. Note that we a
Wolfgang Denk wrote:
> In message <[EMAIL PROTECTED]> you wrote:
>> I think that generally it is a better idea to use U-Boot's includes when
>> building for the host system, as this gives us better control over what
>> exactly gets included. But then on the other hand, tools/Makefils has this:
>
>
In message <[EMAIL PROTECTED]> you wrote:
>
> I think that generally it is a better idea to use U-Boot's includes when
> building for the host system, as this gives us better control over what
> exactly gets included. But then on the other hand, tools/Makefils has this:
But U-boot doesn't have the
On Apr 2, 2008, at 10:59 AM, Bartlomiej Sieka wrote:
> Kumar Gala wrote:
>> On Tue, 1 Apr 2008, Wolfgang Denk wrote:
> [...]
Any ideas on how to work around this? Do we really intend to
pick up
the system md5.h or should we be getting the one from u-boot/
include/
md5.
Kumar Gala wrote:
> On Tue, 1 Apr 2008, Wolfgang Denk wrote:
[...]
>>> Any ideas on how to work around this? Do we really intend to pick up
>>> the system md5.h or should we be getting the one from u-boot/include/
>>> md5.h?
>> We need the system md5.h, I think. We'll investigate.
>
> If I force
On Tue, 1 Apr 2008, Wolfgang Denk wrote:
> In message <[EMAIL PROTECTED]> you wrote:
> >
> > > I don't know RHEL - maybe you can update the RPM?
> >
> > Not that I'm aware of. Its a box run by our IT department so I have
> > no ability to upgrade or modify things. It looks like RHEL4 has the
> >
In message <[EMAIL PROTECTED]> you wrote:
>
> > I don't know RHEL - maybe you can update the RPM?
>
> Not that I'm aware of. Its a box run by our IT department so I have
> no ability to upgrade or modify things. It looks like RHEL4 has the
> same issue.
>
> ld2047$ rpm -qf /usr/include/md5
On Mar 31, 2008, at 3:23 PM, Wolfgang Denk wrote:
> In message <9A2E2F7A-D812-4818-
> [EMAIL PROTECTED]> you wrote:
>>
Which Linux distro are you running?
>>>
>>> RHEL WS 3
>
> Oops.
>
> /usr/include/md5.h:27: error: parse error before "UINT4"
> /usr/include/md5.h:30: error: parse er
In message <[EMAIL PROTECTED]> you wrote:
>
> >> Which Linux distro are you running?
> >
> > RHEL WS 3
Oops.
> >>> /usr/include/md5.h:27: error: parse error before "UINT4"
> >>> /usr/include/md5.h:30: error: parse error before '}' token
> >>> /usr/include/md5.h:38: error: parse error before "PR
On Mar 28, 2008, at 10:44 AM, Kumar Gala wrote:
>
> On Mar 28, 2008, at 9:45 AM, Wolfgang Denk wrote:
>> In message > [EMAIL PROTECTED]> you wrote:
>>> Even with this patch I'm still having issues:
>>>
>>> gcc -g -Wall -idirafter /tmp/u-boot-85xx/include -idirafter /tmp/u-
>>> boot-85xx/include2 -
On Mar 28, 2008, at 9:45 AM, Wolfgang Denk wrote:
> In message [EMAIL PROTECTED]> you wrote:
>> Even with this patch I'm still having issues:
>>
>> gcc -g -Wall -idirafter /tmp/u-boot-85xx/include -idirafter /tmp/u-
>> boot-85xx/include2 -idirafter /tmp/u-boot-85xx/include -
>> DTEXT_BASE=0xfff80
In message <[EMAIL PROTECTED]> you wrote:
> Even with this patch I'm still having issues:
>
> gcc -g -Wall -idirafter /tmp/u-boot-85xx/include -idirafter /tmp/u-
> boot-85xx/include2 -idirafter /tmp/u-boot-85xx/include -
> DTEXT_BASE=0xfff8 -DUSE_HOSTCC -O -c -o image.o image.c
> In file inc
Even with this patch I'm still having issues:
gcc -g -Wall -idirafter /tmp/u-boot-85xx/include -idirafter /tmp/u-
boot-85xx/include2 -idirafter /tmp/u-boot-85xx/include -
DTEXT_BASE=0xfff8 -DUSE_HOSTCC -O -c -o image.o image.c
In file included from image.c:73:
/usr/include/md5.h:27: error: p
On Thu, 27 Mar 2008 15:06:40 +0100
Bartlomiej Sieka <[EMAIL PROTECTED]> wrote:
> Revert commit 87c8431f and fix build breakage so that the build continues
> to work on FC systems.
>
> Signed-off-by: Bartlomiej Sieka <[EMAIL PROTECTED]>
Tested-by: Haavard Skinnemoen <[EMAIL PROTECTED]>
Using Deb
Hi Bartlomiej,
Bartlomiej Sieka <[EMAIL PROTECTED]> writes:
> Revert commit 87c8431f and fix build breakage so that the build continues
> to work on FC systems.
>
> Signed-off-by: Bartlomiej Sieka <[EMAIL PROTECTED]>
> ---
> Patch tested on FC and kubuntu. Could people that reported Haavard's pat
Revert commit 87c8431f and fix build breakage so that the build continues
to work on FC systems.
Signed-off-by: Bartlomiej Sieka <[EMAIL PROTECTED]>
---
Patch tested on FC and kubuntu. Could people that reported Haavard's patch
fixing the build for them try this one out and report back?
diff --gi
19 matches
Mail list logo
