Joerg Wunsch wrote:
As Joel Sherrill wrote:
I just committed a minor change so if you specify
libbfd-path, the first check for libiberty is that
same directory.
It's been me asking. Doesn't seem to work though:
I actually did not commit it. Try again.
What about the discrepancy on how "path" arguments
versus the help? Which of the following patterns should
we use?
--with-XXX=PATH OR
--with-XXX-path=PATH
...
with_bfd_path = /usr/local
with_libiberty_path = check
checking bfd search- /usr/local/i386-unknown-freebsd7.0/avr in "include" and
"lib"... no
checking bfd search- /usr/local/avr in "include" and "lib"... no
checking bfd search- /usr/local in "" and ""... no
checking bfd search- /usr/local in "bfd" and "bfd"... no
checking bfd search- /usr/local in "include" and "lib64"... no
checking bfd search- /usr/local in "include" and "lib"... yes
checking libiberty search- /usr/i386-unknown-freebsd7.0/avr in "lib"... no
checking libiberty search- /usr/avr in "lib"... no
checking libiberty search- /usr in ""... no
checking libiberty search- /usr in "lib64"... no
checking libiberty search- /usr in "lib"... no
checking libiberty search- /usr in ""... no
configure: error:
Could not locate libiberty.a
Please use the --with-libiberty-path=<path to your libiberty library>
--
Joel Sherrill, Ph.D. Director of Research & Development
[email protected] On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
_______________________________________________
Simulavr-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/simulavr-devel
