Woops, apparently only a cleaning was required (I wonder why???) Ahh, the nooks and crannies of autotools are really cramping my style. Lost an afternoon to some crazy caching phenomenon too. Had to move the offending header file into the root source directory, rebuild, then move it back to its subroot directory (a reboot might've done the trick too -- subsequent ssh logins didn't) ...bizarre. As long as this thread is here, If anyone cares to offer any pointers on potential unusual organizational issues with autotools / gcc I'm all ears. michael.a wrote: > > I'm pretty much building my own executibles/libraries for the first time > with gcc. I had no problems with a libtools build, but now I'm trying to > build an executible and during linking I see a bajillion lines that say > "undefined reference to." All of these are referring to symbols which are > internal to the executible's objects files. I'm inclined to say they may > all be inlined functions, or perhaps more specificly inlined/template > functions. > > I've used much of the same code files when building the libtools project, > and my compile options are pretty much identical. So I'm confused why its > not taking for the executible build. > > michael > -- View this message in context: http://www.nabble.com/linking-internal-executible-functions%3A-%22undefined-reference-to%22-----tf4004902.html#a11378595 Sent from the gcc - Help mailing list archive at Nabble.com.
