Re: [OpenWrt-Devel] Compiling outside of buildroot

[Luigi Mantellini]

Hi All,

in order to avoid the absoluted-path issue, I suggest to use the
script wrapper.sh (used to create the toolchain target).

https://dev.openwrt.org/browser/trunk/target/toolchain/files/wrapper.sh

Can we integrate this script also into the SDK target?

thanks and best regards,

luigi

On Sun, Feb 21, 2010 at 3:49 PM, Bas Mevissen  wrote:
> On 02/19/2010 08:08 PM, Felix Fietkau wrote:
>
>> I disagree with the way manufacturers typically set up board support
>> packages. Often you have to install something as root, which is annoying
>> for people that only have user accounts on some machines. Often you can
>> only have one globally installed instance of the SDK, which makes it
>> annoying to support multiple different versions, or even just multiple
>> minor variations of the toolchain.
>>
>
> That's true, but for most of people it is a convenient way to just have
> to install an SDK and start developing.
>
> One issue with pre-compiled SDK's is gcc hardcoded absolute paths to
> libraries that make relocation difficult. There are scripts that change
> the absolute paths to relative one. Then it is possible to install a
> precompiled SDK in the user accessible location you want.
>
> With OpenWRT, it is possible to have multiple different version
> installed at the same time. You can simply choose a different location
> for every variant where you build OpenWRT, e.g. build one in
> /opt/OpenWRT// and another one in
> /opt/OpenWRT//
>
> By sourcing a (to be written) script say
> /opt/OpenWRT///settings.rc you switch between
> different variants.
>
>> Why do you want to call it outside of the tree? You can keep your
>> packages as a separate feed, which makes it easy to keep track of your
>> own work without having to fully integrate it into the OpenWrt tree.
>>
>
> Personally, I like a complete separation between open source and
> propriety code. So when developing propriety code which uses OpenWRT as
> a platform, I prefer to use a fixed tree of OpenWRT stuff (packaged and
> installed somewhere) and have an entirely separate tree of propriety
> code in which I can simply call "make". Then the resulting binaries,
> kmods and images should land somewhere in my propriety tree.
>
> Please note that I'm not saying that the system with the feeds is not
> working properly! I just want to offer an OpenWRT based SDK for a
> certain board (including kernel headers and .config actually) as an easy
> to install package and an archive with only the propriety stuff.
>
> One then only needs to install the SDK, unpack the archive with the
> propriety code and run make.
>
> Bas.
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] remount /dev/root readonly for shutdown

[Luigi Mantellini]

Ciao Gerlando,

In general xfs and ext4 performances are very similar. If you really
need a true transactional fs I suggest you to switch to ext4 that
requires lesser resources than xfs.

ciao

luigi

On Sun, Jan 31, 2010 at 2:29 PM, puchu  wrote:
> Hi,
>
> i use xfs but on my linux desktop system (not openwrt) ... there it works 
> nice.
> the only thing i know is that xfs needs more ram then ext2/3 and on systems 
> with low ram profile it
> can get very unreliable and unstable.
>
> greets
> Am Sonntag 31 Januar 2010 14:11:12 schrieb Gerlando Falauto:
>> > I tried switching to ext2, but now I can't even boot at all:
>> >
>> > VFS: Mounted root (ext2 filesystem) on device 8:2.
>> > Freeing init memory: 116K
>> > Please be patient, while OpenWrt loads ...
>> >
>> > Maybe I screwed up something in my backup / mkfs / restore process...
>> > tomorrow I'll try with a fresh openwrt-built root filesystem.
>>
>> I overwrote my ext2 root fs with the fresh root filesystem.
>> Now everything works perfectly.
>> Does anybody, ever, use XFS at all?
>> It looks so buggy to me...
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] remount /dev/root readonly for shutdown

[Luigi Mantellini]

s/are locking/is locking/g

On Sat, Jan 30, 2010 at 6:30 PM, Luigi Mantellini
 wrote:
> Ciao Gerlando,
>
> can you try to modify the mount init script adding a "ps" just before
> the umount -a -r call?
> I think that you have some process that are locking some file.
>
> best regards,
>
> luigi
>
> On Sat, Jan 30, 2010 at 4:46 PM, puchu  wrote:
>> Hi
>>
>> for me openwrt also doesnt umount the disk ... okay i mount them by hand (in 
>> an init script) and i dont add them to fstab but i found a
>> simple but effective solution...
>>
>> maybe im wrong but for me it seems a poweroff/reboot doesnt bring any 
>> service down
>> ,as it is done on my desktop box,  it just reboots without killing the 
>> runnung apps...
>> therefor openssh and dropbear doesnt unconnect on a reboot and the 
>> connection is dropped when the router is up again ... the shell where the
>> poweroff/reboot command is typed in just "hangs"
>>
>> to avoid this and get a clean umount of my disk i do this
>>
>> i dont use dropbear thefor i stop the sshd script in init.d i dont know if 
>> the dropbears init script has the same name ...
>>
>> to /etc/profile add this lines and source the file or logout and login again 
>> so that
>>  the the changes are used in the current shell ... ash --login should also 
>> work ...
>> the portmap and nfsd script are stop and syslog is killed because
>> if they are not killed the fs wont correctly umount
>>
>>
>> romount() { /etc/init.d/portmap stop
>>            /etc/init.d/nfsd stop
>>            killall syslogd
>>            for i in `cat /proc/mounts|grep "^/dev/"|sed -e "s/ .*//g"|sort 
>> -r|uniq`
>>                do umount -rf $i
>>            done
>>            echo 0 > /proc/diag/led/power
>>            ifdown wan
>>          }
>>
>> reboot() { romount > /dev/null 2>&1
>>           /sbin/reboot
>>           /etc/init.d/sshd stop
>>           exit
>>         }
>>
>> poweroff() { romount > /dev/null 2>&1
>>             /sbin/poweroff
>>             /etc/init.d/sshd stop
>>             exit
>>           }
>>
>>
>> greets
>>
>>
>> Am Samstag 30 Januar 2010 14:13:57 schrieb edgar.sol...@web.de:
>>> Is there a sync command before the unmount?
>>>
>>> Maybe the system does not reach the umount call, and therefor it is
>>> never cleanly unmounted? You could debug that.
>>>
>>> Maybe the controller is caching and needs specific commands to write the
>>> cache to disc? Did you search the web?
>>>
>>> good luck, ede
>>>
>>> On 30.01.2010 00:11, Gerlando Falauto wrote:
>>> > Hi all,
>>> >
>>> > I am (slowly) experimenting with my LaCie Ethernet Disk Mini v2 NAS.
>>> > In order to maintain compatibility with Lacie's software, I did not
>>> > change the disk layout (yet).
>>> > I can run my own OpenWRT without disrupting the original firmware
>>> > by putting the kernel's uImage on [sda9]/snaps/00/boot and the root
>>> > filesystem on [sda2] which is an xfs partition (it's the 300GB user
>>> > partition) mounted as read/write.
>>> >
>>> > Now every time I shutdown the box, my xfs filesystem gets corrupted
>>> > and at the next reboot
>>> > kernel ends up panicking because it can't mount the root filesystem to
>>> > find an init file.
>>> >
>>> > I figured the shutdown sequence did not correctly unmount my filesystem;
>>> > I found the executed command was "umount -a -r", so I tried doing it
>>> > manually:
>>> >
>>> > r...@openwrt:~# umount -a -r
>>> > umount: devpts busy - remounted read-only
>>> > umount: tmpfs busy - remounted read-only
>>> > umount: tmpfs busy - remounted read-only
>>> > umount: can't remount /dev/root read-only
>>> > umount: can't remount rootfs read-only
>>> >
>>> > r...@openwrt:~# mount -t proc proc /proc
>>> > r...@openwrt:~# umount -r /
>>> > umount: can't remount /dev/root read-only
>>> >
>>> > I know that mounting the initial root filesystem as read-write is not
>>> > a very nice thing to do,
>>> > but could someone please point out why it's, like, forbidden by law,
>>> > so that I even get punished for doing it

Re: [OpenWrt-Devel] remount /dev/root readonly for shutdown

[Luigi Mantellini]

Ciao Gerlando,

