C / C++ / MFC

15-Feb-06 11:23

Firstly I'd like to warn you all that this is a "Linux C" question and not anyway CLI related.

I've been doing some work on the PicoTux 100 module for a work project.

The background is that I've been porting an I2C driver for a Mitsubishi EEPROM to the PicoTux. The original file was a bit of a mess and everything was in one source file.

I've been moving various routines into seperate source files to tidy things up, between each move I build the entire project. Once I'd completed moving all routines to their various files I get messages similar to the ones below:

Error: symbol _Z10gpio_writeP13gpio_handle_tjj is undefined
Error: symbol _Z10gpio_writeP13gpio_handle_tjj is undefined
Error: symbol _Z16gpio_set_dir_outP13gpio_handle_tj is undefined
Error: symbol _Z10gpio_writeP13gpio_handle_tjj is undefined
Error: symbol _Z10gpio_writeP13gpio_handle_tjj is undefined
Error: symbol _Z10gpio_writeP13gpio_handle_tjj is undefined

The source compiles ok, this is in the linking stage.

There are routines called gpio_write in the source (well actually they're pre-compiled and I'm linking them in).

Does anyone have any ideas on how to track down where these bugs are?

This compilation is being done on Fedora Core 4 using the gcc compiler provided by PicoTux. I've setup MinGW Dev Studio to use the picotux compilers and created a project with two headers files (one has GPIO (General Purpose IO) definitions and the other has function prototypes & a few other I2C definitions). There are then several source files for the various functions.

Thanks in advance for any help

Ed

-- modified at 17:21 Wednesday 15th February, 2006

Ed

Stephen Hewitt15-Feb-06 11:46

Stephen Hewitt

15-Feb-06 11:46

Do a search for Z10gpio_writeP13gpio_handle_tjj and find where it is in the code. Make sure that the file of library it's defined in is included in your project.

Steve

Ed.Poore15-Feb-06 11:54

15-Feb-06 11:54

Z10gpio_writeP13gpio_handle_tjj is, I think, a decorated function name because:

1) There is no function (or anything infact) named Z10gpio_writeP13gpio_handle_tjj
2) This fails at the linking stage so "it has to be defined" because the source code compiles cleanly.

I've tried just now putting all the code into one source file and jiggling the headers to match. This compiles without any errors at all so I'll work like this to get the project done. In fact it can remain like this to simplify matters at the other end but it'd be nice to know why it failed.

Ed

Stephen Hewitt15-Feb-06 12:02

Stephen Hewitt

15-Feb-06 12:02

If you declare a function without defining it things compile ok but you get a failure at link time. e.g.

void Foo();
 
int main(int argc, char* argv[])
{
     Foo();
 
     return 0;
}

To stop the link error you need to add the definition somewhere in your project. i.e.

void Foo()
{
     // Do stuff...
}

You might be right about the name being mangled, you need the unmangled name, MSVC's linker gives both. If you can't find it you may need to guess. i.e, try "writeP13".

Steve

Dan McCormick15-Feb-06 12:58

Dan McCormick

15-Feb-06 12:58

So, what do we know...

1) it doesn't work when items are in separate files. It complains about 'Z10gpio_writeP13gpio_handle_tjj' (which we think is a decorated name) not being defined at link time. As for my guess, the true routine name is gpio_write() and it's first argument is a gpio_handle object. Am I close? Smile | :)

2) it does work when we cram everybody into the same file - inelegant but all the names are there.

Hmm....

Question: in case (1) is the project building a mix of .c and .cpp files? If so, then I would say that the 'missing routines' live in a .c file and export undecorated names in the .o modules whereas the .cpp files are generating decorated names for the linker to fixup.

If that is the case then you need to ensure the .cpp code knows that the gpio_* routines are 'C' routines and not 'C++' routines. Checkout Linkage to Non-C++ Functions[^] for information on how to tell C++ code to expect undecorated names. Gcc surely provides a similar mechanism, if not this exact same one.

If that's not the case, then I guess an "oh well, never mind" is in order.

Later,
Dan

Remember kids, we're trained professionals. Don't try this at home!

-- modified at 18:59 Wednesday 15th February, 2006

Ryan Binns15-Feb-06 17:47

Ryan Binns

15-Feb-06 17:47

Dan McCormick wrote:
As for my guess, the true routine name is gpio_write() and it's first argument is a gpio_handle object. Am I close?

It's a gpio_handle_t. The integers in the name give the number of characters in the next section - it's a simple matter of counting Smile | :)

I believe the 'j' means the parameter is a char, but I'm not sure.

Ryan

"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

Ed.Poore15-Feb-06 20:08

15-Feb-06 20:08

1) Here are the related GPIO routines (so your close Smile | :)

:

gpio_status_t gpio_alloc(gpio_handle_t *, gpio_ports_t);
void gpio_close(gpio_handle_t *);
gpio_status_t gpio_free(gpio_handle_t *, gpio_ports_t);
gpio_dir_t gpio_get_dir(gpio_handle_t *, gpio_ports_t);
gpio_handle_t *gpio_open(void);
gpio_status_t gpio_read(gpio_handle_t *, gpio_ports_t, gpio_data_t *);
gpio_status_t gpio_set_dir_in(gpio_handle_t *, gpio_ports_t);
gpio_status_t gpio_set_dir_out(gpio_handle_t *, gpio_ports_t);
gpio_status_t gpio_write(gpio_handle_t *, gpio_ports_t, gpio_data_t);

