Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - The cause of porting as colliding GPL.: (2 Items)
   
The cause of porting as colliding GPL.  
Thanks Boudreau and Mathew

The cause of porting as colliding GPL.

So we need another porting one of dd utility.


and, Have we able to use the bmake on QNX6.4.0?



Regards.
Kengo Kinoshita
----- Original Message -----


>On Wed, Aug 04, 2010 at 04:33:47AM -0400, Kengo Kinoshita wrote:
>> Hello
>> 
>> 
>> I am Japanese software engineer.
>> 
>> Now I begin to start the porting job that porting dd utility from NetBSD to QNX6.4.0.
>
>I guess the first question is why do you want to
>port the NetBSD one?  What's wrong with the
>shipped dd?
>
>> 
>> and Source code of dd(NetBSD edition) was already downloaded and already try to rebuild on QNX6.4.0.
>> 
>> But many errors happen,
>> So I am very confused those errors are see bellow(used Makefile)
>> Makefile:7: *** missing separator.
>
>NetBSD uses bsd make (bmake), not gnu make.
>
>> 
>> and simply gcc using as bellow.
>> Please teach me something solve operations regarding the porting job.
>> 
>> 
>> 
>> # gcc dd.c -o dd
>> In file included from /root/NetBSD/usr/src/include/rpc/types.h:41,
>>                  from /root/NetBSD/usr/src/sys/sys/mtio.h:37,
>>                  from dd.c:53:
>> /root/NetBSD/usr/src/sys/arch/hpc/stand/include/machine/types.h:21: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'int64_t'
>> /root/NetBSD/usr/src/sys/arch/hpc/stand/include/machine/types.h:26: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'uint64_t'
>> /root/NetBSD/usr/src/sys/arch/hpc/stand/include/machine/types.h:32: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'u_int64_t'
>> /root/NetBSD/usr/src/sys/arch/hpc/stand/include/machine/types.h:38: error: conflicting types for 'time_t'
>> /usr/qnx640/target/qnx6/usr/include/time.h:46: error: previous declaration of 'time_t' was here
>> In file included from dd.c:66:
>> dd.h:45: error: expected specifier-qualifier-list before 'uint64_t'
>> dd.h:61: error: expected specifier-qualifier-list before 'uint64_t'
>> In file included from dd.c:67:
>> extern.h:58: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cpy_cnt'
>> extern.h:59: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cbsz'
>> extern.h:62: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'progress'
>> dd.c:80: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cpy_cnt'
>> dd.c:83: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cbsz'
>> dd.c:85: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'progress'
>> dd.c: In function 'main':
>> dd.c:107: error: 'SIGINFO' undeclared (first use in this function)
>> dd.c:107: error: (Each undeclared identifier is reported only once
>> dd.c:107: error: for each function it appears in.)
>> dd.c: In function 'setup':
>> dd.c:126: error: 'IO' has no member named 'name'
>> dd.c:127: error: 'IO' has no member named 'name'
>> dd.c:128: error: 'IO' has no member named 'fd'
>> dd.c:130: error: 'IO' has no member named 'fd'
>> dd.c:130: error: 'IO' has no member named 'name'
>> dd.c:131: error: 'IO' has no member named 'fd'
>> dd.c:132: error: 'IO' has no member named 'name'
>> dd.c:136: error: 'IO' has no member named 'fd'
>> dd.c:136: error: 'IO' has no member named 'fd'
>> dd.c:141: error: 'IO' has no member named 'flags'
>> dd.c:146: error: 'IO' has no member named 'name'
>> dd.c:148: error: 'IO' has no member named 'fd'
>> dd.c:149: error: 'IO' has no member named 'name'
>> dd.c:153: error: 'IO' has no member named 'fd'
>> dd.c:153: error: 'IO' has no member named...
View Full Message
Re: The cause of porting as colliding GPL.  
On Wed, Aug 04, 2010 at 04:06:33PM -0400, Kengo Kinoshita wrote:
> Thanks Boudreau and Mathew
> 
> The cause of porting as colliding GPL.
> 
> So we need another porting one of dd utility.
> 

Attached is a NetBSD dd ported to our makefile
structure.  Tape support is disabled.  Grep
for __QNXNTO__ for the diffs.  Test as you feel
appropriate.

> 
> and, Have we able to use the bmake on QNX6.4.0?

You can get one if you bootstrap pkgsrc but there's
other issues (see attached archive).

http://community.qnx.com/sf/projects/pkgsrc

Regards,

-seanb
Attachment: Text dd.tgz 20.06 KB