can you try to modify the mount init script adding a "ps" just before
the umount -a -r call?
I think that you have some process that are locking some file.

best regards,

luigi

On Sat, Jan 30, 2010 at 4:46 PM, puchu  wrote:
> Hi
>
> for me openwrt also doesnt umount the disk ... okay i mount them by hand (in 
> an init script) and i dont add them to fstab but i found a
> simple but effective solution...
>
> maybe im wrong but for me it seems a poweroff/reboot doesnt bring any service 
> down
> ,as it is done on my desktop box,  it just reboots without killing the 
> runnung apps...
> therefor openssh and dropbear doesnt unconnect on a reboot and the connection 
> is dropped when the router is up again ... the shell where the
> poweroff/reboot command is typed in just "hangs"
>
> to avoid this and get a clean umount of my disk i do this
>
> i dont use dropbear thefor i stop the sshd script in init.d i dont know if 
> the dropbears init script has the same name ...
>
> to /etc/profile add this lines and source the file or logout and login again 
> so that
>  the the changes are used in the current shell ... ash --login should also 
> work ...
> the portmap and nfsd script are stop and syslog is killed because
> if they are not killed the fs wont correctly umount
>
>
> romount() { /etc/init.d/portmap stop
>            /etc/init.d/nfsd stop
>            killall syslogd
>            for i in `cat /proc/mounts|grep "^/dev/"|sed -e "s/ .*//g"|sort 
> -r|uniq`
>                do umount -rf $i
>            done
>            echo 0 > /proc/diag/led/power
>            ifdown wan
>          }
>
> reboot() { romount > /dev/null 2>&1
>           /sbin/reboot
>           /etc/init.d/sshd stop
>           exit
>         }
>
> poweroff() { romount > /dev/null 2>&1
>             /sbin/poweroff
>             /etc/init.d/sshd stop
>             exit
>           }
>
>
> greets
>
>
> Am Samstag 30 Januar 2010 14:13:57 schrieb edgar.sol...@web.de:
>> Is there a sync command before the unmount?
>>
>> Maybe the system does not reach the umount call, and therefor it is
>> never cleanly unmounted? You could debug that.
>>
>> Maybe the controller is caching and needs specific commands to write the
>> cache to disc? Did you search the web?
>>
>> good luck, ede
>>
>> On 30.01.2010 00:11, Gerlando Falauto wrote:
>> > Hi all,
>> >
>> > I am (slowly) experimenting with my LaCie Ethernet Disk Mini v2 NAS.
>> > In order to maintain compatibility with Lacie's software, I did not
>> > change the disk layout (yet).
>> > I can run my own OpenWRT without disrupting the original firmware
>> > by putting the kernel's uImage on [sda9]/snaps/00/boot and the root
>> > filesystem on [sda2] which is an xfs partition (it's the 300GB user
>> > partition) mounted as read/write.
>> >
>> > Now every time I shutdown the box, my xfs filesystem gets corrupted
>> > and at the next reboot
>> > kernel ends up panicking because it can't mount the root filesystem to
>> > find an init file.
>> >
>> > I figured the shutdown sequence did not correctly unmount my filesystem;
>> > I found the executed command was "umount -a -r", so I tried doing it
>> > manually:
>> >
>> > r...@openwrt:~# umount -a -r
>> > umount: devpts busy - remounted read-only
>> > umount: tmpfs busy - remounted read-only
>> > umount: tmpfs busy - remounted read-only
>> > umount: can't remount /dev/root read-only
>> > umount: can't remount rootfs read-only
>> >
>> > r...@openwrt:~# mount -t proc proc /proc
>> > r...@openwrt:~# umount -r /
>> > umount: can't remount /dev/root read-only
>> >
>> > I know that mounting the initial root filesystem as read-write is not
>> > a very nice thing to do,
>> > but could someone please point out why it's, like, forbidden by law,
>> > so that I even get punished for doing it?
>> >
>> > Thanks a lot!
>> > Gerlando
>> > ___
>> > openwrt-devel mailing list
>> > openwrt-devel@lists.openwrt.org
>> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Creating Patch Team

[Luigi Mantellini]

On Sat, Jan 30, 2010 at 11:25 AM, Weedy  wrote:
>
> https://dev.openwrt.org/wiki/GetSource --> git://nbd.name/openwrt.git
> --
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?

I know this link... but using git like just a "SVN" site doesn't
permit to have a complete git-like workflow (like u-boot and linux
kernel projects).
For example, using a full featured git repo, you can have a
fork/branch for each "topic": a branch/fork for the
"toolchain"-related patches, a fork for the "internal infrastructure",
a fork for some class of platform (arm, x86, mips, ...) and provide a
development cycle that merge periodically (during a merge window) the
various flows in order to have a release.

I'm not speaking to use the word "git" instead the word "svn" but I'm
speaking regarding the dev workflow.

my 2EuroCents,

ciao

luigi

-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Creating Patch Team

[Luigi Mantellini]

This may be a good idea... but can you switch to git as main control version?

Git permits a more collaborative approach and, using tools like
git-am, git-format-patch, ... make live easy.

ciao

luigi

On Sat, Jan 30, 2010 at 11:00 AM, Weedy  wrote:
> On Fri, Jan 29, 2010 at 2:35 PM, Travis Kemen  wrote:
>> We are looking for 2-3 people that would be willing to help test patches on
>> the mailing list and trac as well as help communicate with developers and
>> patch submitters what the status of their patch is. The goal of this group
>> is to help stem the tide of unanswered tickets and patches. If you are
>> interested please let me know by replying to this to by private email.
>>
>> Thanks
>>
>> Travis Kemen
>> OpenWrt Developer
>>
> I'm bored, sign me up.
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Regarding "make all / make install" usage

[Luigi Mantellini]

These are my patches that (1) enable distcc, (2) parallel make and (3)
fix package to be parallel-make-aware.

ciao

luigi

On Wed, Oct 28, 2009 at 9:56 PM, Michael Buesch  wrote:
> On Wednesday 28 October 2009 21:29:10 Felix Fietkau wrote:
>> Michael Buesch wrote:
>> > On Wednesday 28 October 2009 03:04:41 Felix Fietkau wrote:
>> >> > That would be a huge advantage and speedup the openwrt buildprocess by
>> >> > about 35-40 percent points on my quad machine. The advantage gets 
>> >> > higher the more cores we have.
>> >> > And I think quads are not that uncommon anymore today.
>> >> Why do you think the difference is that big between building multiple
>> >> packages at the same time and building individual packages in parallel?
>> >
>> > Because the cpu utilization is horribly low during an openwrt build.
>> > It ranges from 25% for the toolchain to 99% for the kernel.
>> > For compiling "normal" packages there's usually an overall utilization of 
>> > 60-75%. I'm pretty sure
>> > if we'd allow two processors (or more) on one package at the same time, it 
>> > would go up to nearly 99%
>> > on my machine. Especially for bigger packages like busybox, ssh, etc...
>> > I'd also like to have an optional (default off) parallel build of the 
>> > toolchain. I don't mind
>> > poking it two or three times. That'd still be faster than compiling the 
>> > whole toolchain at 25%.
>> I did a test with all packages of trunk selected (/packages not
>> included), and 3 packages broke with very weird build failures.
>> This was with a small change to include/package.mk that sets
>> MAKE := $(MAKE) -j 8
>> and some other patches to replace $(MAKE) all install calls with
>> multiple calls.
>> The three packages that broke were apex, iproute2, openssl. Also when
>> I've done similar tests in the past, some other packages also broke,
>> though only under rare, hard to trigger circumstances.
>> If somebody makes a patch that enables package build parallelization, I
>> definitely don't want to have this enabled by default whenever somebody
>> does make -j in the OpenWrt build system.
>> I think most people that use make -j would prefer to have something that
>> may be a little slower, but doesn't cause unexpected build failures
>> depending on the parallelization level.
>
> Yeah. I'm fine with an option that defaults to off and has a big warning 
> message.
> However, I don't know the buildsystem good enough to add such an option and
> proper parallelization...
>
> --
> Greetings, Michael.
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com


0001-Enable-the-following-packages-to-parallel-make.patch
Description: Binary data


