From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 29 Nov 2011 08:37:10 +0100 Subject: [Buildroot] LIBFOO_SITE in .mk file In-Reply-To: <003901ccae1b$2d82f950$0400a8c0@dspcgrnzks9p98> References: <003b01cca958$91486a00$0400a8c0@dspcgrnzks9p98> <201111281139.37028.minimod@morethan.org> <002701ccadfe$961b9430$0400a8c0@dspcgrnzks9p98> <201111281324.38619.minimod@morethan.org> <003601ccae04$ada02e80$0400a8c0@dspcgrnzks9p98> <003801ccae12$a7781190$0400a8c0@dspcgrnzks9p98> <003901ccae1b$2d82f950$0400a8c0@dspcgrnzks9p98> Message-ID: <20111129083710.1a83fad6@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Le Mon, 28 Nov 2011 16:15:02 -0600, "Jeff Krasky" a ?crit : > This error message is what got me started down the path of adding the > package in Buildroot. I used to build EtherCAT outside of Buildroot > and then that build process would put EtherCAT in the linux image. > But I'd get this error, so the suggestion was made to make the > EtherCAT build part of Buildroot. Somehow the kernel needs to be > told of this module. The Buildroot process must not be doing a 'make > install'? Or is there a command I should run on the board itself > once Linux is running? It depends on : * what your ethercat.mk file looks like (could you post it on the list ?) * how the EtherCAT build system works Regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com