OK, more clues: Under the EDK cygwin shell, if I execute the gcc without any relative paths, everything fully spelled out as below, it gets further, ending with errors like: /tmp/cc4BfUkn.o: In function `process_inputs': main.c:(.text+0x178): undefined reference to `xemacliteif_input' /tmp/ccR7Ojn4.o: In function `fifo_alloc': fifo.c:(.text+0x1f8): undefined reference to `mem_malloc' /tmp/ccqt00fX.o: In function `lwipinit': lwipinit.c:(.text+0x1ec): undefined reference to `mem_init' lwipinit.c:(.text+0x1f8): undefined reference to `memp_init' So it looks like the libraries are not being linked correctly, even though I am using an absolute path.
If I add -llwip4 to the gcc call, it seems to compile without errors finally. Any ideas as to what is going on with this? Have other people been able to compile lwip using 10.1? Thanks, Glenn $ powerpc-eabi-gcc -O2 /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/main.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/tinysh.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/core_util.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_xsg/clk.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_xsg/devices.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_xsg/memory.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_adc/adc.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_lwip/fifo.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_lwip/lwipinit.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_lwip/lwiputil.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_sw_reg/reg.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_bram/bram.c /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/core_info.c -o /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/executable.elf -Wl,-T -Wl,/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/LinkerScript.lwip -I/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/ppc405_1/include -I/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software -I/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers -I/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_xsg -I/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_adc -I/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_lwip -Idrivers/xps_sw_reg -I/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_bram -L/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/ppc405_1/lib -DLWIP_ENABLE On Wed, Sep 3, 2008 at 5:21 AM, John Ford <[email protected]> wrote: > > Hi Andrew, > > Thanks for the suggestions. The include files are definitely in the > > included > > paths. I tried copying them into the Software directory, and that helped > a > > little, but it still can't find the files included in a subdirectory > (thus > > Software/lwip). Does anyone know how to untangle the makefile to get it > to > > print the working directory or something useful like that? > > Thanks, > > This suggests to me that cygwin or whatever is misinterpreting the forward > slash, as weird as that sounds. I would have expected it to misinterpret > a backslash if anything. > > The other possibility is that putting the extra slash on the end of the > include directives confuses things. I don't normally end a -I./foo/bar > with a slash (-I./foo/bar/) This is one of those things that sometimes > works and sometimes doesn't, that is, some shells/programs silently strip > off the extra slash and some just die. > > You should be able to pass the -d option to make (Not sure where to define > it if the makefiles are generated on the fly. Probably in system.make or > one of the xmp files) which will make it spit out voluminous debug info, > including the full paths to files it is trying to use. > > John > > Glenn > > > > On Tue, Sep 2, 2008 at 6:35 PM, <[email protected]> wrote: > > > >> Hi Glenn, > >> > >> It looks like all the -I lines use relative paths, so maybe the cwd when > >> gcc is being executed is not what's expected? Also, I would #1. Make > >> sure > >> the include files exist in one of the included paths and #2. Try > >> explicitly specifying their location in the source files to see if it is > >> indeed a path problem (of course this is not a long term solution). If > >> #2. works, you could probably just copy the missing header files to > >> XPS_iBOB_base/Software, where they shouldn't be overwritten during > >> subsequent gateware or software compiles. > >> > >> - Andrew > >> > >> > >> > >> > I found the source of the permissions problem, it turns out that EDK > >> is > >> > installed with read only permissions on the 'sw' directory, and this > >> was > >> > being propagated in the local copy. I changed the permissions to read > >> > write > >> > for now, but am curious if there's a better way. > >> > However, I have run across another problem. > >> > When I get to the gcc stage, the following command is executed: > >> > > >> > Bitstream generation is complete. > >> > powerpc-eabi-gcc -O2 > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/main.c > >> > > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/tinysh.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/core_util.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_xsg/clk.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_xsg/devices.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_xsg/memory.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_adc/adc.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_lwip/fifo.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_lwip/lwipinit.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_lwip/lwiputil.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_sw_reg/reg.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/xps_bram/bram.c > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/drivers/core_info.c > >> > -o Software/executable.elf \ > >> > -Wl,-T > >> > > >> > -Wl,/cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/LinkerScript.lwip > >> > -I./ppc405_1/include/ -ISoftware/ -Idrivers/ -Idrivers/xps_xsg/ > >> > -Idrivers/xps_adc/ -Idrivers/xps_lwip/ -Idrivers/xps_sw_reg/ > >> > -Idrivers/xps_bram/ -L./ppc405_1/lib/ \ > >> > -DLWIP_ENABLE > >> > > >> >>From this, it looks like the correct directories are included with -I > >> to > >> > find all of the include files. However, I end up with many many errors > >> > like: > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/main.c:12:25: > >> > error: xparameters.h: No such file or directory > >> > > >> > /cygdrive/d/casper_work/ten/snaptestlwip/XPS_iBOB_base/Software/main.c:13:25: > >> > error: xuartlite_l.h: No such file or directory > >> > which indicates that the include files are not being found. > >> > > >> > Does anyone know why this might be the case, or how I might fix this? > >> I > >> > see > >> > the same behavior regardless if I run through bee_xps or just xps from > >> the > >> > command line. > >> > > >> > Thanks, > >> > Glenn > >> > > >> > On Tue, Aug 19, 2008 at 1:48 PM, G Jones <[email protected]> > >> wrote: > >> > > >> >> I checked the permissions, and they seem fine, I can manually copy > >> the > >> >> file. Perhaps it has to do with cygwin/xygwin somehow? > >> >> > >> >> > >> >> On Tue, Aug 19, 2008 at 1:03 PM, John Ford <[email protected]> wrote: > >> >> > >> >>> >> > >> >>> >> Running generate for OS'es, Drivers and Libraries ... > >> >>> >> Running generate for lwIP library ... > >> >>> >> Generating xemacliteif_g.c ... > >> >>> >> Generating lwipopts.h file ... > >> >>> >> ERROR:MDT - lwip () - error copying > >> >>> >> "./src/contrib/ports/v2pro/netif/xemacliteif_polled.c" to > >> >>> >> "./src/contrib/ports/v2pro/netif/xemacliteif.c": permission > >> >>> denied > >> >>> >> while executing > >> >>> >> "file copy -force > >> >>> >> "./src/contrib/ports/v2pro/netif/xemacliteif_polled.c" > >> >>> >> "./src/contrib/ports/v2pro/netif/xemacliteif.c"" > >> >>> >> (procedure "::sw_lwip_v2_00_a::generate" line 120) > >> >>> >> invoked from within > >> >>> >> "::sw_lwip_v2_00_a::generate 60581752" > >> >>> >> ERROR:MDT - Error while running "generate" for processor > >> ppc405_1... > >> >>> >> make: *** [ppc405_1/lib/libxil.a] Error 2 > >> >>> >> ERROR:MDT - Error while running "make -f system.make init_bram" > >> >>> > >> >>> Sorry if this is a stupid comment. > >> >>> > >> >>> Isn't this purely a file permissions error? Like there's no > >> permission > >> >>> for the build to overwrite an older version or write in the > >> directory? > >> >>> > >> >>> John > >> >>> > >> >>> > >> >>> >> > >> >>> >> > >> >>> >> On Mon, Aug 18, 2008 at 4:48 PM, Henry Chen > >> >>> >> <[email protected]>wrote: > >> >>> >> > >> >>> >>> Hi Glenn, > >> >>> >>> > >> >>> >>> It looks like a lot of cores were deprecated in the intervening > >> >>> tool > >> >>> >>> revisions. > >> >>> >>> If you want, it looks like you can manually bring in pcores from > >> >>> EDK7.1 > >> >>> >>> by > >> >>> >>> going > >> >>> >>> to <EDK dir>\hw\XilinxProcessorIPLib\pcores and copy it into the > >> >>> local > >> >>> >>> pcores > >> >>> >>> directory. > >> >>> >>> > >> >>> >>> Or if are so inclined, you can experiment with the 2.00.a > >> version > >> >>> of > >> >>> >>> the > >> >>> >>> core to > >> >>> >>> bring us up to speed =) > >> >>> >>> > >> >>> >>> Thanks, > >> >>> >>> Henry > >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> G Jones wrote: > >> >>> >>> > >> >>> >>>> Hello, > >> >>> >>>> I'm trying to start using the 10.1 tool flow. Compiling a > >> simple > >> >>> >>>> design > >> >>> >>>> with the iBOB LWIP block yields this error: > >> >>> >>>> ERROR:MDT - IPNAME:opb_ethernetlite HW_VER:1.01.a - Can not > >> find > >> >>> valid > >> >>> >>>> MPD > >> >>> >>>> > >> >>> >>>> I opened XPS and indeed it seems like the only version > >> available > >> >>> is > >> >>> >>>> 2.00.a > >> >>> >>>> > >> >>> >>>> Is there any way to get 10.1 to see the old version of the > >> core? > >> >>> >>>> > >> >>> >>>> Thanks, > >> >>> >>>> Glenn > >> >>> >>>> > >> >>> >>> > >> >>> >> > >> >>> > > >> >>> > >> >>> > >> >>> > >> >> > >> > > >> > >> > >> > > > > >