0002-Add-support-for-parallel-make-and-distcc.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Regarding "make all / make install" usage

[Luigi Mantellini]

I fixed some package (with small patches). I will send tomorrow my
proposed patches.

best regards,

luigi

On Wed, Oct 28, 2009 at 9:29 PM, Felix Fietkau  wrote:
> Michael Buesch wrote:
>> On Wednesday 28 October 2009 03:04:41 Felix Fietkau wrote:
>>> > That would be a huge advantage and speedup the openwrt buildprocess by
>>> > about 35-40 percent points on my quad machine. The advantage gets higher 
>>> > the more cores we have.
>>> > And I think quads are not that uncommon anymore today.
>>> Why do you think the difference is that big between building multiple
>>> packages at the same time and building individual packages in parallel?
>>
>> Because the cpu utilization is horribly low during an openwrt build.
>> It ranges from 25% for the toolchain to 99% for the kernel.
>> For compiling "normal" packages there's usually an overall utilization of 
>> 60-75%. I'm pretty sure
>> if we'd allow two processors (or more) on one package at the same time, it 
>> would go up to nearly 99%
>> on my machine. Especially for bigger packages like busybox, ssh, etc...
>> I'd also like to have an optional (default off) parallel build of the 
>> toolchain. I don't mind
>> poking it two or three times. That'd still be faster than compiling the 
>> whole toolchain at 25%.
> I did a test with all packages of trunk selected (/packages not
> included), and 3 packages broke with very weird build failures.
> This was with a small change to include/package.mk that sets
> MAKE := $(MAKE) -j 8
> and some other patches to replace $(MAKE) all install calls with
> multiple calls.
> The three packages that broke were apex, iproute2, openssl. Also when
> I've done similar tests in the past, some other packages also broke,
> though only under rare, hard to trigger circumstances.
> If somebody makes a patch that enables package build parallelization, I
> definitely don't want to have this enabled by default whenever somebody
> does make -j in the OpenWrt build system.
> I think most people that use make -j would prefer to have something that
> may be a little slower, but doesn't cause unexpected build failures
> depending on the parallelization level.
>
> - Felix
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC] Use xv utils instead lzma

[Luigi Mantellini]

On Sun, Oct 25, 2009 at 3:19 PM, Felix Fietkau  wrote:
>> Can we plan to integrate xz utils in the next future? (deprecating
>> lzma and lzma-old packages).
> We need the lzma library anyway (for squashfs). What advantages are
> there to using the xz utility?

xz (formerly lzma-utils) contains the lzma library and  the complete
application suite to manage the lzma files (lzma alone), also using
the standard gzip cmdline interface (as linux kernel likes).

I know that it's just an alternative... for this reason I'm asking for
a ml opinion.

:)

ciao

luigi

>
> - Felix
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [RFC] Use xv utils instead lzma

[Luigi Mantellini]

Hi

xv format (and related utils) are mode on lzma sdk. These utils also
support the classical lzma alone format and have a gzip-like command
interface.

More information: http://tukaani.org/xz/

Can we plan to integrate xz utils in the next future? (deprecating
lzma and lzma-old packages).

thanks for any comments.

ciao

luigi

-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC] Distcc support - Patchset V5

[Luigi Mantellini]

Hi All,

These patches add:
  1) suport for parallel make (inner package)
  2) distcc support
  3) fix package to be build using parallel make

Any feedback is welcome.

ciao

luigi

On Sun, Oct 18, 2009 at 12:07 PM, Luigi Mantellini
 wrote:
> Hi ml,
>
> As we have the external toolchain support, we can consider to add a
> distcc support.
> I produced the following patch that I never tested yet!
>
> Just some information:
>  - distcc must be usable only if EXTERNAL_TOOLCHAIN is used (it's
> mandatory to have the same compiler on all hosts...)
>  - pump mode is not usable if ccache is also enabled (is it true?)
>
> Consider it like a proof-of-concept and any feedback/suggestion is welcome.
>
> best regards and ciao
>
> luigi
>
>
> NB.: The copyright is 2009 (C) Industrie Dial Face S.p.A. and all is
> released under GPL! (I remark this because somebody suggest me to read
> the GPL...)
>
> --
> Luigi 'Comio' Mantellini
> R&D - Software
> Industrie Dial Face S.p.A.
> Via Canzo, 4
> 20068 Peschiera Borromeo (MI), Italy
>
> Tel.: +39 02 5167 2813
> Fax: +39 02 5167 2459
> web: www.idf-hit.com
> mail: luigi.mantell...@idf-hit.com
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com


0001-Add-support-for-distcc-a-fast-free-distributed-C-C-c.patch
Description: Binary data


0002-Fix-some-packages-to-support-parallel-make.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC] Distcc support

[Luigi Mantellini]

Hi Felix,

On Sun, Oct 18, 2009 at 6:39 PM, Felix Fietkau  wrote:
> Yep, sounds good. By the way, I'm currently working on integrating a gcc
> version with CodeSourcery patches into OpenWrt. Maybe that way you also
> won't have to use external toolchains anymore. I've stripped the diff of

No :) I will use the external toolchain because I need to have the
same environment shared a lot of developers
and use a toolchain provided by a contractor.

> the latest codesourcery toolchain against upstream gcc 4.3.3 down to
> around 2M in size and merged it with our other patches. I'm currently
> checking whether it compiles...

Auguri! it should be an hard task.

ciao

luigi

PS: I modified again the patch (s/FAST_MAKE/MAKE/g is the first
mistake...) and I compiled with success a mips board. I'm still
thinking how to implement the dist-compiler checking.
>
> - Felix
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC] Distcc support

[Luigi Mantellini]

new patch v2

enjoy

On Sun, Oct 18, 2009 at 12:07 PM, Luigi Mantellini
 wrote:
> Hi ml,
>
> As we have the external toolchain support, we can consider to add a
> distcc support.
> I produced the following patch that I never tested yet!
>
> Just some information:
>  - distcc must be usable only if EXTERNAL_TOOLCHAIN is used (it's
> mandatory to have the same compiler on all hosts...)
>  - pump mode is not usable if ccache is also enabled (is it true?)
>
> Consider it like a proof-of-concept and any feedback/suggestion is welcome.
>
> best regards and ciao
>
> luigi
>
>
> NB.: The copyright is 2009 (C) Industrie Dial Face S.p.A. and all is
> released under GPL! (I remark this because somebody suggest me to read
> the GPL...)
>
> --
> Luigi 'Comio' Mantellini
> R&D - Software
> Industrie Dial Face S.p.A.
> Via Canzo, 4
> 20068 Peschiera Borromeo (MI), Italy
>
> Tel.: +39 02 5167 2813
> Fax: +39 02 5167 2459
> web: www.idf-hit.com
> mail: luigi.mantell...@idf-hit.com
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com


0001-Add-distcc-support.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC] Distcc support

[Luigi Mantellini]

Hi  Daniel,

to have a consistent build it's mandatory to have the same toolchain.
For this reason I think that distcc should be used only under this
hypothesis.
I'm using the external toolchain support and it works fine (I used
ELDK's and CodeSourcery's toolchains with good results).

I'm not sure if cerate a tools package for distcc is a good idea or
just add a prereq-build rule.

my2EuroCents,

luigi


On Sun, Oct 18, 2009 at 12:37 PM, poelzi  wrote:
> Luigi Mantellini wrote:
>
>> As we have the external toolchain support, we can consider to add a
>> distcc support.
>> I produced the following patch that I never tested yet!
>>
>> Just some information:
>>   - distcc must be usable only if EXTERNAL_TOOLCHAIN is used (it's
>> mandatory to have the same compiler on all hosts...)
>
> i would love to see distcc support and was thinking about it long ago :-)
>
> but one suggestion: I think requireing a external toolchain is not a
> good idea as openwrt is designed for building its chain itself. As
> distcc is a special case anyways i think it would be ok to make some
> simple assumptions like each host in the distcc cluster does have the
> same path to the openwrt buildchain and the same architecture. this
> would allow to use the openwrt buildchain on all computers with the same
> architecture at least. i think starting on an a 32 bit linux should also
> allow running the chain on a 64 bit system when the 32 bit libs are
> installed. maybe compiling static toolchain and forcing them to be 32
> bit would be a cool option in the future.
>
> kindly regards
>  daniel
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC] Distcc support

