Hi, > I'm trying to use concurrent sdcc installations. I ran configure like this: > > ./configure --program-suffix=-r8459 --datarootdir=/usr/local/share/sdcc-r8459 > --disable-various-ports-here > [snip] > $ sdcc-r8459 -V --std-c99 -c main.c -o main.rel > + /usr/local/bin/sdcpp -nostdinc <skip> > + /usr/local/bin/sdas8051 -plosgffw main.rel main.asm > > I was expecting this to be calling sdcpp-<suffix>, sdas8051-<suffix> etc. For > the time being, I created symlinks sdcpp -> sdcpp-<suffix>, sdld -> > sdld-<suffix> (hence no error above). > > Am I missing something at the configure stage or is this intentional? Or am I > looking at a bug?
I assume you are looking at a bug. The backends (and even Makefiles for libraries?) will have to consider program name transformations when calling the various stages (preprocessor, assembler, linker). This is complicated by the configure-options "--program-prefix=PREFIX", your "--program-suffix=SUFFIX", and especially the horrific "--program-transform-name=SEDPROGRAM". I think the best way to deal with this is to let the configure script compute the final binary names for all helper programs, turn them into AC_DEFINES(), and have the backends use the #defined values when calling the helpers. This is not a trivial task and seems to involve quite some effort. You may want to file a bug report for this issue in the tracker system so that this report is not lost in the depths of our mailboxes. Thank you for reporting this. Best regards Raphael ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