Dan McCormick wrote:
Question: in case (1) is the project building a mix of .c and .cpp files?

No C++, just pure ANSI C, I'm not compiling anything to do with C++.

As I said before, for this project I'll just continue with one source file as it's fairly small, < 500 lines of code. But it's more an annoyance than anything else.

Many Thanks Ed

Ryan Binns15-Feb-06 17:46

Ryan Binns

15-Feb-06 17:46

You're linking to a C library? Those are decorated C++ function names. Make sure if you're linking against a C library and you're compiling C++ files, you put extern "C" around the function declarations in the header file.

If it's all C++, then you must have an object file missing from the library, or the library is not being linked in correctly.

Ryan

"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

Ed.Poore15-Feb-06 20:11

15-Feb-06 20:11

Yes I am linking to a C library, but I'm also coding in C, there is no C++ involved at all it's all (99% sure) ANSI C code.

The GPIO routines which are causing the errors are pre-compiled in object files and I'm linking to them, I do have the source to the routines but because they're linking into the Linux kernel and various other parts of the system it's easier to use the .o files and it works when the source is in one file.

Ed

Ryan Binns15-Feb-06 21:55

Ryan Binns

15-Feb-06 21:55

Ed.Poore wrote:
Yes I am linking to a C library, but I'm also coding in C, there is no C++ involved at all it's all (99% sure) ANSI C code.

The compiler seems to think those functions are C++ functions. As I recall, GCC does not mangle C function names - only C++ function names. I would say that somewhere, your files are getting compiled as C++. I assume all the files have lowercase 'c' extensions - uppercase would cause them to be compiled as C++, and you're not compiling with the '-+' switch that forces C++ compilation.

Ryan

"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

Ed.Poore16-Feb-06 11:55

16-Feb-06 11:55

I don't think that I've got an C++ options turned on, in fact it's the first thing I do when I do embedded stuff is turn on the ANSI C Compliance and turn off C++ stuff.

But then again maybe I missed something, anyhow I'll use the single source file at the moment as it works, flying out to Spain on Monday so I need something operational rather than tidy.

Thanks for the pointers though

Ed

Win32 worth it?

Zanathel15-Feb-06 10:58

Zanathel

15-Feb-06 10:58

Hi,
I hate to be bound to frameworks. I prefer simple DLL's that's easy to redistribute with the application. Hence I'd like to stay with C++ without all .net languages such as C#, VB nor Managed VC++.
Soon Microsoft will release Windows Vista... powered by the new programming API WinFX.

Is it worth studying any further Win32?
If not, would you please recommend a substitute api?

Michael Dunn15-Feb-06 12:03

Michael Dunn

15-Feb-06 12:03

MS has backed away from the "everything new will be managed" direction. Vista will indeed have lots of new APIs and COM interfaces to play with. TaskDialog() is one that comes to mind.
In any event, you can't use the new W*F stuff (Avalon, and so on) without requiring Vista or XP SP2, and I for one am not going to do that to my users anytime soon.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

Ed K15-Feb-06 15:10

Ed K

15-Feb-06 15:10

Michael Dunn wrote:
I for one am not going to do that to my users anytime soon.

And the crowd goes wild!!! Big Grin | :-D

I wouldn't either. I know tons of people who rip out XP and put W2K back on.

Love the Erica link! Top pic is the best! Wow!

ed

~"Watch your thoughts; they become your words. Watch your words they become your actions.
Watch your actions; they become your habits. Watch your habits; they become your character.
Watch your character; it becomes your destiny."
-Frank Outlaw.

ThatsAlok16-Feb-06 2:46

ThatsAlok

16-Feb-06 2:46

Ed K wrote:
know tons of people who rip out XP and put W2K back on.

i am one of them Smile | :)

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

cheers,
Alok Gupta
VC Forum Q&A :- I/ IV

Blake Miller16-Feb-06 12:21

Blake Miller

16-Feb-06 12:21

I only had to do that recently for a game from Activision that used the Intel Indeo ? audio and video drivers.

The drivers came built into Windows 2000 and were mysteriously absent from Windows XP.

Of course, you could download the drivers for $14 US to support XP, but the game only now costs about $5 if you can even find it anywhere anymore.

People that start writing code immediately are programmers (or hackers), people that ask questions first are Software Engineers - Graham Shanks

Blake Miller16-Feb-06 12:19

Blake Miller

16-Feb-06 12:19

MS has backed away from the "everything new will be managed" direction.

Kind of like when they backed away from the "everything new will be COM" direction ... Sigh | :sigh:

People that start writing code immediately are programmers (or hackers), people that ask questions first are Software Engineers - Graham Shanks

Ashutosh_shashi15-Feb-06 17:42

Ashutosh_shashi

15-Feb-06 17:42

Yes .................
There was a time when we worked on DOS .... and now after win2k and new versions of UNIX , what abt ......C and C++
It may me they will change some API , they also can make some new data type...
They can modify some api.... But .... it does not affect the core structure of win32..

Ashutosh