[Luigi Mantellini]

first mistake: add a "\" after $(MAKE_DISTCC_VARS) into package-defaults.mk

I already said that I never tested ! ;) eheh

ciao

On Sun, Oct 18, 2009 at 12:07 PM, Luigi Mantellini
 wrote:
> Hi ml,
>
> As we have the external toolchain support, we can consider to add a
> distcc support.
> I produced the following patch that I never tested yet!
>
> Just some information:
>  - distcc must be usable only if EXTERNAL_TOOLCHAIN is used (it's
> mandatory to have the same compiler on all hosts...)
>  - pump mode is not usable if ccache is also enabled (is it true?)
>
> Consider it like a proof-of-concept and any feedback/suggestion is welcome.
>
> best regards and ciao
>
> luigi
>
>
> NB.: The copyright is 2009 (C) Industrie Dial Face S.p.A. and all is
> released under GPL! (I remark this because somebody suggest me to read
> the GPL...)
>
> --
> Luigi 'Comio' Mantellini
> R&D - Software
> Industrie Dial Face S.p.A.
> Via Canzo, 4
> 20068 Peschiera Borromeo (MI), Italy
>
> Tel.: +39 02 5167 2813
> Fax: +39 02 5167 2459
> web: www.idf-hit.com
> mail: luigi.mantell...@idf-hit.com
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [RFC] Distcc support

[Luigi Mantellini]

Hi ml,

As we have the external toolchain support, we can consider to add a
distcc support.
I produced the following patch that I never tested yet!

Just some information:
  - distcc must be usable only if EXTERNAL_TOOLCHAIN is used (it's
mandatory to have the same compiler on all hosts...)
  - pump mode is not usable if ccache is also enabled (is it true?)

Consider it like a proof-of-concept and any feedback/suggestion is welcome.

best regards and ciao

luigi


NB.: The copyright is 2009 (C) Industrie Dial Face S.p.A. and all is
released under GPL! (I remark this because somebody suggest me to read
the GPL...)

-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com


0001-Add-distcc-support.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] how to manage kernel repos while develop openwrt?

[Luigi Mantellini]

Hi All,

I think that OpenWRT should improve git sources trees support in order
to keep a clone instead a snapshot. One year ago I worked on some
(dirty) patch in order to have a sort of "dev-mode" where the packages
(and kernel) are keep using the git (not just the snapshot). I will
try to resume these patch and I will send again.

This is my usual objection: OpenWRT is powerful build system but the
git/svn support should be made really usable.

my 2EuroCents.

best regards,

luigi

2009/10/3 xiangfu liu :
> Hi
> I try to translate this email. I think it's ok to send to mailing list. :-)
>
> -
> Hi xiangfu
>
> I check your company wiki and blog (http://www.qi-hardware.com)
> the [copyleft hardware] is a good idea.
>
> openwrt manage source code by patch. from kernel to application.
> you can svn co trunk, then create your own patch
>
> we use Micrel chip KSZ8692XPB
> http://www.micrel.com/_PDF/Ethernet/ethernet_datasheet/index.html
> http://www.micrel.com/_PDF/Ethernet/ethernet_designkit/8692/
>
> they use Openwrt as the SDK.
> then use a script put their patches to opnewrt 8.09
> but openwrt not fix all device, most of the device in openwrt is Router.
>
>  BTW: I just login the qi hardware IRC. nobody in there now :-)
>> 你好,刘向福.
>>
>> 我看了你们的wiki和 blog
>> 硬件上版权的开放我还第一次听说.
>> 是个好想法. :-)
>>
>> OPENWRT一堆 patch.
>> 从kernel到 APP.
>>
>> 你可以svn co trunk,然后自己也可以添加Patch进去.
>>
>> 我使用Micrel  一个芯片   KSZ8692XPB
>>  http://www.micrel.com/_PDF/Ethernet/ethernet_datasheet/index.html
>>
>>  http://www.micrel.com/_PDF/Ethernet/ethernet_designkit/8692/
>>
>> 他们使用了 openwrt作为SDK.
>> 然后自己写个简单的脚本,把自己的patch添加到 openwrt当前的主线当中(8.09).
>>
>> 只不过 Openwrt并不是适合所有的硬件设备,
> 因为毕竟面向的绝大部分是 ROUTE设备.
>>
>> BTW:刚刚加入进你们的IRC,很可惜,暂时没看到有人在. 呵呵.
>>
>> 继续关注你们.



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] how to manage kernel repos while develop openwrt?

[Luigi Mantellini]

Can you translate in english?

thanks

luigi

On Fri, Oct 2, 2009 at 6:05 AM, linux_pro  wrote:
> 你好,刘向福.
>
> 我看了你们的wiki和 blog
> 硬件上版权的开放我还第一次听说.
> 是个好想法. :-)
>
> OPENWRT一堆 patch.
> 从kernel到 APP.
>
> 你可以svn co trunk,然后自己也可以添加Patch进去.
>
> 我使用Micrel  一个芯片   KSZ8692XPB
>  http://www.micrel.com/_PDF/Ethernet/ethernet_datasheet/index.html
>
>  http://www.micrel.com/_PDF/Ethernet/ethernet_designkit/8692/
>
> 他们使用了 openwrt作为SDK.
> 然后自己写个简单的脚本,把自己的patch添加到 openwrt当前的主线当中(8.09).
>
> 只不过 Openwrt并不是适合所有的硬件设备,因为毕竟面向的绝大部分是 ROUTE设备.
>
> BTW:刚刚加入进你们的IRC,很可惜,暂时没看到有人在. 呵呵.
>
> 继续关注你们.
> 2009/10/2 xiangfu liu :
>> Hi
>>
>> we(Qi Hardware) are use openwrt as the code repos. for the kernel develop
>> there are four team work on the similar kernel.
>>
>> since the device use the same cpu. we want merge the four team to one
>> kernel. then we can help each other when develop kernel.
>>
>> we can ask other three team to use openwrt. so is there a good way to resolve
>> the problem?
>>
>> are you all use openwrt's patches to manage the kernel source cdoe?
>>
>> do you use git when create the openwrt patches?
>>
>> I saw there is "Use external kernel tree (NEW)"  option in openwrt. is this 
>> fit
>> the situation?
>>
>> we can use a git to manage the kernel, we must have one to create the
>> patches for openwrt? right?
>>
>> give some advice thanks.
>>
>> Best Regards
>> Xiangfu
>> --
>> Blog: http://www.openmobilefree.net
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] How to strip correctly?

[Luigi Mantellini]

My opinion is to remove stripping from source makefiles and use only
OpenWRT mechanism to generate stripped elf.

my2EuroCents,

luiig

On Fri, Sep 25, 2009 at 1:17 PM, Matthias Buecher / Germany
 wrote:
> Some packages have strip errors with the original makefile (e.g. sslh,
> proftpd). Now I want to know how to handle this correctly for OpenWrt.
>
> Possible solutions:
> #1
> Remove strip with a patch as stripping is handled separately by OpenWrt
> (is it?)
>
>
> #2
> Fix strip with a patch by using OpenWrt's $(STRIP) substitution.
> (how this has to look like if no strip is selected?)
>
>
> #3
> Install "binutils-multiarch" (here Debian) to make it build with regular
> strip.
> (package not yet a pre-requisition)
>
>
> Your answers will make my future patches more correct and fitting the
> OpenWrt development guide line?
>
> Kind regards
> Matthias "Maddes" Bücher
>
> --
> http://www.maddes.net/
> Home: Earth / Germany / Ruhr-Area
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] Update dtc to v1.2

[Luigi Mantellini]

Find the attached patch to upgrade the Device Tree Compiler up to v1.2.
Best regards,

luigi

-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com


0001-Update-Device-Tree-Compiler-to-1.2.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Regarding external cross-toolchain

[Luigi Mantellini]

I lost some word...

Hi All,

I rebased the patch on the last tr...@17618. I hope to see the
external-toolchain patch in the main line.

best regards,

luigi

On Sun, Sep 20, 2009 at 5:15 PM, Luigi Mantellini
 wrote:
