[[!meta copyright="Copyright © 2011, 2012 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag open_issue_glibc]] The Hurd does not currently support the `mremap` function. For the `MREMAP_MAYMOVE` case it is easy to work around; see `[binutils]/gold/mremap.c`, for example. Also see the discussion of [[glibc/mmap]]. [[!toc]] # IRC, freenode, #hurd, 2011-01-12 maybe it would be easiest actually to implement mremap()?... antrik: i'm nto sure antrik: implementing mremap could be relatively easy to do actually antrik: IIRC, vm_map() supports overlapping braunr: yes, I think so too braunr: haven't checked, but I have a vague recollection that the fundamentals are pretty much there [[!taglink open_issue_glibc]]: check if it is possible to implement `mremap`. [[I|tschwinge]] remember some discussion about this, but have not yet worked on locating it. [[Talk to me|tschwinge]] if you'd like to have a look at this. # IRC, OFTC, #debian-hurd, 2012-06-19 OK, how the heck do you get an undefined reference to mremap? simply because we don't have it mremap exists only on linux It's in sys/mman.h on linux? No, on GNU/Hurd /usr/include/i386-gnu/sys/mman.h that's just the common file with linux containing just the prototype that doesn't mean there's an implementation behind youpi: hm no, linux has an own version uh Ah, aye, I didn't look at the implementation.. :( it's then odd that it was added to the generic sys/mman.h :) Just another stub? ah, only few linux archs have own versions for the macro values I guess http://paste.debian.net/175173/ on glibc/master Hmm, so where is MREMAP_MAYMOVE coming in from? rgrep on a linux box ;) but that's again linuxish Aye but with us having that in the header it is causing some code to be run which utilizes mremap. If that wasn't defined we wouldn't be calling it. ah we could try to remove it indeed Should I change the code to #ifdef MREMAP_MAYMOVE & !defined __GNU__? no, I said we could remove the definition of MREMAP_MAYMOVE itself