MS-Dos (real mode) segmentation is not the same as protected mode segmentation (which is the one that relies on GDT and LDT). In real mode, the processor "invents" GDT entries by taking the segment selector and multiplying it by 16 for using that as the segment's offset. Hardly much of the capabilities that the processor provides.
In protected mode, you'll have to provide a GDT (and if you want to use segmentation to its fullest, you probably want a LDT as well). Each selector now points to an entry in the GDT or LDT, which in turn determines the segment's offset and size, access permissions and a few more things.
The problems with protected mode segmentation is that you need a compiler that is aware of that. However, most compilers (i.e. all common ones) assume a flat memory model based on paging and no segmentation, or assume real-mode segmentation (all 16 bit compilers), making it a hell to write programs for your OS in a language other than assembly
Since paging is the norm, you'll find that everything around isn't meant for segmented models. Hence getting a segmentation based OS working takes some creativeness in respect to memory management, which you will figure can cause some classical problems. Expect an absense in tutorials for segmented memory models for the same reason, so you will really doing all the research on your own.
And as mathematician mentioned, segmentation was dropped in long mode (which you need for 64-bit code)
So, now you know what you're up to you can decide whether you actually want the added challenge, or prefer to take the beaten path. Irrespective of what
you decide, we can help with other problems you might get.