> Hi All,
>
> I rebased the patch on the last tr...@17618 the external-toolchain
> patch in the main line.
>
> best regards,
>
> luigi
>
> On Thu, Sep 10, 2009 at 12:56 AM, Luigi Mantellini
>  wrote:
>> Thanks :D
>>
>> On Thu, Sep 10, 2009 at 12:17 AM, Nico wrote:
>>> Hi Luigi,
>>>
>>> There were no particular reasons preventing external toolchain support
>>> from hitting trunk apart from a constant lack of time on my side...
>>>
>>> I'll try my best to have it commited by the end of the week.
>>>
>>> Thanks for your help and support !
>>>
>>> Regards,
>>> --
>>> Nico
>>>
>>>
>>> Luigi 'Comio' Mantellini wrote:
>>>> Hi List,
>>>> Hi Nico,
>>>>
>>>> find the attached my contribute.
>>>> Starting from nico's patch I build this patchset that adds the ability to 
>>>> use
>>>> use an external toolchain (rebased on r17459).
>>>>
>>>> I compiled a simple ppc440 target with and without the external toolchain
>>>> usage and it seems to work fine. As external toolchain I used the 
>>>> CodeSourcery
>>>> G++lite 4.3-50 for Power EABI
>>>> (http://www.codesourcery.com/sgpp/lite/power/portal/release603).
>>>>
>>>> Find also the config.external and config.normal configs to look my board 
>>>> setup.
>>>>
>>>> My wish is to see this patch in the main-line as soon possible because is 
>>>> very
>>>> important for my job.
>>>>
>>>> Any feedback is welcome.
>>>>
>>>> best regards,
>>>>
>>>> luigi
>>>>
>>>>
>>>>
>>>> Il domenica 6 settembre 2009 20:26:46 Luigi Mantellini ha scritto:
>>>>
>>>>> Hi List,
>>>>>
>>>>> as in the past I will ask again opinions regarding the optional
>>>>> support for external cross-toolchain.
>>>>>
>>>>> Reading the dev.openwrt.org I see:
>>>>>
>>>>> "OpenWrt is currently being used in industrial control systems, small
>>>>> robots, sensor networks, home control solutions, VoIP systems, both
>>>>> wired and wireless networks and a whole lot more."
>>>>>
>>>>> I'm working on network devices and usually I receive from my vendors
>>>>> the BSP and toolchain that is considered "official" and "safe" for the
>>>>> BSP. My suppliers usually don't accent to support BSP (and anwser to
>>>>> my questions) if I don't use the provided toolchain.
>>>>>
>>>>> From these considerations, My opinion is that external target-specific
>>>>> toolchian should be supported by OpenWRT avoiding to compile everytime
>>>>> the toolchain.
>>>>>
>>>>> In past Nico sent a set of patch for support this feature but I think
>>>>> that are not included yet in the mainline.
>>>>>
>>>>> Nico, can you provide me your last patches? and explain if them will
>>>>> be included or not?
>>>>>
>>>>> thanks in advance and best regards,
>>>>>
>>>>> luigi
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> ___
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>>
>>
>>
>>
>> --
>> Luigi 'Comio' Mantellini
>> R&D - Software
>> Industrie Dial Face S.p.A.
>> Via Canzo, 4
>> 20068 Peschiera Borromeo (MI), Italy
>>
>> Tel.: +39 02 5167 2813
>> Fax: +39 02 5167 2459
>> web: www.idf-hit.com
>> mail: luigi.mantell...@idf-hit.com
>>
>
>
>
> --
> Luigi 'Comio' Mantellini
> R&D - Software
> Industrie Dial Face S.p.A.
> Via Canzo, 4
> 20068 Peschiera Borromeo (MI), Italy
>
> Tel.: +39 02 5167 2813
> Fax: +39 02 5167 2459
> web: www.idf-hit.com
> mail: luigi.mantell...@idf-hit.com
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Regarding external cross-toolchain

[Luigi Mantellini]

Hi All,

I rebased the patch on the last tr...@17618 the external-toolchain
patch in the main line.

best regards,

luigi

On Thu, Sep 10, 2009 at 12:56 AM, Luigi Mantellini
 wrote:
> Thanks :D
>
> On Thu, Sep 10, 2009 at 12:17 AM, Nico wrote:
>> Hi Luigi,
>>
>> There were no particular reasons preventing external toolchain support
>> from hitting trunk apart from a constant lack of time on my side...
>>
>> I'll try my best to have it commited by the end of the week.
>>
>> Thanks for your help and support !
>>
>> Regards,
>> --
>> Nico
>>
>>
>> Luigi 'Comio' Mantellini wrote:
>>> Hi List,
>>> Hi Nico,
>>>
>>> find the attached my contribute.
>>> Starting from nico's patch I build this patchset that adds the ability to 
>>> use
>>> use an external toolchain (rebased on r17459).
>>>
>>> I compiled a simple ppc440 target with and without the external toolchain
>>> usage and it seems to work fine. As external toolchain I used the 
>>> CodeSourcery
>>> G++lite 4.3-50 for Power EABI
>>> (http://www.codesourcery.com/sgpp/lite/power/portal/release603).
>>>
>>> Find also the config.external and config.normal configs to look my board 
>>> setup.
>>>
>>> My wish is to see this patch in the main-line as soon possible because is 
>>> very
>>> important for my job.
>>>
>>> Any feedback is welcome.
>>>
>>> best regards,
>>>
>>> luigi
>>>
>>>
>>>
>>> Il domenica 6 settembre 2009 20:26:46 Luigi Mantellini ha scritto:
>>>
>>>> Hi List,
>>>>
>>>> as in the past I will ask again opinions regarding the optional
>>>> support for external cross-toolchain.
>>>>
>>>> Reading the dev.openwrt.org I see:
>>>>
>>>> "OpenWrt is currently being used in industrial control systems, small
>>>> robots, sensor networks, home control solutions, VoIP systems, both
>>>> wired and wireless networks and a whole lot more."
>>>>
>>>> I'm working on network devices and usually I receive from my vendors
>>>> the BSP and toolchain that is considered "official" and "safe" for the
>>>> BSP. My suppliers usually don't accent to support BSP (and anwser to
>>>> my questions) if I don't use the provided toolchain.
>>>>
>>>> From these considerations, My opinion is that external target-specific
>>>> toolchian should be supported by OpenWRT avoiding to compile everytime
>>>> the toolchain.
>>>>
>>>> In past Nico sent a set of patch for support this feature but I think
>>>> that are not included yet in the mainline.
>>>>
>>>> Nico, can you provide me your last patches? and explain if them will
>>>> be included or not?
>>>>
>>>> thanks in advance and best regards,
>>>>
>>>> luigi
>>>>
>>>>
>>>
>>>
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>
>
>
> --
> Luigi 'Comio' Mantellini
> R&D - Software
> Industrie Dial Face S.p.A.
> Via Canzo, 4
> 20068 Peschiera Borromeo (MI), Italy
>
> Tel.: +39 02 5167 2813
> Fax: +39 02 5167 2459
> web: www.idf-hit.com
> mail: luigi.mantell...@idf-hit.com
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com


0001-toolchain-Add-external-toolchain-support.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Regarding external cross-toolchain

[Luigi Mantellini]

Thanks :D

On Thu, Sep 10, 2009 at 12:17 AM, Nico wrote:
> Hi Luigi,
>
> There were no particular reasons preventing external toolchain support
> from hitting trunk apart from a constant lack of time on my side...
>
> I'll try my best to have it commited by the end of the week.
>
> Thanks for your help and support !
>
> Regards,
> --
> Nico
>
>
> Luigi 'Comio' Mantellini wrote:
>> Hi List,
>> Hi Nico,
>>
>> find the attached my contribute.
>> Starting from nico's patch I build this patchset that adds the ability to use
>> use an external toolchain (rebased on r17459).
>>
>> I compiled a simple ppc440 target with and without the external toolchain
>> usage and it seems to work fine. As external toolchain I used the 
>> CodeSourcery
>> G++lite 4.3-50 for Power EABI
>> (http://www.codesourcery.com/sgpp/lite/power/portal/release603).
>>
>> Find also the config.external and config.normal configs to look my board 
>> setup.
>>
>> My wish is to see this patch in the main-line as soon possible because is 
>> very
>> important for my job.
>>
>> Any feedback is welcome.
>>
>> best regards,
>>
>> luigi
>>
>>
>>
>> Il domenica 6 settembre 2009 20:26:46 Luigi Mantellini ha scritto:
>>
>>> Hi List,
>>>
>>> as in the past I will ask again opinions regarding the optional
>>> support for external cross-toolchain.
>>>
>>> Reading the dev.openwrt.org I see:
>>>
>>> "OpenWrt is currently being used in industrial control systems, small
>>> robots, sensor networks, home control solutions, VoIP systems, both
>>> wired and wireless networks and a whole lot more."
>>>
>>> I'm working on network devices and usually I receive from my vendors
>>> the BSP and toolchain that is considered "official" and "safe" for the
>>> BSP. My suppliers usually don't accent to support BSP (and anwser to
>>> my questions) if I don't use the provided toolchain.
>>>
>>> From these considerations, My opinion is that external target-specific
>>> toolchian should be supported by OpenWRT avoiding to compile everytime
>>> the toolchain.
>>>
>>> In past Nico sent a set of patch for support this feature but I think
>>> that are not included yet in the mainline.
>>>
>>> Nico, can you provide me your last patches? and explain if them will
>>> be included or not?
>>>
>>> thanks in advance and best regards,
>>>
>>> luigi
>>>
>>>
>>
>>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Regarding external cross-toolchain

[Luigi Mantellini]

Hi List,

as in the past I will ask again opinions regarding the optional
support for external cross-toolchain.

Reading the dev.openwrt.org I see:

"OpenWrt is currently being used in industrial control systems, small
robots, sensor networks, home control solutions, VoIP systems, both
wired and wireless networks and a whole lot more."

I'm working on network devices and usually I receive from my vendors
the BSP and toolchain that is considered "official" and "safe" for the
BSP. My suppliers usually don't accent to support BSP (and anwser to
my questions) if I don't use the provided toolchain.

>From these considerations, My opinion is that external target-specific
toolchian should be supported by OpenWRT avoiding to compile everytime
the toolchain.

In past Nico sent a set of patch for support this feature but I think
that are not included yet in the mainline.

Nico, can you provide me your last patches? and explain if them will
be included or not?

thanks in advance and best regards,

luigi

-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Add colorization support for gcc/g++ compiler

[Luigi Mantellini]

Hi List,

this patch add support for the gcc output colorization using a little
modified colorgcc script.

The our compiling activities will be more exciting :)

best regards,

luigi


-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com


0001-Add-colorization-support-for-gcc-g-compiler.patch.gz
Description: GNU Zip compressed data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #4940: Request for newer lzma package

[Luigi Mantellini]

see this https://dev.openwrt.org/ticket/4847

On Tue, Apr 14, 2009 at 4:05 AM, OpenWrt
 wrote:
> #4940: Request for newer lzma package
> +---
>  Reporter:  ya...@…                 |       Owner:  developers
>     Type:  enhancement             |      Status:  new
>  Priority:  normal                  |   Milestone:  Kamikaze
> Component:  toolchain               |     Version:  Trunk
>  Keywords:  lzma                    |
> +---
>  Hi, I've just recently started playing with OpenWrt (thanks to
>  www.bifferos.com) and noticed that OpenWrt is using a ''really'' old
>  version of the lzma package. history.txt inside
>  http://downloads.openwrt.org/sources/lzma432.tar.bz2 (referenced by
>  /trunk/tools/lzma/Makefile) dates from 2005-12-09! Newer versions are
>  available from http://tukaani.org/lzma/download and this appears to be the
>  'standard source' for linux lzma packages.
>
>  Why is this relevant? Well apart from the fact the current OpenWrt package
>  is 3 years old, the newer packages have much nicer gzip-like command line
>  syntax. And in linux kernel 2.6.30 they've integrated 'bzip2-lzma-for-
>  linus' which provides kernel compression in bzip and lzma formats (similar
>  to https://dev.openwrt.org/changeset/14890), and this obviously uses the
>  newer-lzma syntax.
>  http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.30-rc1
>
>
>  So in order for OpenWrt to be able to compile linux 2.6.30, you'll either
>  need to update your ancient lzma package, or patch the kernel's Makefile
>  to use the horrible syntax of your current lzma package ;-)
>
> --
> Ticket URL: 
> OpenWrt 
> Opensource Wireless Router Technology
> ___
> openwrt-tickets mailing list
> openwrt-tick...@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-tickets
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #4809: uClibc daemon/pthred fix (need on 0.9.29 and 0.9.30)

[Luigi Mantellini]

Any news?
I noticed that a uclibc nptl support is pushed in last time into
openwrt... anyway can you evaluate to integrate these patches for
0.9.29 and 0.9.30?

thanks a lot

luigi

On Sat, Mar 21, 2009 at 11:22 PM, OpenWrt
 wrote:
> #4809: uClibc daemon/pthred fix (need on 0.9.29 and 0.9.30)
> -+--
>  Reporter:  Luigi 'Comio' Mantellini   |        
> Owner:  developers
>     Type:  defect                                                   |       
> Status:  new
>  Priority:  highest                                                  |    
> Milestone:  Kamikaze
> Component:  toolchain                                                |   
> Resolution:
>  Keywords:  daemon uclibc                                            |
> -+--
>
> Comment(by luigi.mantell...@idf-hit.com):
>
>  This patch covers changes like: https://dev.openwrt.org/changeset/13712
>  and many other.
>
>  Let me say that the final solution is to switch to nptl (when it will be
>  available... mena carmelo!)
>
>
>  ciao
>
>  luigi
>
> --
> Ticket URL: 
> OpenWrt 
> Opensource Wireless Router Technology
> ___
> openwrt-tickets mailing list
> openwrt-tick...@lists.openwrt.org
> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] uclibc-0.9.30 compilation fails

[Luigi Mantellini]

The patches are for uClibc 0.9.30.1. Change your .config adding:

CONFIG_UCLIBC_EXTRA_VERSION=".1"

ciao

luigi

On Sun, Mar 29, 2009 at 1:57 PM, Michael Buesch  wrote:
> /develop/svn/openwrt_wap54g/trunk/staging_dir/toolchain-mipsel_gcc-4.3.3_uClibc-0.9.30/info.mk
> /home/mb/develop/svn/openwrt_wap54g/trunk/staging_dir/host/bin/sed -i -e 
> 's,^\(LIBC_VERSION\)=.*,\1=0.9.30,' 
> /home/mb/develop/svn/openwrt_wap54g/trunk/staging_dir/toolchain-mipsel_gcc-4.3.3_uClibc-0.9.30/info.mk
> /home/mb/develop/svn/openwrt_wap54g/trunk/staging_dir/host/bin/sed -i -e 
> 's,^\(LIBC_PATCHVER\)=.*,\1=,' 
> /home/mb/develop/svn/openwrt_wap54g/trunk/staging_dir/toolchain-mipsel_gcc-4.3.3_uClibc-0.9.30/info.mk
> prepare uClibc version 0.9.30
> bzcat /home/mb/develop/svn/openwrt_dl/uClibc-0.9.30.tar.bz2 | /bin/tar -C 
> /home/mb/develop/svn/openwrt_wap54g/trunk/build_dir/toolchain-mipsel_gcc-4.3.3_uClibc-0.9.30/uClibc-0.9.30/..
>  -xf -
>
> Applying ./patches-0.9.30/110-compat_macros.patch using plaintext:
> patching file include/string.h
>
> Applying ./patches-0.9.30/120-adjtimex.patch using plaintext:
> patching file include/sys/timex.h
> Hunk #1 succeeded at 116 with fuzz 1.
>
> Applying ./patches-0.9.30/130-sockets_throw.patch using plaintext:
> patching file libc/sysdeps/linux/mips/bits/socket.h
> Hunk #1 FAILED at 269.
> 1 out of 1 hunk FAILED -- saving rejects to file 
> libc/sysdeps/linux/mips/bits/socket.h.rej
> Patch failed!  Please fix ./patches-0.9.30/130-sockets_throw.patch!
> make[3]: *** 
> [/home/mb/develop/svn/openwrt_wap54g/trunk/build_dir/toolchain-mipsel_gcc-4.3.3_uClibc-0.9.30/uClibc-0.9.30/.prepareda7863fa5905298a1f0c5dda1163671a2]
>  Error 1
> make[3]: Leaving directory 
> `/home/mb/develop/svn/openwrt_wap54g/trunk/toolchain/uClibc'
> make[2]: *** [toolchain/uClibc/prepare] Error 2
> make[2]: Leaving directory `/home/mb/develop/svn/openwrt_wap54g/trunk'
> make[1]: *** 
> [/home/mb/develop/svn/openwrt_wap54g/trunk/staging_dir/target-mipsel_uClibc-0.9.30/stamp/.toolchain_install]
>  Error 2
> make[1]: Leaving directory `/home/mb/develop/svn/openwrt_wap54g/trunk'
> make: *** [world] Error 2
>
> --
> Greetings, Michael.
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] External cross toolchain

[Luigi Mantellini]

Dear all,


are there any news on this topic?

best regards,

ciao

luigi

On Fri, Feb 6, 2009 at 9:44 AM, Luigi 'Comio' Mantellini
 wrote:
> Dear All,
>
> this is my patch, based on the work of Nico. This patch should be considered
>
> as "what luigi thinks about it".
>
> The patch add the following:
>
> - the v2 patch from Nico
>
> - the TOOLCHAIN_DIR is fixed with respect the EXTERNAL_TOOLCHAIN_ROOT_DIR
>
> - Few package fixes (ie iproute2)
>
> In addition I added a wrapper.sh script used to make the OperWRT SDK a
> usable
>
> external toolchain. This wrapper.sh fixes the sysroot in order to be sure
> that
>
> the correct directory is chosen.
>
> Anyway, I started from Nico v3 patch and I think that the patch v4 is better
>
> for the toolchain directories (LIB, INC, ...) setup.
>
> I hope that my work can be useful for the community.
>
> ciao ciao
>
> luigi
>
>
>
> Il giovedì 05 febbraio 2009 20:29:49 Luigi Mantellini ha scritto:
>
>> I'm preparing a new version of the patch. (I will post tomorrow, now
>
>> I'm at home to wach my cartoons).
>
>>
>
>> Briefly, I added some option to override the sysroot and I also
>
>> modified the gcc Makefile in order to create a toolchain wrapper that
>
>> fixes the sysroot. This change is necessary to use better the
>
>> Openwrt-SDK as an external toolchain. I wil post tomorrow the patch
>
>> and I will try to explain better.
>
>>
>
>> ciao
>
>>
>
>> luigi
>
>>
>
>> 2009/2/5 Florian Fainelli :
>
>> > Hi Nico, Luigi,
>
>> >
>
>> > Le Thursday 05 February 2009 13:29:04 Nico, vous avez écrit :
>
>> >> Hi Luigi,
>
>> >>
>
>> >> following your suggestions, i updated the patch [1] to support a
>
>> >> toolchain root config and added 2 options to specify additional
>
>> >> directories to search for header files and libraries.
>
>> >>
>
>> >> I dropped the LD_LIBRARY_PATH hack as I'm not sure it's actually
>
>> >> useful, but it could easily be added later if it proves it is.
>
>> >
>
>> > Nice work ! I will test your patch.
>
>> > --
>
>> > Best regards, Florian Fainelli
>
>> > Email : flor...@openwrt.org
>
>> > http://openwrt.org
>
>> > ---
>
> --
>
>
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] External cross toolchain

[Luigi Mantellini]

I'm preparing a new version of the patch. (I will post tomorrow, now
I'm at home to wach my cartoons).

Briefly, I added some option to override the sysroot and I also
modified the gcc Makefile in order to create a toolchain wrapper that
fixes the sysroot. This change is necessary to use better the
Openwrt-SDK as an external toolchain. I wil post tomorrow the patch
and I will try to explain better.

ciao

luigi

2009/2/5 Florian Fainelli :
> Hi Nico, Luigi,
>
> Le Thursday 05 February 2009 13:29:04 Nico, vous avez écrit :
>> Hi Luigi,
>>
>> following your suggestions, i updated the patch [1] to support a
>> toolchain root config and added 2 options to specify additional
>> directories to search for header files and libraries.
>>
>> I dropped the LD_LIBRARY_PATH hack as I'm not sure it's actually
>> useful, but it could easily be added later if it proves it is.
>
> Nice work ! I will test your patch.
> --
> Best regards, Florian Fainelli
> Email : flor...@openwrt.org
> http://openwrt.org
> ---
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [rfc] regarding ubifs

[Luigi Mantellini]

Hi Guys,

I would like understand if (and, when and how) the ubifs filesystem
(successor of jffs2) will be supported.

>From my checks, I noticed 3 points where changes will applied in order
to support the ubifs:

 - tools/mtd -> to add host crosstools for make ubifs
 - packages/mtd -> to add target tools to manage ubifs partitions
 - include/* and Makefiles -> to add the needed options

I would like to know tha actual interest on this feature and who is
working on this. Of coure, I will give my contribute to create
proof-of-concept patches.

Thanks for your time,

ciao

luigi


-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Help on initramfs usage

[Luigi Mantellini]

Hi people,

I'm working on a mips based board. I need to create a single file
image (uimage+filesystem) to load on my system (I can choice the
formats). I have the necessity to use a initramfs with a minimal
busybox and some support file to prepare the final root filesystem.

Which is the best way to create a customized initramfs under OpenWRT
that includes a minimal execution environment (minimal busybox,
scritps, ...)? I would avoid to heavy hack the OpenWRT code to meet my
targed.

Thanks in advance for any suggestion.

ciao

luigi

-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #3711: [patch] Support for different Xlibc libraries (glibc, eglibc, ...)

[Luigi Mantellini]

Thanks!

luigi

2009/1/10 OpenWrt :
> #3711: [patch] Support for different Xlibc libraries (glibc, eglibc, ...)
> --+-
>  Reporter:  luigi.mantell...@idf-hit.com  |Owner:  nico
> Type:  enhancement   |   Status:  closed
>  Priority:  high  |Milestone:  Kamikaze
> Component:  toolchain |   Resolution:  fixed
>  Keywords:|
> --+-
> Changes (by nico):
>
>  * status:  assigned => closed
>  * resolution:  => fixed
>
>
> Comment:
>
>  Support for glibc & eglibc added in [13931]
>
> --
> Ticket URL: 
> OpenWrt 
> Opensource Wireless Router Technology
> ___
> openwrt-tickets mailing list
> openwrt-tick...@lists.openwrt.org
> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] OpenWrt development process

[Luigi Mantellini]

Good idea... I sent in the past some patch (like prof of concenpt)
without receiving any feedback... To have an "official" way for the
third-part patches can only improve the development process.

my 2EuroCent.

ciao

luigi


2009/1/6 Jose Vasconcellos :
> Hello to fellow OpenWrt developers!
>
> I would like to start a discussion on how to improve OpenWrt.
> Part of the problem is that I don't fully understand OpenWrt
> as an organization. What are its goals?
>
> It's clear that OpenWrt consists of a core group of developers;
> I've gather this because they have write priviledges to svn.
> What's not obvious is how other developers can help. I think
> a set of guidelines that's needs to be developed to define how
> contributions are handled. I think transparency is key to
> success.
>
> Of course, OpenWrt is not a commercial venture with deadlines
> and deliverables. But some kind of formal organization needs
> to be setup for the long term viability of the project.
>
> Regards,
>
> Jose
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Support for gcc 4.3.2 gcc 4.3.1 uClib 0.9.30 (only mips)

[Luigi Mantellini]

These patches...

2009/1/2 Luigi 'Comio' Mantellini :
> Hi guys,
>
> This patches add the following:
>
> - gcc 4.3.2 and 4.3.1: tested using mips target... should be ok with other
> archs.
>
> - uClibc 0.9.30: only a config for mips is provided... The "pregen" make
> target is removed from the configure time to be sure that a correct syscall
> table is filled.
>
> I tested using the attached config.test file.
>
> ciao
>
> luigi
>
> --
>
> Luigi Mantellini
>
> R&D - Software
>
> Industrie Dial Face S.p.A.
>
> Via Canzo, 4
>
> 20068 Peschiera Borromeo (MI), Italy
>
> Tel.: +39 02 5167 2813
>
> Fax: +39 02 5167 2459
>
> Email: luigi.mantell...@idf-hit.com



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] GCC 4.3.1 support for OpenWRT trunk

[Luigi Mantellini]

Hi guys,

I want just underline that this work is from buildroot project.

thanks

luigi

2008/12/31 Luigi Mantellini :
> This patch adds the gcc4.3.2 support. you need to apply after the
> previous patch (gcc4.3.1 support).
>
> ciao
>
> luigi
>
> 2008/12/30 Luigi 'Comio' Mantellini :
>> Hi guys,
>>
>> this is a patchset to add the gcc4.3.1 support. I tested the patch using a
>> ifx mips target with a 2.6.24 kernel.
>>
>> I know that using old kernels (<2.6.23?) there problem with linking (for
>> some un-resolved symbol).
>>
>> ciao and happy new year.
>>
>> luigi
>>
>> --
>>
>> Luigi Mantellini
>>
>> R&D - Software
>>
>> Industrie Dial Face S.p.A.
>>
>> Via Canzo, 4
>>
>> 20068 Peschiera Borromeo (MI), Italy
>>
>> Tel.: +39 02 5167 2813
>>
>> Fax: +39 02 5167 2459
>>
>> Email: luigi.mantell...@idf-hit.com
>
>
>
> --
> Luigi 'Comio' Mantellini
> R&D - Software
> Industrie Dial Face S.p.A.
> Via Canzo, 4
> 20068 Peschiera Borromeo (MI), Italy
>
> Tel.: +39 02 5167 2813
> Fax: +39 02 5167 2459
> web: www.idf-hit.com
> mail: luigi.mantell...@idf-hit.com
>



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] GCC 4.3.1 support for OpenWRT trunk

[Luigi Mantellini]

This patch adds the gcc4.3.2 support. you need to apply after the
previous patch (gcc4.3.1 support).

ciao

luigi

2008/12/30 Luigi 'Comio' Mantellini :
> Hi guys,
>
> this is a patchset to add the gcc4.3.1 support. I tested the patch using a
> ifx mips target with a 2.6.24 kernel.
>
> I know that using old kernels (<2.6.23?) there problem with linking (for
> some un-resolved symbol).
>
> ciao and happy new year.
>
> luigi
>
> --
>
> Luigi Mantellini
>
> R&D - Software
>
> Industrie Dial Face S.p.A.
>
> Via Canzo, 4
>
> 20068 Peschiera Borromeo (MI), Italy
>
> Tel.: +39 02 5167 2813
>
> Fax: +39 02 5167 2459
>
> Email: luigi.mantell...@idf-hit.com



-- 
Luigi 'Comio' Mantellini
R&D - Software
Industrie Dial Face S.p.A.
Via Canzo, 4
20068 Peschiera Borromeo (MI), Italy

Tel.: +39 02 5167 2813
Fax: +39 02 5167 2459
web: www.idf-hit.com
mail: luigi.mantell...@idf-hit.com
From 72e67e36f697145ecf02c92642fd4d7b696760de Mon Sep 17 00:00:00 2001
From: Luigi 'Comio' Mantellini 
Date: Wed, 31 Dec 2008 00:46:30 +0100
Subject: [PATCH] Add support for GCC 4.3.2

---
 toolchain/gcc/Config.in|4 +
 toolchain/gcc/Config.version   |4 +
 toolchain/gcc/patches/4.3.2/100-uclibc-conf.patch  |   33 +++
 .../patches/4.3.2/104-gnuhurd-uclibc-conf.patch|   13 +
 toolchain/gcc/patches/4.3.2/105-libtool.patch  |   84 ++
 .../gcc/patches/4.3.2/301-missing-execinfo_h.patch |   11 +
 toolchain/gcc/patches/4.3.2/302-c99-snprintf.patch |   13 +
 .../4.3.2/305-libmudflap-susv3-legacy.patch|   49 
 .../patches/4.3.2/810-arm-softfloat-libgcc.patch   |   29 ++
 toolchain/gcc/patches/4.3.2/910-mbsd_multi.patch   |  284 
 .../4.3.2/993-arm_insn-opinit-RTX_CODE-fixup.patch |   41 +++
 toolchain/gcc/patches/4.3.2/995-short-enums.diff   |   42 +++
 .../4.3.2/998-gcc-4.3.0-fix-header.00.patch|   15 +
 toolchain/gcc/patches/4.3.2/999-coldfire.patch |   10 +
 14 files changed, 632 insertions(+), 0 deletions(-)
 create mode 100644 toolchain/gcc/patches/4.3.2/100-uclibc-conf.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/104-gnuhurd-uclibc-conf.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/105-libtool.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/301-missing-execinfo_h.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/302-c99-snprintf.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/305-libmudflap-susv3-legacy.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/810-arm-softfloat-libgcc.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/910-mbsd_multi.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/993-arm_insn-opinit-RTX_CODE-fixup.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/995-short-enums.diff
 create mode 100644 toolchain/gcc/patches/4.3.2/998-gcc-4.3.0-fix-header.00.patch
 create mode 100644 toolchain/gcc/patches/4.3.2/999-coldfire.patch

diff --git a/toolchain/gcc/Config.in b/toolchain/gcc/Config.in
index 80c2e6a..ca0086c 100644
--- a/toolchain/gcc/Config.in
+++ b/toolchain/gcc/Config.in
@@ -27,6 +27,10 @@ choice
 		depends !LINUX_2_4
 		bool "gcc 4.3.1"
 
+	config GCC_VERSION_4_3_2
+		depends !LINUX_2_4
+		bool "gcc 4.3.2"
+
 endchoice
 
 config EABI_SUPPORT
diff --git a/toolchain/gcc/Config.version b/toolchain/gcc/Config.version
index a6771dc..8c64a08 100644
--- a/toolchain/gcc/Config.version
+++ b/toolchain/gcc/Config.version
@@ -4,6 +4,7 @@ config GCC_VERSION
 	default "4.1.2" if GCC_VERSION_4_1_2
 	default "4.2.4" if GCC_VERSION_4_2_4
 	default "4.3.1" if GCC_VERSION_4_3_1
+	default "4.3.2" if GCC_VERSION_4_3_2
 	default "4.1.2"
 
 if !TOOLCHAINOPTS
@@ -25,6 +26,7 @@ config GCC_VERSION_4
 	default y	if GCC_VERSION_4_1_2
 	default y	if GCC_VERSION_4_2_4
 	default y	if GCC_VERSION_4_3_1
+	default y	if GCC_VERSION_4_3_2
 
 config GCC_VERSION_3_4
 	bool
@@ -41,6 +43,7 @@ config GCC_VERSION_4_2
 config GCC_VERSION_4_3
 	bool
 	default y	if GCC_VERSION_4_3_1
+	default y	if GCC_VERSION_4_3_2
 
 config GCC_SUPPORTS_FINEGRAINEDMTUNE
 bool
@@ -48,4 +51,5 @@ config GCC_SUPPORTS_FINEGRAINEDMTUNE
 default n if GCC_VERSION_4_1_2
 default n if GCC_VERSION_4_2_4
 default y if GCC_VERSION_4_3_1
+default y if GCC_VERSION_4_3_2
 	default n
\ No newline at end of file
diff --git a/toolchain/gcc/patches/4.3.2/100-uclibc-conf.patch b/toolchain/gcc/patches/4.3.2/100-uclibc-conf.patch
new file mode 100644
index 000..cca8c82
--- /dev/null
+++ b/toolchain/gcc/patches/4.3.2/100-uclibc-conf.patch
@@ -0,0 +1,33 @@
+--- gcc/gcc/config/--- gcc/contrib/regression/objs-gcc.sh
 gcc/contrib/regression/objs-gcc.sh
+@@ -105,6 +105,10 @@
+  then
+   make all-gdb all-dejagnu all-ld || exit 1
+   make install-gdb install-dejagnu install-ld || exit 1
++